CVE-2026-102504

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 CISA-ADP (Vulnrichment) CVSS v3.1 (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from CISA-ADP (Vulnrichment) CVSS v3.1
Sources: CISA-ADP (Vulnrichment) CVSS v3.1, EPSS

Also known asEUVD-2026-90811 (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).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to Imager 1.037 or later."

Imager versions before 1.037 for Perl exit the process reading a raw image with an out-of-range raw_datachannels value in i_readraw_wiol.

Nothing range-checks raw_datachannels. The line buffer is sized as the image width times the channel count with no overflow check, so a negative or very large count requests an excessive allocation. When it fails, Imager's allocator calls exit(3).

Passing an untrusted raw_datachannels value to Imager->read() triggers an uncatchable exit.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
49
EG Risk 49/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.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
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 none (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.4%
EPSS %ILE
33rd
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.CISA-ADP (Vulnrichment) CVSS v3.1 · CVSS v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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, and whom BOD 26-04 binds: 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 none (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.

The score's inputs: 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

October 1, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Oct 1, 2026
Patch available. Sources: github.
Web page

oss-security - CVE-2026-102504: Imager versions before 1.037 for Perl exit the process reading a raw image with an out-of-range raw_datachannels value in i_readraw_wiol

http://www.openwall.com/lists/oss-security/2026/10/01/9
GitHub advisoryMentions a patch (unverified)

Unvalidated raw_datachannels can cause incorrect memory allocations · Advisory · tonycoz/imager · GitHub

https://github.com/tonycoz/imager/security/advisories/GHSA-g549-r73g-x7x6

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
libimager-perl1.019+dfsg-1 ... 1.037+dfsg-2 (21 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
libimager-perl1.027+dfsg-1 ... 1.037+dfsg-2 (13 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
libimager-perl1.027+dfsg-1 ... 1.037+dfsg-1 (12 versions)
  • every version up to 1.037+dfsg-2: fixed in 1.037+dfsg-2
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 47× 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.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  3. 2026-10-30 18:10 UTCEG score recompute
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  9. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-25 14:56 UTCEG score recompute
  11. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  12. 2026-10-24 07:00 UTCEG score recompute
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-18 05:10 UTCEG score recompute
  20. 2026-10-17 19:49 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  24. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  25. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
Show 28 more
  1. 2026-10-12 16:41 UTCEG score recompute
  2. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.4% · 31st 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:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-10-10 22:15 UTCEG score recompute
  8. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-10-09 23:32 UTCEG score recompute
  10. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-10-09 00:59 UTCEG score recompute
  12. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  13. 2026-10-08 10:44 UTCEG score recompute
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  15. 2026-10-07 00:32 UTCEG score recompute
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-10-06 01:56 UTCEG score recompute
  18. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-05 03:25 UTCEG score recompute
  20. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-03 17:35 UTCEG score recompute
  22. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  23. 2026-10-02 19:03 UTCEG score recompute
  24. 2026-10-01 19:46 UTCEG score recomputeFirst assessed: 7.5 HIGH
  25. 2026-10-01 19:45 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  26. 2026-10-01 14:20 UTCNVD update
  27. 2026-10-01 13:31 UTCEG score recompute
  28. 2026-10-01 13:30 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102504?
CVE-2026-102504 is a high-severity vulnerability; its CVE record was published on October 1, 2026. Imager versions before 1.037 for Perl exit the process reading a raw image with an out-of-range raw_datachannels value in i_readraw_wiol. Nothing range-checks raw_datachannels. The line buffer is sized as the image width times the channel count with no overflow check, so a negative or very large…
When was the CVE record for CVE-2026-102504 published?
The CVE record for CVE-2026-102504 was published on October 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 October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-102504 actively exploited?
CVE-2026-102504 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102504?
CVE-2026-102504 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-102504?
A fix for CVE-2026-102504 is available: update to the fixed version the vendor names in its advisory. Fixed versions, as the CVE record's CNA (CPAN Security Group) states them: "Upgrade to Imager 1.037 or later."

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-102504?

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