Answer in brief
CVE-2026-54529 records a Medium severity (CVSS 5.3) vulnerability in SQLAdmin: Unvalidated sortBy parameter in `ModelView` bypasses `column_sortable_list`. The current sources do not mark it as known exploited. The current feed maps smithyhq/sqladmin (generic), sqladmin (pip), sqladmin (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps smithyhq/sqladmin (generic), sqladmin (pip), sqladmin (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| smithyhq/sqladmingeneric | <0.27.1 | 0.27.1 |
| sqladminpip | <0.27.1 | 0.27.1 |
| sqladminpypi | >=0 <0.27.1 | 0.27.1 |
Published upstream
Sep 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Sep 9, 2026
SQLAdmin is a flexible Admin interface for SQLAlchemy models. Prior to 0.27.1, ModelView.sort_query in sqladmin/models.py accepts the attacker-controlled sortBy list-view query parameter without enforcing the configured column_sortable_list server-side allow-list in self._sort_fields. The value is resolved with getattr and passed to relationship joins and order_by, allowing requests to sort by columns hidden from column_list and by related-model columns through dotted paths. The resulting row order forms an information-exposure oracle for unexposed values, and reversing ascending and descending order confirms their relative ordering. Pairing sortBy with searchable or filterable columns and pagination can narrow the oracle toward specific values, but exact recovery depends on the application's available fields and data. This issue is fixed in version 0.27.1.
Quoted source text, attributed separately from HOL analysis.