CVE-2026-27628

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.5Exploit: Elevated riskExposed: 0

A fix is available — apply it.

pypdf is a free and open-source pure-python PDF library. Prior to 6.7.2, an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires reading the file. This has been fixed in pypdf 6.7.2. As a workaround, one may apply the patch manually.

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
50(Track)
EG Risk 50/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 computed
Severity75% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
28%
KEV
Not listed

Published

February 25, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
Patch available. Sources: github, github_commit.
generic

BUG: Infinite loop from circular /Prev xref references · Issue #3654 · py-pdf/pypdf · GitHub

https://github.com/py-pdf/pypdf/issues/3654
github Patch Available

Possible infinite loop when loading circular /Prev entries in cross-reference streams · Advisory · py-pdf/pypdf · GitHub

https://github.com/py-pdf/pypdf/security/advisories/GHSA-2rw7-x74f-jg35
github_commit Patch Available

commit f0a462d36971 (py-pdf/pypdf)

Patch available: py-pdf/pypdf 6.7.2 (contains commit f0a462d36971)

https://github.com/py-pdf/pypdf/commit/f0a462d36971cf077d74492a348d0d06fd60ea4d

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17751444032026-04-23redhat
redhatquay/quay-rhel8:17751692192026-04-03redhat
redhatquay/quay-rhel9:17751692262026-04-03redhat
redhatquay/quay-rhel9:17750694912026-04-02redhat
redhatquay/quay-rhel8:17739710772026-03-24redhat
redhatquay/quay-rhel8:17739363232026-03-19redhat
redhatquay/quay-rhel8:17737719622026-03-18redhat

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

(6 across 5 ecosystems)
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypdf3.17.4-1 ... 6.9.2-2 (14 versions)
pypdf22.12.1-3, 2.12.1-3+deb12u1, 2.12.1-4
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pypdf21.26.0-4 ... 2.9.0-1 (24 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pypdf5.4.0-1, 6.9.0-1, 6.9.2-1, 6.9.2-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pypdf5.4.0-16.9.0-1
PyPI(1)
PackageVulnerable rangeFixed inDependents
pypdf1.0 ... 6.7.1 (90 versions)6.7.2

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-31 17:04 UTCOSV refresh
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-30 01:22 UTCEPSS rescore
  21. 2026-08-28 21:41 UTCEPSS rescore
  22. 2026-08-27 14:25 UTCEPSS rescore
  23. 2026-08-26 14:46 UTCEPSS rescore
  24. 2026-08-25 13:48 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 49 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-18 13:48 UTCEPSS rescore
  5. 2026-08-17 13:47 UTCEPSS rescore
  6. 2026-08-16 14:56 UTCEPSS rescore
  7. 2026-08-16 02:14 UTCEPSS rescore
  8. 2026-08-15 01:30 UTCEPSS rescore
  9. 2026-08-14 21:27 UTCVendor advisory
  10. 2026-08-14 09:04 UTCEG score recompute
  11. 2026-08-14 09:04 UTCVendor advisory
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-13 01:04 UTCEG score recompute
  14. 2026-08-13 01:04 UTCVendor advisory
  15. 2026-08-12 13:50 UTCEPSS rescore
  16. 2026-08-12 00:48 UTCEG score recompute
  17. 2026-08-12 00:48 UTCVendor advisory
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 06:29 UTCEG score recompute
  20. 2026-08-11 06:29 UTCVendor advisory
  21. 2026-08-11 00:00 UTCEPSS rescore
  22. 2026-08-10 09:06 UTCVendor advisory
  23. 2026-08-09 20:54 UTCEG score recompute
  24. 2026-08-09 20:54 UTCVendor advisory
  25. 2026-08-09 13:46 UTCEPSS rescore
  26. 2026-08-09 08:42 UTCEG score recompute
  27. 2026-08-09 08:42 UTCVendor advisory
  28. 2026-08-08 16:37 UTCEPSS rescore
  29. 2026-08-08 08:58 UTCVendor advisory
  30. 2026-08-07 20:47 UTCEG score recompute
  31. 2026-08-07 20:47 UTCVendor advisory
  32. 2026-08-06 13:46 UTCEPSS rescore
  33. 2026-08-06 03:03 UTCEG score recompute
  34. 2026-08-06 03:03 UTCVendor advisory
  35. 2026-08-05 19:17 UTCEPSS rescore
  36. 2026-08-04 15:10 UTCEPSS rescore
  37. 2026-08-04 05:56 UTCEG score recompute
  38. 2026-08-04 05:56 UTCVendor advisory
  39. 2026-08-03 10:36 UTCEPSS rescore
  40. 2026-08-02 19:38 UTCEG score recompute 6.30
  41. 2026-08-02 19:38 UTCVendor advisory
  42. 2026-08-02 02:26 UTCEPSS rescore
  43. 2026-08-01 04:16 UTCEPSS rescore
  44. 2026-07-30 16:27 UTCEPSS rescore
  45. 2026-07-30 01:30 UTCEPSS rescore
  46. 2026-07-28 15:36 UTCEPSS rescore
  47. 2026-07-27 12:55 UTCEG score recompute
  48. 2026-07-27 12:55 UTCVendor advisory
  49. 2026-07-27 12:50 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-27628?
CVE-2026-27628 is a high vulnerability published on February 25, 2026. pypdf is a free and open-source pure-python PDF library. Prior to 6.7.2, an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires reading the file. This has been fixed in pypdf 6.7.2. As a workaround, one may apply the patch manually.
When was CVE-2026-27628 disclosed?
CVE-2026-27628 was first published in the National Vulnerability Database on February 25, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27628 actively exploited?
CVE-2026-27628 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 71.8% of all scored CVEs.
What is the CVSS score of CVE-2026-27628?
CVE-2026-27628 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-27628?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27628, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-27628?

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