CVE-2026-102994

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3% (27th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-90366 (ENISA EUVD) · GHSA-5jq2-8x83-x246 (GitHub Security Advisories)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.3%CVSS: 7.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pypdf is a free and open-source pure-python PDF library. Prior to 6.18.0, a crafted PDF containing indirect-object identifiers or generation-number tokens that continue for a long time without whitespace can cause pypdf/_reader.py and pypdf/generic/_base.py to scan excessive input through read_until_whitespace, resulting in long runtimes and application unavailability. This issue is fixed in version 6.18.0.

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.3% × 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.3%
EPSS %ILE
27th
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.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

September 30, 2026

Last Modified

October 5, 2026

Advisory Details (4)

Auto-updated Sep 30, 2026
Patch available. Sources: github, github_commit, github_pr, github_release.
GitHub advisoryMentions a patch (unverified)

Possible long runtimes when parsing indirect objects · Advisory · py-pdf/pypdf · GitHub

https://github.com/py-pdf/pypdf/security/advisories/GHSA-5jq2-8x83-x246
GitHub release Patch Available

Version 6.18.0, 2026-09-07

Patch available: py-pdf/pypdf 6.18.0

https://github.com/py-pdf/pypdf/releases/tag/6.18.0
GitHub pull request Patch Available

SEC: Limit allowed length of indirect object tokens

Patch available: py-pdf/pypdf 6.18.0 (PR #4055 merged 2026-09-07)

https://github.com/py-pdf/pypdf/pull/4055
GitHub commit Patch Available

commit 82501d2993c6 (py-pdf/pypdf)

Patch available: py-pdf/pypdf 6.18.0 (contains commit 82501d2993c6)

https://github.com/py-pdf/pypdf/commit/82501d2993c6387833c4949d205caeb188f8bb9e

Vendor Advisories for CVE-2026-102994(2)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatquay/quay-rhel9:17921727152026-10-20redhat
redhatquay/quay-rhel9:17920721282026-10-16redhat
pippypdf @ 6.18.0 (fixes < 6.18.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
pypdf3.17.4-1 ... 6.9.2-2 (15 versions)
  • every version on: no fix on record
—
pypdf22.12.1-3, 2.12.1-3+deb12u1, 2.12.1-4
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
pypdf5.4.0-1, 6.19.0-1, 6.9.0-1, 6.9.2-1, 6.9.2-2
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
pypdf5.4.0-1, 6.9.0-1, 6.9.2-1, 6.9.2-2
  • every version up to 6.19.0-1: fixed in 6.19.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pypdf1.0 ... 6.9.2 (117 versions)
  • every version up to 6.18.0: fixed in 6.18.0
—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 11× in last 7d / 54× 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.3% · 27th percentile
  2. 2026-11-01 08:00 UTCGHSA enrichmentGHSA-5jq2-8x83-x246 · GitHub severity HIGH
  3. 2026-11-01 08:00 UTCEG score recompute
  4. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  5. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  6. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  7. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  8. 2026-10-27 20:29 UTCEG score recompute
  9. 2026-10-27 20:29 UTCVendor advisory
  10. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-10-25 14:56 UTCEG score recompute
  14. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  15. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  16. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  17. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  18. 2026-10-20 19:15 UTCEG score recompute
  19. 2026-10-20 19:15 UTCVendor advisory
  20. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  21. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  22. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  23. 2026-10-18 05:10 UTCEG score recompute
  24. 2026-10-17 19:48 UTCEG score recompute
  25. 2026-10-17 19:48 UTCVendor advisory
Show 37 more
  1. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-12 16:40 UTCEG score recompute
  7. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-11 20:15 UTCEG score recompute
  9. 2026-10-11 18:28 UTCEG score recompute
  10. 2026-10-11 14:20 UTCEG score recompute
  11. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-10-11 01:23 UTCEG score recompute
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-09 23:26 UTCEG score recompute
  15. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  16. 2026-10-08 21:28 UTCEG score recompute
  17. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  18. 2026-10-08 08:28 UTCEG score recompute
  19. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-06 17:28 UTCEG score recompute
  21. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-06 04:31 UTCEG score recompute
  23. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  24. 2026-10-05 15:33 UTCEG score recompute▼ 1.20
  25. 2026-10-05 15:25 UTCNVD updateCVSS v3 → 7.5
  26. 2026-10-05 10:17 UTCEG score recompute
  27. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  28. 2026-10-03 19:25 UTCEG score recompute
  29. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  30. 2026-10-02 17:30 UTCEG score recompute
  31. 2026-10-02 04:33 UTCEG score recompute
  32. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  33. 2026-09-30 21:28 UTCEG score recompute
  34. 2026-09-30 20:56 UTCEG score recompute
  35. 2026-09-30 20:22 UTCEG score recompute
  36. 2026-09-30 20:06 UTCEG score recomputeFirst assessed: 8.7 HIGH
  37. 2026-09-30 20:05 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-102994?
CVE-2026-102994 is a high-severity vulnerability; its CVE record was published on September 30, 2026. pypdf is a free and open-source pure-python PDF library. Prior to 6.18.0, a crafted PDF containing indirect-object identifiers or generation-number tokens that continue for a long time without whitespace can cause pypdf/_reader.py and pypdf/generic/_base.py to scan excessive input through…
When was the CVE record for CVE-2026-102994 published?
The CVE record for CVE-2026-102994 was published on September 30, 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 5, 2026; the record at its source may have been updated since.
Is CVE-2026-102994 actively exploited?
CVE-2026-102994 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-102994?
CVE-2026-102994 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-102994?
A fix for CVE-2026-102994 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-102994 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-102994

Explore →

Is Your Infrastructure Affected by CVE-2026-102994?

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