CVE-2026-27888

MEDIUMPre-NVD 6.66.6—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 72% 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: cna:github_m, epss
6.6EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.6Exploit: None knownExposed: 0

A fix is available — apply it.

pypdf is a free and open-source pure-python PDF library. Prior to 6.7.3, an attacker who uses this vulnerability can craft a PDF which leads to the RAM being exhausted. This requires accessing the xfa property of a reader or writer and the corresponding stream being compressed using /FlateDecode. This has been fixed in pypdf 6.7.3. As a workaround, apply the patch manually.

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

Published

February 26, 2026

Last Modified

June 23, 2026

Advisory Details (4)

Auto-updated Aug 4, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
github_release Patch Available

Version 6.7.3, 2026-02-24

Patch available: py-pdf/pypdf 6.7.3

https://github.com/py-pdf/pypdf/releases/tag/6.7.3
github_commit Patch Available

commit 7a4c8246ed48 (py-pdf/pypdf)

Patch available: py-pdf/pypdf 6.7.3 (contains commit 7a4c8246ed48)

https://github.com/py-pdf/pypdf/commit/7a4c8246ed48d9d328fb596942271da47b6d109c
github_pr Patch Available

SEC: Use zlib decompression limit when retrieving XFA data

Patch available: py-pdf/pypdf 6.7.3 (PR #3658 merged 2026-02-24)

https://github.com/py-pdf/pypdf/pull/3658
github Patch Available

Manipulated FlateDecode XFA streams can exhaust RAM · Advisory · py-pdf/pypdf · GitHub

https://github.com/py-pdf/pypdf/security/advisories/GHSA-x7hp-r3qg-r3cj

Vendor Advisories for CVE-2026-27888(1)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17751444032026-04-23redhat

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.2 (91 versions)6.7.3—

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-27888?
CVE-2026-27888 is a medium vulnerability published on February 26, 2026. pypdf is a free and open-source pure-python PDF library. Prior to 6.7.3, an attacker who uses this vulnerability can craft a PDF which leads to the RAM being exhausted. This requires accessing the xfa property of a reader or writer and the corresponding stream being compressed using /FlateDecode.…
When was CVE-2026-27888 disclosed?
CVE-2026-27888 was first published in the National Vulnerability Database on February 26, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-27888 actively exploited?
CVE-2026-27888 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 72.0% of all scored CVEs.
What is the CVSS score of CVE-2026-27888?
CVE-2026-27888 has a CVSS v4.0 base score of 6.6 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-27888?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-27888, 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-27888

Explore →

Is Your Infrastructure Affected by CVE-2026-27888?

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

Start Free Scan →Browse All CVEs