Skip to main content
Menu
CVEs

CVE

Assimp heap out-of-bounds read in glTF data URI parser

CVE-2026-129478EUVD-2026-126029GHSA-4WFG-WH54-RM56

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N

6.9MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Do first: Apply the patch listed under Evidence.

Published
Last modified
Reference
Last checked
0.12% · 1st percentile
7/100 · provisional
None on Exploit-DB, Metasploit or GitHub

Summary

Assimp, a 3D model import library, has a heap out-of-bounds read in its glTF data URI parser that a local attacker can trigger without logging in, though it requires a user to open a crafted glTF file. Successful exploitation can crash the application or leak nearby heap memory.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Original description

Assimp through 6.0.6 contains a heap out-of-bounds read vulnerability in glTFCommon::Util::ParseDataURI caused by storing the data offset in a signed char. Attackers can supply a crafted glTF file with a raw data URI whose segment starts beyond byte 127 to crash applications or leak adjacent heap memory.

cve.now Index

7Pcve.now Index 7 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity6.9/10CVSS 6.9
  • No patch0/5No signal

What would change the score

  • Would score about 62 if added to CISA KEV
  • Would score about 57 if CISA's SSVC rates exploitation active
  • Would score about 29 if advisories confirm default setups are exposed

What to do

  • Apply the patch listed under Evidence.

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-129478 (Assimp through 6.0.6 Heap Out-of-Bounds Read via glTF ParseDataURI), 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-129478 (entry last updated 2026-11-15):
Affected:
- assimp assimp: through 6.0.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129478 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129478 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/assimp/assimp/pull/7029
- https://github.com/assimp/assimp/issues/6927
- https://github.com/assimp/assimp/blob/v6.0.6/code/AssetLib/glTFCommon/glTFCommon.cpp#L86-L105
- https://www.vulncheck.com/advisories/assimp-through-6.0.6-heap-out-of-bounds-read-via-gltf-parsedatauri
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-129478
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-129478"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • assimp assimp

    through 6.0.6

Evidence 6

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 4

  1. Patch
  2. Report
  3. Repository
  4. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-129478

Is CVE-2026-129478 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-129478?

assimp: through 6.0.6.Source: cve.now feed data