CVE-2026-4980: 
NixOS vulnerability analysis and mitigation

CVE-2026-4980 is a local file disclosure vulnerability in the XInclude processing component of Inkscape, classified under CWE-611 (Improper Restriction of XML External Entity Reference). It affects Inkscape versions 1.1 through 1.3 (exclusive), allowing a remote attacker to read arbitrary local files by tricking a user into opening a crafted SVG file containing malicious xi:include tags. The vulnerability was published on March 27, 2026, and carries a CVSS v3.1 base score of 6.3 (Medium) (Feedly, EUVD).

The root cause is Inkscape's failure to properly restrict XML XInclude (xi:include) directives when processing SVG files, classified as CWE-611 (Improper Restriction of XML External Entity Reference). When Inkscape renders or exports an SVG containing <xi:include parse="text" href="file:///etc/passwd"/>, it resolves the file URI and embeds the contents of the referenced local file into the output document (e.g., a PDF export). Exploitation requires no privileges but does require user interaction — specifically, the victim must open the malicious SVG file. A public proof-of-concept demonstrating the attack using the Inkscape CLI (inkscape test.svg --export-type=pdf --export-filename=output.pdf) is available (Inkscape GitLab Issue, Inkscape MR).

Successful exploitation allows an attacker to read arbitrary files accessible to the user running Inkscape, including sensitive files such as /etc/passwd, SSH private keys, configuration files, or application credentials. The confidentiality impact is rated High, while integrity and availability are unaffected. Because the scope is marked as Changed in the CVSS vector, the impact extends beyond the Inkscape process itself to the broader file system accessible by the user account (Feedly, EUVD).

A proof-of-concept exploit with concrete reproduction steps is publicly available on the Inkscape GitLab issue tracker, demonstrating file disclosure via a crafted SVG and CLI export command (Inkscape GitLab Issue). There is no current evidence of in-the-wild exploitation or threat actor attribution. The EPSS score is approximately 0.025% (0.000250), indicating low probability of near-term automated exploitation. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Detection plugins are available via Nessus (ID: 304166) and Qualys (ID: 6275011) (Feedly).

1. Craft a malicious SVG file: Create an SVG file containing an XInclude directive targeting a sensitive local file, for example:

<?xml version="1.0" encoding="UTF-8"?>
<svg xmlns="http://www.w3.org/2000/svg"
     xmlns:xi="http://www.w3.org/2001/XInclude">
  <xi:include parse="text" href="file:///etc/passwd"/>
</svg>

2. Deliver the file to the victim: Distribute the malicious SVG via email attachment, file sharing platform, or a website offering SVG downloads, relying on social engineering to convince the target to open it.
3. Victim opens the file in Inkscape: The victim opens the SVG in Inkscape 1.1–1.2.x, either interactively or via a CLI export command such as inkscape test.svg --export-type=pdf --export-filename=output.pdf.
4. XInclude is processed: Inkscape's XInclude processor resolves the file:// URI and embeds the contents of the referenced local file (e.g., /etc/passwd) into the rendered or exported output.
5. Attacker retrieves the exfiltrated data: The attacker obtains the output file (e.g., the exported PDF) containing the embedded sensitive file contents, completing the local file disclosure (Inkscape GitLab Issue).

• File System: SVG files received from external sources containing xi:include elements with file:// URIs; unexpected PDF or other export files containing embedded plaintext content from system files (e.g., /etc/passwd entries).
• Process: Inkscape process spawned with CLI export arguments (--export-type, --export-filename) on files from untrusted or temporary directories.
• Logs: Application or audit logs showing Inkscape accessing sensitive files (e.g., /etc/passwd, ~/.ssh/id_rsa) outside of normal user activity; file access events triggered by the Inkscape process to system configuration files.

Upgrade Inkscape to version 1.3 or later, which addresses the XInclude file disclosure vulnerability via the fix in merge request Inkscape MR. Until patching is possible, users should avoid opening SVG files from untrusted or unknown sources. Organizations can implement file-type filtering on email gateways and restrict Inkscape's execution environment (e.g., using sandboxing or AppArmor/SELinux profiles) to limit file system access (Feedly, EUVD).

Coverage of CVE-2026-4980 has been limited to vulnerability database aggregators and security scanning vendors. Tenable published a Nessus detection plugin (ID: 304166), and Qualys added detection (ID: 6275011). A brief technical write-up was published by Infinitsec (Infinitsec). No notable researcher commentary or significant social media discussion has been observed beyond standard CVE tracking.