Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-102342 medium CVSS 5.4

Cross-Site Scripting (XSS) in ammonia (CVE-2026-102342)

Summary

Cross-site scripting in ammonia (CVE-2026-102342). Risk of unauthorized operations or information disclosure. Exploitable via javascript. Mitigation: upgrade to 3.3.3 or later.

Original description

The description as published by the source.

The following SVG will produce a link with a javascript scheme.
If the user clicks this link, they will run it.


  
    
    Click set

Ammonia did not apply attribute filters based on attributeName,
so the contents of the to, from, and values tags were not sanitized as URLs.

Applications that do not explicitly allow either of these tags should not be affected,
since neither are allowed by default.

Discovered by: Younghun Ko (@koyokr)

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-102342 has been found in ammonia.
Attackers can target a specific entry point like javascript over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.4/10.
What to do: upgrade ammonia to 3.3.3 or later.
If unsure, ask your IT team or search "ammonia CVE-2026-102342" on the vendor's site.

CVE-2026-102342 (ammonia) — CWE-79 / CVSS v3 5.4
Attack vector: remote (network-reachable)
Attack surface: javascript / animate / set
Patched: 3.3.3 — apply immediately
Workaround: Do not enable the animate or set tags.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in ammonia. Attackers reach the vulnerable code path via javascript.

📍 Affected scope

Check the vendor advisory for the affected versions of ammonia. Attack surface: javascript / animate / set.

🔥 Severity

Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.3.3.

🛡️ Workaround

Workaround: Do not enable the animate or set tags.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'ammonia' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'ammonia' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で ammonia を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    Do not enable the `animate` or `set` tags.

    パッチが適用されるまでの応急処置として、Do not enable the animate or set tags. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade ammonia to 3.3.3

    ステージング環境で 3.3.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

rust ammonia
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.1.4"}]}]
crates.io ammonia
[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"3.3.3"},{"introduced":"4.0.0"},{"fixed":"4.0.3"},{"introduced":"4.1.0"},{"fixed":"4.1.4"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details