CVE-2026-33699

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 62% 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
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: None knownExposed: 0

A fix is available — apply it.

pypdf is a free and open-source pure-python PDF library. Versions prior to 6.9.2 have a vulnerability in which an attacker can craft a PDF which leads to an infinite loop. This requires reading a file in non-strict mode. This has been fixed in pypdf 6.9.2. If users cannot upgrade yet, consider applying the changes from the patch manually.

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

Published

March 26, 2026

Last Modified

June 17, 2026

Advisory Details (3)

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

Possible infinite loop during recovery attempts in DictionaryObject.read_from_stream · Advisory · py-pdf/pypdf · GitHub

https://github.com/py-pdf/pypdf/security/advisories/GHSA-87mj-5ggw-8qc3
github_release Patch Available

Version 6.9.2, 2026-03-23

Patch available: py-pdf/pypdf 6.9.2

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

SEC: Avoid infinite loop in read_from_stream for broken files

Patch available: py-pdf/pypdf 6.9.2 (PR #3693 merged 2026-03-23)

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

Vendor Advisories for CVE-2026-33699(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-llama-stack-core-rhel9:17837015982026-07-21redhat
redhatrhoai/odh-llama-stack-core-rhel9:17824715872026-07-09redhat

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-1, 6.9.0-16.9.2-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pypdf1.0 ... 6.9.1 (97 versions)6.9.2—

Weakness Classification(1)

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

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-33699?
CVE-2026-33699 is a high vulnerability published on March 26, 2026. pypdf is a free and open-source pure-python PDF library. Versions prior to 6.9.2 have a vulnerability in which an attacker can craft a PDF which leads to an infinite loop. This requires reading a file in non-strict mode. This has been fixed in pypdf 6.9.2. If users cannot upgrade yet, consider…
When was CVE-2026-33699 disclosed?
CVE-2026-33699 was first published in the National Vulnerability Database on March 26, 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-33699 actively exploited?
CVE-2026-33699 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 61.2% of all scored CVEs.
What is the CVSS score of CVE-2026-33699?
CVE-2026-33699 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-33699?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33699, 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-33699

Explore →

Is Your Infrastructure Affected by CVE-2026-33699?

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

Start Free Scan →Browse All CVEs