← Back
RUSTSEC-2026-0198

Vulnerability in error-stack (RUSTSEC-2026-0198)

Summary

vulnerability in error-stack (RUSTSEC-2026-0198). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `0.8.0` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **RUSTSEC-2026-0198** has been found in error-stack. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade error-stack to **0.8.0** or later. If unsure, ask your IT team or search "error-stack RUSTSEC-2026-0198" on the vendor's site.
RUSTSEC-2026-0198 (error-stack) — Patched: `0.8.0` — apply immediately 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** (unclassified) exists in error-stack.
📍 Affected scope
error-stack — .
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.8.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'error-stack' .` 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 'error-stack' . | grep -v node_modules

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

  2. 6
    Apply patch patch
    Upgrade error-stack to 0.8.0

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

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

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

Affected packages

crates.io error-stack
[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.8.0"}]}]

References

🍪 About cookies

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

Details →