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.6%CVSS: 6.6Exploit: 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.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.6MEDIUMmedium confidence
EG Risk
45
EG Risk 45/100

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%
EPSS PROB
0.6%
EPSS %ILE
49th
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 / EcosystemFix (by version range) / 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 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:11(1)
PackageVulnerable rangeFix by version rangeDependents
pypdf21.26.0-4 ... 2.9.0-1 (24 versions)
  • 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
  • every version up to 6.9.0-1: fixed in 6.9.0-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pypdf1.0 ... 6.7.2 (91 versions)
  • every version up to 6.7.3: fixed in 6.7.3
—

Weakness Classification(1)

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

Data Freshness Timeline

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

Showing the most recent 100 of 131 total refreshes for this CVE.

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

Related CVEs(same product + 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 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.6% probability of exploitation in the next 30 days (49th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-27888?
CVE-2026-27888 has a CVSS base score of 6.6 (the CNA's own assessment, by github_m; NVD's own analysis pending).
How do I remediate CVE-2026-27888?
A fix for CVE-2026-27888 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-27888 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-27888

Explore →

Is Your Infrastructure Affected by CVE-2026-27888?

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

Book a Demo →Browse All CVEs