ClassiCube heap out-of-bounds write in PNG decoder
- Exploited
- No known exploitation
- Fix
- Fixed in 1.4.0
- Who is exposed
- Not reported
Summary
ClassiCube contains a heap out-of-bounds write flaw in its PNG decoder. A malicious multiplayer server can trigger it remotely, without logging in, by supplying a crafted texture pack URL or player skin, though this requires user action to load. The flaw can corrupt memory and crash connecting clients.
Written by a model
Original description
ClassiCube before 1.4.0 contains a heap-based out-of-bounds write vulnerability in Png_Reconstruct in src/Bitmap.c that occurs when AVERAGE and PAETH filters process zero-width PNG images. A malicious multiplayer server can supply a crafted texture pack URL or player skin to write past the heap buffer, corrupting memory and crashing connecting clients.
What to do
Upgrade 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-133308 (ClassiCube before 1.4.0 Heap Out-of-Bounds Write via PNG Decoder Filters), 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-133308 (entry last updated 2026-11-19):
Affected:
- ClassiCube ClassiCube: fixed in 1.4.0
Fixed versions: 1.4.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133308 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133308 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#L172
- https://github.com/ClassiCube/ClassiCube/blob/1.3.9/src/Bitmap.c#L182
- https://github.com/ClassiCube/ClassiCube
- https://www.vulncheck.com/advisories/classicube-before-1.4.0-heap-out-of-bounds-write-via-png-decoder-filters
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-133308
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-133308"}.Affected versions
- ClassiCube ClassiCubefixed in 1.4.0
cve.now Index
- Exploitation0/40No signal
- 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 patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 27 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Evidence 8
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133308 |
| Record | NVD · CVE-2026-133308 |
| Other links 6 | |
| Patch | GitHub · ClassiCube/ClassiCube · Commit c461fa75 |
| Repository | GitHub · ClassiCube/ClassiCube · Release 1.4.0 |
| Repository | GitHub · ClassiCube/ClassiCube · src/Bitmap.c · L172 |
| Repository | GitHub · ClassiCube/ClassiCube · src/Bitmap.c · L182 |
| Repository | GitHub · ClassiCube/ClassiCube · Repository |
| Link | vulncheck.com · advisories/classicube-before-1.4.0-heap-out-of-bounds-write-via-png-decoder-filters |
Questions about CVE-2026-133308
Is CVE-2026-133308 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-133308?
ClassiCube: before 1.4.0.
Source: cve.now feed data
How do I fix CVE-2026-133308?
Upgrade to a fixed version: 1.4.0.
Source: cve.now feed data
Related
- CVE-2026-133307ClassiCube before 1.4.0 Heap Out-of-Bounds Write via Png_Decode Duplicate IHDR
- 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.