Scribus before 1.6.7 Heap Buffer Overflow via PICT 4-bit Pixel Unpacking
Affects Scribus 1.6.x builds before 1.6.7 when a crafted PICT file with 4-bit indexed images is placed in an image frame or imported. 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, an open-source desktop publishing application, is affected by this flaw in its Mac PICT image loader and import plugin. A specially crafted PICT image file can trigger a memory overflow when imported, potentially crashing the program or allowing an attacker to run arbitrary code.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
Scribus before 1.6.7 contains a heap buffer overflow vulnerability in the Mac PICT image loader and import plugin when unpacking 4-bit indexed pixel data. Attackers can supply a crafted PICT file with inconsistent width and row data that, when placed or imported, writes out of bounds, causing crashes or code execution.
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-104066
What does this mean?
The PICT image loader writes past the end of a heap buffer while unpacking 4-bit indexed images, so it can read or write memory outside what was allocated. This can crash Scribus or lead to a worse outcome.Source: wiki.scribus.net
Am I affected, and how do I check?
Scribus 1.6.x builds before 1.6.7 are in scope. Check the installed Scribus version number, and note that the issue involves crafted PICT files placed in an image frame or imported into Scribus.Source: wiki.scribus.net
What should I do about it?
Upgrade to Scribus 1.6.7, which contains the fix. The Scribus Team strongly encourages all 1.6.x users to upgrade.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