# CVE-2026-54529: SQLAdmin: Unvalidated sortBy parameter in `ModelView` bypasses `column_sortable_list`

> Attackers can exploit unvalidated sorting parameters to infer hidden database values through ordering oracles in SQLAdmin applications.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-ccg5-9c8w-xh6v, PYSEC-2026-3922

## What is CVE-2026-54529?

CVE-2026-54529 is a medium-severity vulnerability in smithyhq sqladmin, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-248 (Uncaught Exception), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2026-54529?

3 open source packages ship an affected version, including sqladmin.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sqladmin` | PyPI | All versions | 0.27.1 |
| `sqladmin` | PyPI | All versions | 0.27.1 |
| `sqladmin` | PyPI | All versions | 0.27.1 |

## How do I fix CVE-2026-54529?

Upgrade sqladmin to 0.27.1 or later.

## Is CVE-2026-54529 being exploited?

There is no known exploitation of CVE-2026-54529 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54529 and fix it if it is affected.

What it is: CVE-2026-54529 is a medium-severity vulnerability in smithyhq sqladmin, published on 14 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-54529 in the wild and no public exploit code.

Affected packages and fixed versions:
- sqladmin (PyPI): affected all versions; fixed in 0.27.1
- sqladmin (PyPI): affected all versions; fixed in 0.27.1
- sqladmin (PyPI): affected all versions; fixed in 0.27.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54529/ (Markdown: https://insights.sbomify.com/CVE-2026-54529/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54529
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54529
- OSV: https://osv.dev/vulnerability/CVE-2026-54529

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54529/
Summaries are generated and may contain mistakes; the official description above is the record.