Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-40258

Path Traversal in gramps-webapi (CVE-2026-40258)

Summary

path traversal in gramps-webapi (CVE-2026-40258). Successful exploitation can lead to full system takeover. Exploitable via ``zipfile``. Mitigation: upgrade to `3.11.1` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-40258** has been found in gramps-webapi. Attackers can target a specific entry point like ``zipfile`` over the network to misuse the product. Successful exploitation can lead to full system takeover. CVSS score: ?/10. What to do: upgrade gramps-webapi to **3.11.1** or later. If unsure, ask your IT team or search "gramps-webapi CVE-2026-40258" on the vendor's site.
CVE-2026-40258 (gramps-webapi) — CWE-22 / Attack vector: remote (network-reachable) / no user interaction Attack surface: `zipfile` Patched: `3.11.1` — 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
**Path traversal** (CWE-22) exists in gramps-webapi. Attackers reach the vulnerable code path via ``zipfile`` without authentication.
📍 Affected scope
gramps-webapi — . Attack surface: `zipfile`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **3.11.1**.
🛡️ 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 'gramps-webapi' .` 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 'gramps-webapi' . | grep -v node_modules

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

  2. 6
    Apply patch patch 
    Upgrade gramps-webapi to 3.11.1

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

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

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

Affected packages

PyPI gramps-webapi
[{"type":"ECOSYSTEM","events":[{"introduced":"1.6.0"},{"fixed":"3.11.1"}]}]

References

🍪 About cookies

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

Details →