{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119203 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-119203 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119203 is a high-severity vulnerability in py-pdf pypdf, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119203 and fix it if it is affected.\n\nWhat it is: CVE-2026-119203 is a high-severity vulnerability in py-pdf pypdf, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119203 in the wild and no public exploit code.\n\nAffected product: py-pdf pypdf. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-119203/ (Markdown: https://insights.sbomify.com/CVE-2026-119203/index.md)","id":"CVE-2026-119203","markdown":"https://insights.sbomify.com/CVE-2026-119203/index.md","name":"CVE-2026-119203","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"pypdf is a free and open-source pure-python PDF library. Prior to 6.21.4, pypdf can enter an infinite loop while opening a crafted incomplete PDF whose standard cross-reference table reaches the end of the file without a trailer. The trailer search can repeatedly rewind to the same stream position instead of terminating when parsing makes no progress, blocking the processing thread. This issue is fixed in version 6.21.4.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"pypdf: Possible infinite loop when hitting EOF in standard xref table during trailer search","id":"CVE-2026-119203","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"pypdf: Possible large memory usage when parsing page tree","id":"CVE-2026-119204"},"packages":[],"prev":{"headline":"@hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service","id":"CVE-2026-119202"},"products":["pypdf"],"published":"2026-10-29","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-29","vendors":["py-pdf"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119203/"}