ClassiCube memory corruption in PNG decoder
ClassiCube versions before 1.4.0 are affected when decoding a PNG with a duplicate IHDR chunk, such as a texture pack or player skin. CVSS rates it 8.7 (high). Fixed in 1.4.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.0
- Who is exposed
- Specific setups only
Summary
ClassiCube, before the fixed release, has a heap out-of-bounds write in its PNG decoder that a malicious server can trigger by sending a PNG with a duplicate IHDR chunk. Attackers can reach it remotely, without logging in, by supplying a crafted PNG as a texture pack or player skin, which requires the user to take an action such as loading it, and it can crash the client or potentially execute code.
Written by a model
Original description
ClassiCube before 1.4.0 contains a heap-based out-of-bounds write vulnerability in Png_Decode in src/Bitmap.c that allows malicious servers to corrupt client memory by sending a PNG with a duplicate IHDR chunk. Attackers can supply crafted PNGs via texture pack URLs or player skins so the unreset bufferIdx underflows remaining space, letting IDAT data overflow the buffer to crash clients or execute code.
Who should check
Anyone running ClassiCube clients before 1.4.0, including players who load texture packs or skins from servers
“Affecting ClassiCube >= 0, < 1.4.0”
What to do
Check whether your setup matches what the bug needs.
ClassiCube versions before 1.4.0 A PNG containing a duplicate IHDR chunk is decoded, e.g. a texture pack or player skinUpgrade to a fixed version: 1.4.0.
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-133307 (ClassiCube before 1.4.0 Heap Out-of-Bounds Write via Png_Decode Duplicate IHDR), 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-133307 (entry last updated 2026-11-19):
Affected:
- ClassiCube ClassiCube: fixed in 1.4.0
Fixed versions: 1.4.0.
Conditions (all must be true for the bug to be hit):
- ClassiCube versions before 1.4.0 (source: https://www.vulncheck.com/advisories/classicube-before-1.4.0-heap-out-of-bounds-write-via-png-decode-duplicate-ihdr)
- A PNG containing a duplicate IHDR chunk is decoded, e.g. a texture pack or player skin (source: https://www.vulncheck.com/advisories/classicube-before-1.4.0-heap-out-of-bounds-write-via-png-decode-duplicate-ihdr)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, a user action.
CISA KEV: CVE-2026-133307 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133307 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/ClassiCube/ClassiCube/commit/c461fa759f218e3c6bda4642b9af79a98dc84a43
- https://github.com/ClassiCube/ClassiCube/releases/tag/1.4.0
- https://github.com/ClassiCube/ClassiCube/blob/1.3.9/src/Bitmap.c#L529
- https://github.com/ClassiCube/ClassiCube
- https://www.vulncheck.com/advisories/classicube-before-1.4.0-heap-out-of-bounds-write-via-png-decode-duplicate-ihdr
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-133307
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-133307"}.Affected versions
- ClassiCube ClassiCubefixed in 1.4.0
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
Timeline
- CVE published
- First seen by cve.now
Evidence 7
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133307 |
| Record | NVD · CVE-2026-133307 |
| Other links 5 | |
| Patch | GitHub · ClassiCube/ClassiCube · Commit c461fa75 |
| Repository | GitHub · ClassiCube/ClassiCube · Release 1.4.0 |
| Repository | GitHub · ClassiCube/ClassiCube · src/Bitmap.c · L529 |
| Repository | GitHub · ClassiCube/ClassiCube · Repository |
| Link | vulncheck.com · advisories/classicube-before-1.4.0-heap-out-of-bounds-write-via-png-decode-duplicate-ihdr |
Questions about CVE-2026-133307
Is CVE-2026-133307 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
What does this mean?
ClassiCube's PNG decoder writes past the end of a heap buffer when a PNG contains a duplicate IHDR chunk. This corrupts client memory and can crash the client or allow code execution.
Source: vulncheck.com
Which versions are affected by CVE-2026-133307?
ClassiCube: before 1.4.0.
Source: cve.now feed data
Am I affected, and how do I check?
ClassiCube versions before 1.4.0 are affected. The affected setup is decoding a PNG with a duplicate IHDR chunk, such as a texture pack or player skin. Compare the installed ClassiCube version with 1.4.0 and check which PNG sources the client loads.
Source: vulncheck.com
How do I fix CVE-2026-133307?
Upgrade to ClassiCube 1.4.0 or later, which is the listed fixed version.
Source: vulncheck.com
Related
- CVE-2026-133308ClassiCube before 1.4.0 Heap Out-of-Bounds Write via PNG Decoder Filters
- CVE-2026-116446Dell PowerStore SDNAS contains an out-of-bounds memory vulnerability in the NAS NFS service that an unauthenticated remote attacker could…
- CVE-2026-110486Remote heap out-of-bounds read/write in Eclipse Mosquitto
- CVE-2026-116441Dell PowerStore SDNAS contains an out-of-bounds write vulnerability in the storage-processor interconnect driver that could allow a…
- CVE-2026-133528BeamNG.drive before 0.40.6 LuaJIT FFI Sandbox Escape via JIT Bounds-Check Bypass
- CVE-2026-62258HTSlib: Stack write overflow in HTSlib CRAM decoder
No corrections so far. Something wrong on this page? Report an error.