cgltf through 1.15 contains an integer overflow vulnerability in the non-sparse accessor bounds check within cgltf_validate() that allows remote attackers to cause memory disclosure and denial of service by supplying crafted accessor count values. Attackers can provide malformed .gltf or .glb input with a specially crafted accessor count to overflow the unsigned integer multiplication of accessor stride and element count, causing the bounds check to pass and triggering a heap out-of-bounds read when cgltf_accessor_read_float() is subsequently called on the validated malformed accessor.
CVE-2026-75148
Score 6.1 from GitHub Security Advisory published 2026-08-19. a secondary CVSS source baseline 6.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.1
- EG Score
- 6.1(high)
- EG Risk
- 43(Track)EG Risk 43/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity61% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
August 19, 2026
Last Modified
August 20, 2026
Advisory Details (2)
Auto-updated Aug 19, 2026cgltf 1.15 Integer Overflow via cgltf_validate() Accessor Bounds Check | Advisories | VulnCheck
https://www.vulncheck.com/advisories/cgltf-integer-overflow-via-cgltf-validate-accessor-bounds-checkSecurity: Integer overflow in cgltf_validate() non-sparse accessor causes heap OOB read (CWE-125/CWE-190) · Issue #301 · jkuhlmann/cgltf · GitHub
https://github.com/jkuhlmann/cgltf/issues/301Vendor Advisories for CVE-2026-75148(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-20 18:17 UTCEG score recompute
- 2026-08-20 18:17 UTCGHSA enrichment
- 2026-08-20 17:32 UTCEG score recompute
- 2026-08-20 17:32 UTCGHSA enrichment
- 2026-08-20 14:25 UTCEG score recompute
- 2026-08-20 14:25 UTCGHSA enrichment
- 2026-08-19 14:26 UTCEG score recompute
- 2026-08-19 13:57 UTCEG score recompute
- 2026-08-19 13:57 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-190
Frequently asked(5)
What is CVE-2026-75148?
When was CVE-2026-75148 disclosed?
Is CVE-2026-75148 actively exploited?
What is the CVSS score of CVE-2026-75148?
How do I remediate CVE-2026-75148?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-75148
Is Your Infrastructure Affected by CVE-2026-75148?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.