CVE-2026-46645

Workarounds

None. Developers relying on is_accessible() to restrict model visibility are exposed regardless of what other access controls are in place.

The ajax_lookup endpoint in application.py bypasses the is_accessible() access control check that all other endpoints enforce.

If a developer restricts model access by overriding is_accessible(), an authenticated user can still query that model's data through the ajax_lookup endpoint, silently bypassing the restriction.

Affected endpoint:

GET /{identity}/ajax/lookup?name=<field>&term=<query>

All other endpoints enforce both checks:

Note: before this fix, ajax_lookup also lacked the @login_required decorator, unauthenticated users could query it directly. That was addressed in #1035. This report covers the remaining gap: authenticated but unauthorized users.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-46645 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.25.1); upgrading removes the vulnerable code path.

Kodem intelligence

Two changes were made to ajax_lookup:

1. Replaced the hand-rolled authentication check added in #1035 with the standard @login_required decorator used by all other endpoints.
2. Added the missing is_accessible(request) check, raising HTTP 403 when it returns False.

1. What is CVE-2026-46645? CVE-2026-46645 is a medium-severity missing authorization vulnerability in sqladmin (pip), affecting versions <= 0.25.0. It is fixed in 0.25.1. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-46645? CVE-2026-46645 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of sqladmin are affected by CVE-2026-46645? sqladmin (pip) versions <= 0.25.0 is affected.
4. Is there a fix for CVE-2026-46645? Yes. CVE-2026-46645 is fixed in 0.25.1. Upgrade to this version or later.
5. Is CVE-2026-46645 exploitable, and should I be worried? Whether CVE-2026-46645 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-46645 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-46645? Upgrade sqladmin to 0.25.1 or later.