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.
CVE-2026-33699
MEDIUMNVD 7.54.6Trending — 3 sources updated this week
EchelonGraph scoreLOW confidence
This medium-severity CVE scores 4.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). 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
4.6EG
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.
- CVSS v3
- 7.5
- EG Score
- 4.6(low)
- EG Risk
- 21(Track)EG Risk 21/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 computedSeverity46% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 37%
- KEV
- Not listed
Published
March 26, 2026
Last Modified
June 17, 2026
References (3)
- security-advisories@githubhttps://github.com/py-pdf/pypdf/pull/3693
- security-advisories@githubhttps://github.com/py-pdf/pypdf/releases/tag/6.9.2
- security-advisories@githubhttps://github.com/py-pdf/pypdf/security/advisories/GHSA-87mj-5ggw-8qc3
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 / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | rhoai/odh-llama-stack-core-rhel9:1783701598 | 2026-07-21 | redhat |
| redhat | rhoai/odh-llama-stack-core-rhel9:1782471587 | 2026-07-09 | redhat |
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
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| pypdf | 1.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 3× in last 7d / 3× 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.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:50 UTCEG score recompute
- 2026-07-27 12:50 UTCVendor advisory
Frequently asked(5)
What is CVE-2026-33699?
CVE-2026-33699 is a medium 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 62.9% 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). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 4.6. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
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
Is Your Infrastructure Affected by CVE-2026-33699?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.