← Back
CVE-2026-54770
medium
CVSS 6.1
Open Redirect in webob (CVE-2026-54770)
Summary
vulnerability in webob (CVE-2026-54770). Risk of unauthorized operations or information disclosure. Exploitable via ``Location``. Mitigation: upgrade to `1.8.11` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-54770** has been found in webob.
Attackers can target a specific entry point like ``Location`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade webob to **1.8.11** or later.
If unsure, ask your IT team or search "webob CVE-2026-54770" on the vendor's site.
CVE-2026-54770 (webob) — CWE-601 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: `Location` / `SCHEME_RE` / `Response.location` / `webob.exc._HTTPMove`
Patched: `1.8.11` — 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** (CWE-601) exists in webob. Attackers reach the vulnerable code path via ``Location`` without authentication.
📍 Affected scope
webob — . Attack surface: `Location` / `SCHEME_RE` / `Response.location` / `webob.exc._HTTPMove`.
🔥 Severity
Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.8.11**.
🛡️ 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 'webob' .` 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
-
1Identify exposure identify
grep -r 'webob' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `webob` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade webob to 1.8.11ステージング環境で 1.8.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
webob
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.8.11"}]}]
References
- web https://github.com/Pylons/webob/commit/ff89560643fb252751b4db8806a283b5377f1f07
- web https://github.com/Pylons/webob/security/advisories/GHSA-6hx8-3wjj-gr8g
- web https://github.com/Pylons/webob/tree/1.8.11
- web https://nvd.nist.gov/vuln/detail/CVE-2026-54770
- web https://github.com/advisories/GHSA-6hx8-3wjj-gr8g