GHSA-mm7x-qfjj-5g2c — ammonia
Fix: rust-ammonia/ammonia@de02971GHSA-mm7x-qfjj-5g2c is a security vulnerability in ammonia. A fix is available for ammonia — see the affected versions and patch details below.
Ammonia incorrectly handles embedded SVG and MathML leading to mutation XSS after removal
Real-World Exposure
ammonia🦀ammonia🦀ammoniaReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Affected versions of this crate did not correctly strip namespace-incompatible tags in certain situations, causing it to incorrectly account for differences between HTML, SVG, and MathML.
This vulnerability only has an effect when the svg or math tag is allowed,
because it relies on a tag being parsed as html during the cleaning process, but
serialized in a way that causes in to be parsed as xml by the browser.
Additionally, the application using this library must allow a tag that is parsed as raw text in HTML. These elements are:
- title
- textarea
- xmp
- iframe
- noembed
- noframes
- plaintext
- noscript
- style
- script
Applications that do not explicitly allow any of these tags should not be affected, since none are allowed by default.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | ammonia | ≥ 4.1.0&&< 4.1.2 | 4.1.2cargo update -p ammonia --precise 4.1.2 |
| 🦀crates.io | ammonia | ≥ 4.0.0&&< 4.0.1 | 4.0.1cargo update -p ammonia --precise 4.0.1 |
| 🦀crates.io | ammonia | all versions | 3.3.1cargo update -p ammonia --precise 3.3.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ammonia, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update ammonia to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm7x-qfjj-5g2c is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mm7x-qfjj-5g2c can be triaged on real exposure rather than presence alone.
Tailored to GHSA-mm7x-qfjj-5g2c. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-mm7x-qfjj-5g2c in your dependencies?
O3 Security finds GHSA-mm7x-qfjj-5g2c across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.