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.
Original description
The description as published by the source.
Summary
Affected versions of Starlette-Admin prior to 0.16.1 do not properly validate user-supplied sort and search parameters against the configured field allowlists. While the administrative UI restricts available fields based on field configuration, the backend accepts arbitrary field names supplied through API requests.
An authenticated user can submit crafted requests to sort or filter records using fields that are not intended to be searchable or sortable. Additionally, supplying invalid field names or special Python attribute names can trigger unhandled exceptions that result in HTTP 500 responses.
Impact
An authenticated user with access to affected list endpoints may:
- Bypass intended UI restrictions and perform sorting or filtering on fields that are not configured as searchable or sortable.
- Cause affected API requests to fail with HTTP 500 responses by supplying invalid field names or special Python attribute names such as
metadataor__class__.
This vulnerability may result in unauthorized use of query functionality and limited denial-of-service conditions affecting the targeted endpoint.
Affected Versions
All versions before 0.16.1.
Patched Versions
- 0.16.1
Workarounds
There are no known workarounds. Users should upgrade to version 0.16.1 or later.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
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.
Information disclosure (CWE-200) exists in starlette-admin. Attackers reach the vulnerable code path via metadata.
Check the vendor advisory for the affected versions of starlette-admin. Attack surface: metadata / __class__.
Severity: Medium (CVSS 5.4/10). Risk of unauthorized operations or information disclosure.
Update to 0.16.1.
Workaround: There are no known workarounds.
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
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 し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
There are no known workarounds.パッチが適用されるまでの応急処置として、There are no known workarounds. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade starlette-admin to 0.16.1ステージング環境で 0.16.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。