{"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-82398 in the wild and no public exploit code.","fix":"Upgrade pypdf to 6.15.0 or later.","what":"CVE-2026-82398 is a medium-severity denial of service vulnerability in Pypdf Project Pypdf, published on 31 Aug 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-82398 and fix it if it is affected.\n\nWhat it is: CVE-2026-82398 is a medium-severity denial of service vulnerability in Pypdf Project Pypdf, published on 31 Aug 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-82398 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pypdf (PyPI): affected all versions; fixed in 6.15.0\n- pypdf (PyPI): affected all versions; fixed in 6.15.0\n- pypdf (PyPI): affected all versions; fixed in 6.15.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-82398/ (Markdown: https://insights.sbomify.com/CVE-2026-82398/index.md)","id":"CVE-2026-82398","markdown":"https://insights.sbomify.com/CVE-2026-82398/index.md","name":"CVE-2026-82398","record":{"aliases":["DEBIAN-CVE-2026-82398","ECHO-c915-e406-2ed8","GHSA-fc8x-2rww-xw9m","MINI-23q6-fmm3-frpw","MINI-59wp-mq5w-qpfr","MINI-74jr-8vc8-jx3c","MINI-85rm-rh33-r88v","MINI-988x-h7c2-88jv","MINI-9q38-3j58-7gvc","MINI-g83q-rm6g-7p4w","MINI-jp5p-fw6f-mg5r","MINI-m4xr-4x2v-rg97","MINI-mc5q-4hcx-7c9j","MINI-q5x2-9xcj-hvm8","MINI-qp5w-j8gp-w9wg","MINI-r9gg-8863-fwmj","MINI-v75v-c79q-h5q6","MINI-vp26-g868-f8qx","PYSEC-2026-3912","UBUNTU-CVE-2026-82398"],"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":"An attacker can cause denial of service in pypdf by crafting a PDF with long non-whitespace sequences, leading to excessive CPU consumption.","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":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-407","name":"Inefficient Algorithmic Complexity"}],"description":"pypdf is a free and open-source pure-python PDF library. Prior to 6.15.0, an attacker can craft a PDF that causes long runtimes when the pypdf/_utils.py function read_until_whitespace reads a stream containing a long run of bytes without whitespace. The function repeatedly performs immutable bytes concatenation in a one-byte loop, causing quadratic processing cost for the long non-whitespace input. This issue is fixed in version 6.15.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: Inefficient handling of non-whitespace inputs in read_until_whitespace","id":"CVE-2026-82398","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":"CoreDNS: Unauthenticated memory exhaustion in custom transports","id":"CVE-2026-82399"},"packages":[{"ecosystem":"PyPI","fixed":["6.15.0"],"introduced":["0"],"last_affected":[],"package":"pypdf","purl":null,"source":"GHSA-fc8x-2rww-xw9m"},{"ecosystem":"PyPI","fixed":["6.15.0"],"introduced":["0"],"last_affected":[],"package":"pypdf","purl":"pkg:pypi/pypdf","source":"GHSA-fc8x-2rww-xw9m"},{"ecosystem":"PyPI","fixed":["6.15.0"],"introduced":["0"],"last_affected":[],"package":"pypdf","purl":"pkg:pypi/pypdf","source":"PYSEC-2026-3912"}],"prev":{"headline":"Tornado: Urlencoded body parsing omits max_num_fields, so one request can stall the event loop","id":"CVE-2026-82397"},"products":["pypdf"],"published":"2026-08-31","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-01","vendors":["py-pdf"]},"summary":"An attacker can cause denial of service in pypdf by crafting a PDF with long non-whitespace sequences, leading to excessive CPU consumption.","url":"https://insights.sbomify.com/CVE-2026-82398/"}