cve.bz

CVE-2026-120433 Stack-based Buffer Overflow

8.5 highEPSS 0.2%

High (8.5). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
Netpbm before 10.86.51, 11.x before 11.02.30, and 11.03 before 11.15.08 contains a stack-based buffer overflow in the picttoppm paintPoly() function due to an unbounded polygon point count. Attackers can supply a crafted PICT file with a polygon exceeding 100 points to overwrite the fixed pts array, causing crashes or potentially code execution.

Severity

CVSS 4.0

8.5 high
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

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-121 Stack-based Buffer Overflow
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-120433 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120433?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120433?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-120433 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14netpbm-freeno fix listedDEBIAN-CVE-2026-120433
Ubuntu16.04:LTS, 18.04:LTS, 20.04:LTS and 4 morenetpbm-freeno fix listedUBUNTU-CVE-2026-120433
openSUSETumbleweednetpbm11.16.1-2.1openSUSE-SU-2026:12463-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Important because an attacker can potentially execute arbitrary code or trigger an application crash within the privileges of the executing process. Exploitation requires user interaction or an automated ingestion pipeline that passes untrusted Apple QuickDraw graphic data to the standalone conversion tool. While the affected binary is not an active network service by default, environments running server-side file transformation workflows or multi-user systems where users process external graphics are directly exposed.

Red Hat's mitigation

Update to a fixed netpbm release (upstream 10.86.51 / 11.02.30 / 11.15.08, or RHEL errata builds such as RHEL 8 netpbm 10.82.00-9 once released); alternatively avoid processing untrusted PICT files with picttoppm and sandbox or filter image-ingestion pipelines that pass untrusted data to conversion tools.

--- CME Mitigation Guidance (2026-11-04) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to enforce bounds checking on polygon point counts in picttoppm to prevent stack buffer overruns when parsing QuickDraw PICT files: upgrade to Netpbm 10.86.51, 11.02.30, 11.15.08 (or the fixed Netpbm builds), which prevent buffer overrun when parsing polygons with large point counts in picttoppm, closing crafted QuickDraw PICT file containing a polygon with excessive point count. Until patched, this is a concern on Linux systems executing picttoppm via automated file transformation pipelines or user interaction, so Avoid processing untrusted PICT files with picttoppm, and isolate or filter image-ingestion pipelines that pass external graphics to conversion tools. As a compensating measure, Enable ASLR to randomize process memory segments and impede reliable execution redirection, Enable PIE and full RELRO to hinder function redirection and ROP gadget location, Apply Control Flow Integrity or Shadow Call Stack to protect return addresses against ROP chains, Run SELinux in enforcing mode to confine the picttoppm process and restrict unauthorized actions, Use Landlock filesystem sandboxing to isolate picttoppm and limit accessible paths, and Isolate picttoppm within Linux user, PID, network, and mount namespaces to prevent broader host compromise. These controls limit blast radius and contain exploitation, but they do not fix the underlying stack-based buffer overflow defect — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10netpbmAffected
Red Hat Enterprise Linux 6netpbmAffected
Red Hat Enterprise Linux 7netpbmAffected
Red Hat Enterprise Linux 8netpbmAffected
Red Hat Enterprise Linux 9netpbmAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-120433.

References

Check your stackJSON