Scribus before 1.6.7 Out-of-Bounds Memory Access via SVM Import Plugin
Scribus versions before 1.6.7 are exposed when a crafted SVM file is imported or placed in an image frame. CVSS rates it High (8.5). Fixed in 1.6.7.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 1.6.7
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
Scribus, a desktop publishing application, is affected through its SVM image import plugin. A specially crafted SVM file can trigger out-of-bounds memory access, potentially causing the program to crash or allowing an attacker to run code with the user's privileges.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Scribus before 1.6.7 contains an out-of-bounds memory access vulnerability in the importsvm plugin that fails to verify bitmap and transparency mask dimensions match. Attackers can supply a crafted SVM file with mismatched mask dimensions to trigger heap reads and writes, causing crashes or code execution as the user.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Scribus Scribus
fixed in 1.6.7
References 4
GitHub · scribusproject/scribus
wiki.scribus.net
Questions about CVE-2026-104067
What does this mean?
The SVM import plugin can be made to read or write memory outside the buffers it allocated. This can crash Scribus or lead to worse outcomes.Source: wiki.scribus.net
Am I affected, and how do I check?
Scribus versions before 1.6.7 are affected, and the problem occurs when a crafted SVM file is imported or placed in an image frame. To check a version, look at the Scribus about dialog or the version shown at startup.Source: wiki.scribus.net
What should I do about it?
Upgrade to Scribus 1.6.7 or later, which contains the fix.Source: wiki.scribus.net
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data