{"answers":{"affected":"3 open source packages ship an affected version, including pypdf. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-103000 in the wild and no public exploit code.","fix":"Upgrade pypdf to 6.19.0 or later.","what":"CVE-2026-103000 is a high-severity denial of service vulnerability in Pypdf Project Pypdf, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-103000 and fix it if it is affected.\n\nWhat it is: CVE-2026-103000 is a high-severity denial of service vulnerability in Pypdf Project Pypdf, published on 30 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-103000 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pypdf (PyPI): affected all versions; fixed in 6.19.0\n- pypdf (PyPI): affected all versions; fixed in 6.19.0\n- pypdf (PyPI): affected all versions; fixed in 6.19.0\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-103000/ (Markdown: https://insights.sbomify.com/CVE-2026-103000/index.md)","id":"CVE-2026-103000","markdown":"https://insights.sbomify.com/CVE-2026-103000/index.md","name":"CVE-2026-103000","record":{"aliases":["DEBIAN-CVE-2026-103000","ECHO-68fb-d005-2ef4","GHSA-w23x-9jrw-r45c","MINI-239v-rrg2-fvw5","MINI-2r8x-fp7h-53g9","MINI-6vh3-crmj-4r8q","MINI-6xpv-4h6m-f3rc","MINI-7gvq-8h5g-pvq7","MINI-95gq-7fj6-mmq3","MINI-cq2p-64jw-gxv2","MINI-f93m-hv4f-7cr7","MINI-mchr-4gwq-2q73","MINI-pp32-wc6h-xg2x","MINI-q2qm-93jr-p7ff","MINI-q5gc-hxjc-3p9g","MINI-v8jp-3f95-3ww9","MINI-xm45-62h5-q3fm","MINI-xv28-fjh3-w9ww","PYSEC-2026-4160","ROOT-APP-PYPI-CVE-2026-103000","UBUNTU-CVE-2026-103000"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Python PDF library","requires_auth":"none","summary":"Attackers can cause excessive memory consumption and application unavailability by providing crafted PDFs with large alphabetical page labels.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pypdf","vendor":"pypdf_project"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-400","name":"Uncontrolled Resource Consumption"}],"description":"pypdf is a free and open-source pure-python PDF library. Prior to 6.19.0, a crafted PDF can provide unusually large alphabetical page-label values that cause pypdf/_page_labels.py to generate strings beyond a reasonable page-label length when an application retrieves document page labels, consuming excessive memory and potentially making the application unavailable. This issue is fixed in version 6.19.0.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"pypdf: Possible large memory usage when retrieving alphabetical page labels","id":"CVE-2026-103000","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"pypdf_project:pypdf","products":["pypdf_project:pypdf"],"type":"denial_of_service","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"PyJWT.decode() reintroduces options-dict mutation, enabling silent claim-verification bypass on dict reuse","id":"CVE-2026-103001"},"packages":[{"ecosystem":"PyPI","fixed":["6.19.0"],"introduced":["0"],"last_affected":[],"package":"pypdf","purl":null,"source":"GHSA-w23x-9jrw-r45c"},{"ecosystem":"PyPI","fixed":["6.19.0"],"introduced":["0"],"last_affected":[],"package":"pypdf","purl":"pkg:pypi/pypdf","source":"GHSA-w23x-9jrw-r45c"},{"ecosystem":"PyPI","fixed":["6.19.0"],"introduced":["0"],"last_affected":[],"package":"pypdf","purl":"pkg:pypi/pypdf","source":"PYSEC-2026-4160"}],"prev":{"headline":"pypdf: Possible long runtimes with large amount of embedded files","id":"CVE-2026-102999"},"products":["pypdf"],"published":"2026-09-30","related":[{"cvss_score":8.7,"headline":"pypdf: Possible large memory usage when retrieving Roman page labels","id":"CVE-2026-102993","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":8.7,"headline":"pypdf: Possible long runtimes/large memory usage when parsing indirect objects","id":"CVE-2026-102994","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":8.7,"headline":"pypdf: Possible large memory usage for large /ToUnicode streams (Follow-up 2)","id":"CVE-2026-102995","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":8.7,"headline":"pypdf: Possible large memory usage when parsing font data","id":"CVE-2026-102996","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":8.7,"headline":"pypdf: Possible long runtimes for partially malformed FlateDecode streams (Follow-up)","id":"CVE-2026-102997","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":8.7,"headline":"pypdf: Possible long runtimes when generating appearance streams","id":"CVE-2026-102998","kev_date_added":null,"published":"2026-09-30"},{"cvss_score":8.7,"headline":"pypdf: Possible long runtimes with large amount of embedded files","id":"CVE-2026-102999","kev_date_added":null,"published":"2026-09-30"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-30","vendors":["py-pdf"]},"summary":"Attackers can cause excessive memory consumption and application unavailability by providing crafted PDFs with large alphabetical page labels.","url":"https://insights.sbomify.com/CVE-2026-103000/"}