Scribus before 1.6.7 Heap Buffer Overflow via PICT Pixmap Loader
Affects Scribus versions before 1.6.7 when a PICT file 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 a heap buffer overflow in its PICT image loader and import plugin. An attacker who supplies a specially crafted PICT file could crash the program or potentially run code with the user's privileges when the file is placed or imported.
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 PICT image loader and import plugin that allows attackers to corrupt heap memory by supplying an unchecked bytesPerLine value. Attackers can craft a PICT file whose bytesPerLine exceeds the QImage scanline size, so placing or importing it crashes Scribus and may execute code 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-104062
What does this mean?
A crafted PICT image whose stored bytes-per-line value does not match its width can make the Scribus pixmap loader read or write memory outside the buffers it allocated. This can crash Scribus and may lead to worse outcomes such as code execution.Source: wiki.scribus.net
Am I affected, and how do I check?
All Scribus versions before 1.6.7 are in scope. The bug needs a PICT file whose stored bytes-per-line does not match the image width, placed in an image frame or imported. To check your version, look at the version shown in Scribus's About dialog or run scribus --version from a terminal.Source: wiki.scribus.net
What should I do about it?
Upgrade Scribus to version 1.6.7 or later. No workaround is listed in the facts, so the fixed release is the only documented remedy.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