Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-6322 high CVSS 7.5

Vulnerability in fast-uri (CVE-2026-6322)

Summary

vulnerability in fast-uri (CVE-2026-6322). Data can be tampered with by attackers. Exploitable via ``evil.com``. Mitigation: upgrade to `2.4.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-6322** has been found in fast-uri. Attackers can target a specific entry point like ``evil.com`` over the network to misuse the product. Data can be tampered with by attackers. CVSS score: 7.5/10. What to do: upgrade fast-uri to **2.4.1** or later. If unsure, ask your IT team or search "fast-uri CVE-2026-6322" on the vendor's site.
CVE-2026-6322 (fast-uri) — CWE-140 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `evil.com` / `trusted.com` Patched: `2.4.1` — apply immediately Workaround: None. 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
**A vulnerability** (CWE-140) exists in fast-uri. Attackers reach the vulnerable code path via ``evil.com`` without authentication.
📍 Affected scope
fast-uri — . Attack surface: `evil.com` / `trusted.com`.
🔥 Severity
Severity: High (CVSS 7.5/10). Data can be tampered with by attackers
🔧 How to fix
Update to **2.4.1**.
🛡️ Workaround
Workaround: None.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'fast-uri' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

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

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

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

  2. 5
    Apply temporary workaround mitigate 
    None.

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

  3. 6
    Apply patch patch 
    Upgrade fast-uri to 2.4.1

    ステージング環境で 2.4.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

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

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

Affected packages

npm fast-uri
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.4.1"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →