{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119202 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-119202 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119202 is a high-severity vulnerability in hapijs content, published on 29 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119202 and fix it if it is affected.\n\nWhat it is: CVE-2026-119202 is a high-severity vulnerability in hapijs content, published on 29 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119202 in the wild and no public exploit code.\n\nAffected product: hapijs content. 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-119202/ (Markdown: https://insights.sbomify.com/CVE-2026-119202/index.md)","id":"CVE-2026-119202","markdown":"https://insights.sbomify.com/CVE-2026-119202/index.md","name":"CVE-2026-119202","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-1333","name":"Inefficient Regular Expression Complexity"}],"description":"@hapi/content provides HTTP Content-* header parsing. From 3.0.6 until 6.0.3, Content.disposition() uses an unanchored parameter-name expression in a global regular-expression scan, causing repeated failed matching over the remaining input when a Content-Disposition parameter contains a long token without an equals sign. The resulting quadratic processing can block the Node.js event loop before route handlers or validation when @hapi/pez parses multipart/form-data headers, including unauthenticated hapi routes with payload.multipart enabled, and also affects applications that pass untrusted headers directly to Content.disposition(). This issue is fixed in @hapi/content version 6.0.3.","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":"@hapi/content: quadratic-time parsing of Content-Disposition parameters allows denial of service","id":"CVE-2026-119202","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"pypdf: Possible infinite loop when hitting EOF in standard xref table during trailer search","id":"CVE-2026-119203"},"packages":[],"prev":{"headline":"Nuxt dev server exposes generated appSecret through Vite file serving","id":"CVE-2026-119201"},"products":["content"],"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":["hapijs"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119202/"}