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

Path Traversal in wisp (CVE-2026-28807)

Summary

path traversal in wisp (CVE-2026-28807). Confidential information can be exposed externally. Exploitable via ``wisp.serve_static``. Mitigation: upgrade to `2.2.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-28807** has been found in wisp. Attackers can target a specific entry point like ``wisp.serve_static`` over the network to misuse the product. Confidential information can be exposed externally. CVSS score: 7.5/10. What to do: upgrade wisp to **2.2.1** or later. If unsure, ask your IT team or search "wisp CVE-2026-28807" on the vendor's site.
CVE-2026-28807 (wisp) — CWE-22 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `wisp.serve_static` / `serve_static` / `string.replace` / `uri.percent_decode` Patched: `2.2.1` — apply immediately Workaround: Copy the [fixed implementation](https://github.com/gleam-wisp/wisp/blob/161118c431047f7ef1ff7cabfcc38981877fdd93/src/wisp.gleam#L1413-L1461) to your codebase and replace references to wisp.serve_static with this version in your codebase. 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
**Path traversal** (CWE-22) exists in wisp. Attackers reach the vulnerable code path via ``wisp.serve_static`` without authentication.
📍 Affected scope
wisp — . Attack surface: `wisp.serve_static` / `serve_static` / `string.replace` / `uri.percent_decode`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **2.2.1**.
🛡️ Workaround
Workaround: Copy the [fixed implementation](https://github.com/gleam-wisp/wisp/blob/161118c431047f7ef1ff7cabfcc38981877fdd93/src/wisp.gleam#L1413-L1461) to your codebase and replace references to wisp.serve_static with this version in your codebase.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'wisp' .` 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 'wisp' . | grep -v node_modules

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

  2. 5
    Apply temporary workaround mitigate 
    Copy the [fixed implementation](https://github.com/gleam-wisp/wisp/blob/161118c431047f7ef1ff7cabfcc38981877fdd93/src/wisp.gleam#L1413-L1461) to your codebase and replace references to wisp.serve_static with this version in your codebase.

    パッチが適用されるまでの応急処置として、Copy the [fixed implementation](https://github.com/gleam-wisp/wisp/blob/161118c431047f7ef1ff7cabfcc38981877fdd93/src/wisp.gleam#L1413-L1461) to your codebase and replace references to wisp.serve_static with this version in your codebase. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 6
    Apply patch patch 
    Upgrade wisp to 2.2.1

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

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

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

Affected packages

erlang wisp
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.2.1"}]}]
Hex wisp
[{"type":"SEMVER","events":[{"introduced":"2.1.1"},{"fixed":"2.2.1"}]}]

References

🍪 About cookies

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

Details →