{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-117540 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-117540 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-117540 is a high-severity vulnerability in darylldoyle svg-sanitizer, published on 27 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-117540 and fix it if it is affected.\n\nWhat it is: CVE-2026-117540 is a high-severity vulnerability in darylldoyle svg-sanitizer, published on 27 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-117540 in the wild and no public exploit code.\n\nAffected product: darylldoyle svg-sanitizer. 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-117540/ (Markdown: https://insights.sbomify.com/CVE-2026-117540/index.md)","id":"CVE-2026-117540","markdown":"https://insights.sbomify.com/CVE-2026-117540/index.md","name":"CVE-2026-117540","record":{"aliases":["GHSA-2v7c-jx29-jprp","GHSA-5fhv-8j9p-2v94"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"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-407","name":"Inefficient Algorithmic Complexity"}],"description":"svg-sanitizer from 0.5.3 before 1.1.0 contains a denial of service vulnerability in Sanitizer::sanitize() that repeatedly rescans the whole input while stripping PHP tags. Unauthenticated attackers can upload SVGs with many overlapping PHP tag openers and closers, forcing quadratic preg_replace passes that exhaust worker CPU for minutes.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"svg-sanitizer before 1.1.0 Quadratic CPU-Exhaustion DoS via PHP-Tag Stripping Loop","id":"CVE-2026-117540","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"svg-sanitizer 0.11.0 before 1.1.0 Uncaught LogicException DoS via sanitize()","id":"CVE-2026-117541"},"packages":[],"prev":{"headline":"darylldoyle svg-sanitizer before 1.0.0 CSS Injection and Remote Reference Bypass","id":"CVE-2026-117539"},"products":["svg-sanitizer"],"published":"2026-10-27","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-27","vendors":["darylldoyle"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-117540/"}