CVE-2026-10233

LOWPre-NVD 3.33.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-06-01. A secondary CVSS source baseline 3.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated
3.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 3.3Exploit: No code on recordExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

The CVE record's description, written by its CNA (VulDB), states the affected versions: "A security vulnerability has been detected in Assimp up to 6.0.4." No release containing a fix is confirmed on record.

A security vulnerability has been detected in Assimp up to 6.0.4. Affected by this issue is the function HL1MDLLoader::read_sequence_infos of the file HL1MDLLoader.cpp of the component Half-Life 1 MDL Loader. The manipulation of the argument aiString leads to out-of-bounds read. The attack needs to be performed locally. The exploit has been disclosed publicly and may be used. The project tagged the reported issue as bug.

CVSS v3
3.3
EG Score
3.3LOWmedium confidence
EG Risk
31
EG Risk 31/100

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 computed (value × EchelonGraph’s weight)
Severity33% × 45%
The EG Score, 3.3 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 1, 2026

Last Modified

July 22, 2026

References (7)

Vendor Advisories for CVE-2026-10233(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.0.1~ds0-2 ... 6.0.5+ds-1 (34 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.2.5~ds0-1 ... 6.0.5+ds-1 (14 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.4.3+ds-2 ... 6.0.5+ds-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
assimp5.4.3+ds-2 ... 6.0.5+ds-1 (7 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 26× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 155 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 56 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 16:41 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-10-11 20:16 UTCEG score recompute
  4. 2026-10-11 18:28 UTCEG score recompute
  5. 2026-10-11 15:02 UTCEG score recompute
  6. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  14. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  15. 2026-10-03 13:39 UTCOSV refresh
  16. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  18. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  21. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  22. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-09-14 06:12 UTCEG score recompute
  25. 2026-09-14 06:12 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
Show 74 more
  1. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  2. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  3. 2026-09-10 21:53 UTCOSV refresh
  4. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  5. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  6. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  7. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  8. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  9. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  10. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  11. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  12. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  13. 2026-08-23 13:58 UTCEG score recompute
  14. 2026-08-23 13:58 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  15. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  16. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  17. 2026-08-20 10:20 UTCEG score recompute
  18. 2026-08-20 10:20 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  19. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  20. 2026-08-17 07:36 UTCEG score recompute
  21. 2026-08-17 07:36 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  22. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  23. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  24. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  25. 2026-08-14 11:12 UTCEG score recompute
  26. 2026-08-14 11:12 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  27. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  28. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  29. 2026-08-11 14:55 UTCEG score recompute
  30. 2026-08-11 14:55 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  31. 2026-08-11 13:42 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  32. 2026-08-10 23:59 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  33. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  34. 2026-08-08 18:38 UTCEG score recompute
  35. 2026-08-08 18:38 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  36. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  37. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  38. 2026-08-05 22:21 UTCEG score recompute
  39. 2026-08-05 22:21 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  40. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  41. 2026-08-04 15:09 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  42. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  43. 2026-08-03 10:35 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  44. 2026-08-03 02:04 UTCEG score recompute
  45. 2026-08-03 02:04 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  46. 2026-08-02 02:26 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  47. 2026-08-01 04:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  48. 2026-07-31 05:47 UTCEG score recompute
  49. 2026-07-31 05:47 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  50. 2026-07-30 16:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  51. 2026-07-30 01:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  52. 2026-07-28 15:36 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  53. 2026-07-27 02:10 UTCEG score recompute
  54. 2026-07-27 02:10 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  55. 2026-07-25 14:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  56. 2026-07-24 14:17 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  57. 2026-07-23 03:04 UTCEG score recompute
  58. 2026-07-22 14:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  59. 2026-07-20 17:08 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  60. 2026-07-19 14:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  61. 2026-07-18 10:04 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  62. 2026-07-16 17:02 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  63. 2026-07-15 16:57 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  64. 2026-07-15 02:00 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  65. 2026-07-14 13:23 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  66. 2026-07-13 22:30 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  67. 2026-07-13 06:12 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  68. 2026-07-12 05:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  69. 2026-07-11 13:50 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  70. 2026-07-11 08:27 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  71. 2026-07-09 19:10 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  72. 2026-07-08 17:06 UTCGHSA enrichmentGHSA-964j-jgrw-m572 · GitHub severity LOW · GitHub CVSS 3.3
  73. 2026-07-08 15:15 UTCEPSS rescoreEPSS 0.1% · 1st percentile
  74. 2026-07-07 13:46 UTCEPSS rescoreEPSS 0.1% · 1st percentile

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-10233?
CVE-2026-10233 is a low-severity vulnerability; its CVE record was published on June 1, 2026. A security vulnerability has been detected in Assimp up to 6.0.4. Affected by this issue is the function HL1MDLLoader::readsequenceinfos of the file HL1MDLLoader.cpp of the component Half-Life 1 MDL Loader. The manipulation of the argument aiString leads to out-of-bounds read. The attack needs to…
When was the CVE record for CVE-2026-10233 published?
The CVE record for CVE-2026-10233 was published on June 1, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of July 22, 2026; the record at its source may have been updated since.
Is CVE-2026-10233 actively exploited?
CVE-2026-10233 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-10233?
CVE-2026-10233 has a CVSS base score of 3.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-10233?
No fix for CVE-2026-10233 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (VulDB), states the affected versions: "A security vulnerability has been detected in Assimp up to 6.0.4." No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-10233 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-10233

Explore →

Is Your Infrastructure Affected by CVE-2026-10233?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs