← Back
CVE-2025-32962
Open Redirect in flask-appbuilder (CVE-2025-32962)
Summary
vulnerability in flask-appbuilder (CVE-2025-32962). Risk of unauthorized operations or information disclosure. Exploitable via `Host header`. Mitigation: upgrade to `4.6.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-32962** has been found in flask-appbuilder.
Attackers can target a specific entry point like `Host header` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade flask-appbuilder to **4.6.2** or later.
If unsure, ask your IT team or search "flask-appbuilder CVE-2025-32962" on the vendor's site.
CVE-2025-32962 (flask-appbuilder) — CWE-601 /
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: Host header / `FAB_SAFE_REDIRECT_HOSTS`
Patched: `4.6.2` — apply immediately
Workaround: Use a Reverse Proxy to Enforce Trusted Host Headers
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 flask-appbuilder. Attackers reach the vulnerable code path via `Host header` without authentication.
📍 Affected scope
flask-appbuilder — . Attack surface: Host header / `FAB_SAFE_REDIRECT_HOSTS`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **4.6.2**.
🛡️ Workaround
Workaround: Use a Reverse Proxy to Enforce Trusted Host Headers
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'flask-appbuilder' .` 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 'flask-appbuilder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `flask-appbuilder` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Use a Reverse Proxy to Enforce Trusted Host Headersパッチが適用されるまでの応急処置として、Use a Reverse Proxy to Enforce Trusted Host Headers を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade flask-appbuilder to 4.6.2ステージング環境で 4.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
flask-appbuilder
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.6.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-32962
- advisory https://github.com/advisories/GHSA-99pm-ch96-ccp2
- package https://github.com/dpgaspar/Flask-AppBuilder
- package https://pypi.org/project/flask-appbuilder
- web https://github.com/dpgaspar/Flask-AppBuilder/security/advisories/GHSA-99pm-ch96-ccp2
- web https://github.com/dpgaspar/Flask-AppBuilder/commit/32eedbbb5cb483a3e782c5f2732de4a6a650d9b6