CVE-2026-54651

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 99% 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
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

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

pypdf is a free and open-source pure-python PDF library. Prior to 6.13.1, an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires merging a file with threads/articles into a writer. This vulnerability is fixed in 6.13.1.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
25(Track)
EG Risk 25/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
Severity55% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

June 22, 2026

Last Modified

June 24, 2026

Advisory Details (3)

Auto-updated Jun 22, 2026
Patch available. Sources: github_pr, github_release, github.
github Patch Available

Possible infinite loop when processing threads/articles in writer · Advisory · py-pdf/pypdf · GitHub

https://github.com/py-pdf/pypdf/security/advisories/GHSA-g9xf-7f8q-9mcj
github_release Patch Available

Version 6.13.1, 2026-06-08

Patch available: py-pdf/pypdf 6.13.1

https://github.com/py-pdf/pypdf/releases/tag/6.13.1
github_pr Patch Available

SEC: Prevent infinite loops when processing threads/articles

Patch available: py-pdf/pypdf 6.13.1 (PR #3839 merged 2026-06-08)

https://github.com/py-pdf/pypdf/pull/3839

Vendor Advisories for CVE-2026-54651(1)

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

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-1, 6.9.0-1, 6.9.2-1, 6.9.2-2——
PyPI(1)
PackageVulnerable rangeFixed inDependents
pypdf1.0 ... 6.9.2 (106 versions)6.13.1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 41× 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-08-26 14:46 UTCEPSS rescore
  2. 2026-08-25 13:49 UTCEPSS rescore
  3. 2026-08-24 13:55 UTCEG score recompute
  4. 2026-08-23 12:42 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 05:35 UTCEG score recompute
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 07:50 UTCEG score recompute
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-19 04:51 UTCEG score recompute
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 14:58 UTCEG score recompute
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 02:14 UTCEPSS rescore
  16. 2026-08-15 17:13 UTCEG score recompute
  17. 2026-08-15 01:30 UTCEPSS rescore
  18. 2026-08-14 19:25 UTCEG score recompute
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-12 01:53 UTCEG score recompute
  21. 2026-08-11 04:08 UTCEG score recompute
  22. 2026-08-11 00:00 UTCEPSS rescore
  23. 2026-08-10 06:22 UTCEG score recompute
  24. 2026-08-09 13:46 UTCEPSS rescore
  25. 2026-08-09 08:37 UTCEG score recompute
Show 66 more
  1. 2026-08-08 16:37 UTCEPSS rescore
  2. 2026-08-08 10:52 UTCEG score recompute
  3. 2026-08-06 15:21 UTCEG score recompute
  4. 2026-08-06 13:47 UTCEPSS rescore
  5. 2026-08-05 19:17 UTCEPSS rescore
  6. 2026-08-04 15:16 UTCEG score recompute
  7. 2026-08-04 15:10 UTCEPSS rescore
  8. 2026-08-04 10:39 UTCEPSS rescore
  9. 2026-08-03 15:39 UTCEG score recompute
  10. 2026-08-03 10:36 UTCEPSS rescore
  11. 2026-08-01 20:08 UTCEG score recompute
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-31 00:30 UTCEG score recompute
  14. 2026-07-30 16:28 UTCEPSS rescore
  15. 2026-07-29 01:21 UTCEG score recompute
  16. 2026-07-28 15:37 UTCEPSS rescore
  17. 2026-07-26 15:58 UTCEG score recompute
  18. 2026-07-25 14:18 UTCEPSS rescore
  19. 2026-07-24 14:18 UTCEPSS rescore
  20. 2026-07-23 14:18 UTCEPSS rescore
  21. 2026-07-23 03:19 UTCEG score recompute
  22. 2026-07-22 14:08 UTCEPSS rescore
  23. 2026-07-21 15:25 UTCEPSS rescore
  24. 2026-07-20 17:08 UTCEPSS rescore
  25. 2026-07-19 14:31 UTCEPSS rescore
  26. 2026-07-19 14:31 UTCEPSS rescore
  27. 2026-07-19 02:29 UTCEPSS rescore
  28. 2026-07-18 10:04 UTCEPSS rescore
  29. 2026-07-16 17:03 UTCEPSS rescore
  30. 2026-07-15 16:57 UTCEPSS rescore
  31. 2026-07-15 16:57 UTCEPSS rescore
  32. 2026-07-13 22:31 UTCEPSS rescore
  33. 2026-07-13 06:13 UTCEPSS rescore
  34. 2026-07-13 06:13 UTCEPSS rescore
  35. 2026-07-11 08:27 UTCEPSS rescore
  36. 2026-07-11 08:27 UTCEPSS rescore
  37. 2026-07-09 19:10 UTCEPSS rescore
  38. 2026-07-09 19:10 UTCEPSS rescore
  39. 2026-07-08 15:16 UTCEPSS rescore
  40. 2026-07-08 15:16 UTCEPSS rescore
  41. 2026-07-07 13:46 UTCEPSS rescore
  42. 2026-07-07 13:46 UTCEPSS rescore
  43. 2026-07-06 16:27 UTCEPSS rescore
  44. 2026-07-06 16:27 UTCEPSS rescore
  45. 2026-07-06 02:23 UTCEPSS rescore
  46. 2026-07-06 02:23 UTCEPSS rescore
  47. 2026-07-05 02:31 UTCEPSS rescore
  48. 2026-07-05 02:30 UTCEPSS rescore
  49. 2026-07-04 06:31 UTCEPSS rescore
  50. 2026-07-04 06:31 UTCEPSS rescore
  51. 2026-07-01 15:07 UTCEPSS rescore
  52. 2026-06-30 23:22 UTCEPSS rescore
  53. 2026-06-29 14:06 UTCEPSS rescore
  54. 2026-06-29 14:06 UTCEPSS rescore
  55. 2026-06-28 14:07 UTCEPSS rescore
  56. 2026-06-28 04:56 UTCEPSS rescore
  57. 2026-06-28 04:56 UTCEPSS rescore
  58. 2026-06-27 03:08 UTCEPSS rescore
  59. 2026-06-25 14:59 UTCEG score recompute▼ 1.40
  60. 2026-06-25 13:49 UTCEPSS rescore
  61. 2026-06-24 18:02 UTCNVD updateCVSS v3 → 5.5
  62. 2026-06-24 14:05 UTCEPSS rescore
  63. 2026-06-23 21:33 UTCEPSS rescore
  64. 2026-06-23 21:33 UTCEPSS rescore
  65. 2026-06-22 21:38 UTCEG score recompute
  66. 2026-06-22 21:37 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-54651?
CVE-2026-54651 is a medium vulnerability published on June 22, 2026. pypdf is a free and open-source pure-python PDF library. Prior to 6.13.1, an attacker who uses this vulnerability can craft a PDF which leads to an infinite loop. This requires merging a file with threads/articles into a writer. This vulnerability is fixed in 6.13.1.
When was CVE-2026-54651 disclosed?
CVE-2026-54651 was first published in the National Vulnerability Database on June 22, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-54651 actively exploited?
CVE-2026-54651 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 94.8% of all scored CVEs.
What is the CVSS score of CVE-2026-54651?
CVE-2026-54651 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-54651?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-54651, 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-54651

Explore →

Is Your Infrastructure Affected by CVE-2026-54651?

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

Start Free Scan →Browse All CVEs