CVE-2026-47667

HIGHPre-NVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (43rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Elevated

Also known asEUVD-2026-46392 (ENISA EUVD)Source: ENISA EUVD

7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.5%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

CImg Library is a C++ library for image processing. Prior to version 4.0.0 in _load_analyze(), the header_size field is read as an unsigned int from the first 4 bytes of an Analyze/NIfTI file and passed directly to new unsigned char[header_size] without being bounded against the actual file size. A value up to ~4 GB is accepted. If the subsequent fread returns short as it will for any malformed file), the function throws a CImgIOException and the allocated buffer is never freed. A 6-byte crafted file is sufficient to trigger an allocation of ~1.3 GB per call, with the full allocation leaked on every error path. The issue is reachable via load_analyze() and the generic load() when the file extension is .hdr, .img, or .nii. Version 4.0.0 fixes the issue.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

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

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

July 21, 2026

Last Modified

October 24, 2026

Advisory Details (3)

Auto-updated Jul 21, 2026
Patch available. Sources: github_commit, github.
GitHub advisoryMentions a patch (unverified)

Uncontrolled Memory Allocation and Memory Leak in `_load_analyze()` via Crafted NIfTI/Analyze Header · Advisory · GreycLab/CImg · GitHub

https://github.com/GreycLab/CImg/security/advisories/GHSA-rmfc-grgj-qwhv
Web page

OOM and memory leak via unbounded header_size in crafted Analyze/NIfTI file (_load_analyze) · Issue #480 · GreycLab/CImg · GitHub

https://github.com/GreycLab/CImg/issues/480
GitHub commit

commit 6a69bf725ffd (GreycLab/CImg)

Fix landed in GreycLab/CImg commit 6a69bf725ffd — awaiting tagged release

https://github.com/GreycLab/CImg/commit/6a69bf725ffd111a4c7dc61cc15e3661abd158ee

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
cimg2.9.4+dfsg-2 ... 3.5.2+dfsg-2 (15 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
cimg3.2.1+dfsg-1 ... 4.0.4+dfsg-1 (6 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
cimg3.5.2+dfsg-1, 3.5.2+dfsg-1+deb13u1, 3.5.2+dfsg-2, 4.0.4+dfsg-1
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
cimg3.5.2+dfsg-1, 3.5.2+dfsg-2
  • every version up to 4.0.4+dfsg-1: fixed in 4.0.4+dfsg-1
—

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 39× 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 100 of 145 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. None are among the latest 100 rows. The 45 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-47667?
CVE-2026-47667 is a high-severity vulnerability; its CVE record was published on July 21, 2026. CImg Library is a C++ library for image processing. Prior to version 4.0.0 in loadanalyze(), the headersize field is read as an unsigned int from the first 4 bytes of an Analyze/NIfTI file and passed directly to new unsigned char[headersize] without being bounded against the actual file size. A…
When was the CVE record for CVE-2026-47667 published?
The CVE record for CVE-2026-47667 was published on July 21, 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 October 24, 2026; the record at its source may have been updated since.
Is CVE-2026-47667 actively exploited?
CVE-2026-47667 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-47667?
CVE-2026-47667 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-47667?
A fix for CVE-2026-47667 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-47667?

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