{"answers":{"affected":"1 open source package ship an affected version, including rails-html-sanitizer.","exploited":"There is no known exploitation of CVE-2026-128069 in the wild and no public exploit code.","exposure":"","fix":"Upgrade rails-html-sanitizer to 1.7.2 or later.","what":"CVE-2026-128069 is a medium-severity vulnerability in rails-html-sanitizer, published on 13 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-128069 and fix it if it is affected.\n\nWhat it is: CVE-2026-128069 is a medium-severity vulnerability in rails-html-sanitizer, published on 13 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-128069 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- rails-html-sanitizer (RubyGems): affected all versions; fixed in 1.7.2\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-128069/ (Markdown: https://insights.sbomify.com/CVE-2026-128069/index.md)","id":"CVE-2026-128069","markdown":"https://insights.sbomify.com/CVE-2026-128069/index.md","name":"CVE-2026-128069","record":{"aliases":["DEBIAN-CVE-2026-128069","DHI-ihec-5yjq-yemi-ynqz","GHSA-h7wh-q2qr-458c","UBUNTU-CVE-2026-128069"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":4.7,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"},{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"rails-html-sanitizer is responsible for sanitizing HTML fragments in Rails applications. Before 1.7.2, the HTML4 and HTML5 variants of Rails::HTML::SafeListSanitizer reuse one Rails::HTML::PermitScrubber across calls and mutate its tags and attributes without synchronization. In a multithreaded process, concurrent sanitize calls using different tags: or attributes: options can interleave and cause one call to use the other call's allowlist. If a permissive call admits a script element or event-handler attribute, output expected to be sanitized under a stricter policy can retain it and cause cross-site scripting when rendered. Applications that are single-threaded, use one identical allowlist everywhere, or provide a separate scrubber: are not affected. This issue is fixed in version 1.7.2.","ecosystems":["RubyGems"],"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":"rails-html-sanitizer: Possible XSS via shared scrubber state in concurrent calls","id":"CVE-2026-128069","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":null,"year":"2026"},"n_packages":1,"n_references":4,"n_vendor_status":1,"next":{"headline":"Nuxt dev server serves files from a parent directory that contains a lockfile","id":"CVE-2026-128070"},"nickname":null,"packages":[{"ecosystem":"RubyGems","fixed":["1.7.2"],"introduced":["0"],"last_affected":[],"name_kind":null,"package":"rails-html-sanitizer","purl":"pkg:gem/rails-html-sanitizer","purl_source":"derived","scope":"upstream","source":"GHSA-h7wh-q2qr-458c"}],"prev":{"headline":"rails-html-sanitizer: Possible regular expression denial of service with certain configurations","id":"CVE-2026-128068"},"products":["rails-html-sanitizer"],"published":"2026-11-13","related":[],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-11-18","vendor_status":[{"n_packages":1,"name":"Upstream","packages":[{"fixed":["1.7.2"],"name":"rails-html-sanitizer","purl":"pkg:gem/rails-html-sanitizer","sources":["GHSA-h7wh-q2qr-458c"],"status":"fixed"}],"release":null,"scope":"upstream","status":"fixed","statuses":{"fixed":1},"vendor":null}],"vendors":["rails"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-128069/"}