jhead memory corruption in PNG section handling
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
Matthias-Wandel jhead has a double free flaw in its PNG section handling code (RemovePngSection in pngfile.c). An attacker can trigger it remotely, without logging in, though a user must take some action for it to work. Manipulating the data the software processes leads to the double free.
Written by a model
Original description
A security vulnerability has been detected in Matthias-Wandel jhead up to 3.3. This affects the function RemovePngSectionByType/RemovePngSection of the file src/pngfile.c of the component PNG Section Handler. The manipulation leads to double free. Remote exploitation of the attack is possible. The exploit has been disclosed publicly and may be used. The project was informed of the problem early through an issue report but has not responded yet.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133496 (Matthias-Wandel jhead PNG Section pngfile.c RemovePngSection double free), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133496 (entry last updated 2026-11-20):
Affected:
- Matthias-Wandel jhead: versions 3.0, 3.1, 3.2, 3.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133496 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133496 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/Matthias-Wandel/jhead/issues/114
- https://vuldb.com/vuln/440916
- https://vuldb.com/vuln/440916/cti
- https://vuldb.com/cve/CVE-2026-133496
- https://vuldb.com/submit/1049876
- https://github.com/Matthias-Wandel/jhead/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133496
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133496"}.Affected versions
- Matthias-Wandel jhead3.0, 3.1, 3.2, 3.3
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 8
| Kind | Source |
|---|---|
| CVE record 1Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133496 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · user-attachments/files · 32914916/jhead_png_ekif_double_free.zip |
| Other links 6 | |
| Advisory | VulDB · Advisory #440916 |
| Advisory | VulDB · Threat intelligence #440916 |
| Advisory | VulDB · CVE-2026-133496 record |
| Advisory | VulDB · Submission #1049876 |
| Report | GitHub · Matthias-Wandel/jhead · Issue #114 |
| Repository | GitHub · Matthias-Wandel/jhead · Repository |
Questions about CVE-2026-133496
Is CVE-2026-133496 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
Which versions are affected by CVE-2026-133496?
jhead: versions 3.0, 3.1, 3.2, 3.3.
Source: cve.now feed data
Related
- CVE-2024-2824Matthias-Wandel jhead exif.c PrintFormatNumber heap-based overflow
- CVE-2026-90682Matthias-Wandel jhead WebP EXIF gpsinfo.c ProcessGpsInfo heap-based overflow
- CVE-2026-90681Matthias-Wandel jhead EXIF Parsing exif.c Get16u out-of-bounds
- CVE-2026-132143DrayTek Vigor2960 Backup mainfunction.cgi doWebBackup stack-based overflow
- CVE-2026-132142DrayTek Vigor2960 CGI Process mainfunction.cgi dataflowstatus stack-based overflow
- CVE-2026-132141DrayTek Vigor2960 Jsonstatus mainfunction.cgi json_load_lock stack-based overflow
No corrections so far. Something wrong on this page? Report an error.