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