Starlette-Admin's unvalidated order_by parameter allows ordering by hidden columns (info-exposure oracle) and HTTP 500 DoS

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

EPSS

• CVE-2026-54553: 0.45% estimated exploitation activity in the next 30 days; percentile 39.07 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 metadata or class. This vulnerability may result in…

Published by the source

26 Aug 2026, 14:14 UTC

Last modified by the source

26 Aug 2026, 14:14 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6753-gr46-6wpr

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-54553

Advisory: Starlette-Admin's unvalidated `order_by` parameter allows ordering by hidden columns (info-exposure oracle) and HTTP 500 DoS
IDs: CVE-2026-54553, GHSA-6753-gr46-6wpr
Record: https://patchnext.com/advisories/cve-2026-54553 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: starlette-admin 0.16.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI starlette-admin: affected <= 0.16.0; fixed in 0.16.1

## Suggested inspection (read-only)
- `python -m pip show starlette-admin`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on starlette-admin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6753-gr46-6wpr (GitHub-reviewed advisory GHSA-6753-gr46-6wpr lists affected ranges: PyPI starlette-admin >=0 <=0.16.0)

Commands are suggestions: review each one before running it.