CVE-2026-119209 pypdf: Possible large memory usage when parsing cross-reference streams
High 7.1
Published
Updated
Check this codebase for CVE-2026-119209 and fix it if it is affected.
What it is: CVE-2026-119209 is a high-severity vulnerability in py-pdf pypdf, published on 29 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119209 in the wild and no public exploit code.
Affected product: py-pdf pypdf. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-119209/ (Markdown: https://insights.sbomify.com/CVE-2026-119209/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119209?
CVE-2026-119209 is a high-severity vulnerability in py-pdf pypdf, published on 29 Oct 2026.
Official description
pypdf is a free and open-source pure-python PDF library. Prior to 6.21.3, pypdf can consume excessive memory while opening a crafted PDF containing cross-reference streams that declare very large entry counts. Highly compressible streams and /Prev chains can multiply the number of parsed entries across a document, while negative /Index counts can bypass the existing per-stream clamp. This issue is fixed in version 6.21.3.
Which versions are affected by CVE-2026-119209?
How do I fix CVE-2026-119209?
No fix has been published for CVE-2026-119209 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119209 being exploited?
There is no known exploitation of CVE-2026-119209 in the wild and no public exploit code.