# CVE-2026-111642: FastapiAdmin through 3.0 Hard-Coded JWT Secret Privilege Escalation

> Hard-coded JWT secret allows attackers to forge superuser tokens and escalate privileges in FastapiAdmin.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-p7cm-h8w6-p4cm

## What is CVE-2026-111642?

CVE-2026-111642 is a high-severity vulnerability in FastapiAdmin, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

FastapiAdmin through 3.0 contains a hard-coded JWT signing secret in backend/app/config/setting.py that allows low-privileged users to forge tokens impersonating the superuser. Attackers can register via the unauthenticated /api/v1/system/user/register endpoint, log in, and forge an HS256 token keeping their session_id but naming the superuser in user_name to gain superuser privileges.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

No fix has been published for CVE-2026-111642 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111642 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111642 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-111642 is a high-severity vulnerability in FastapiAdmin, published on 16 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-111642 exists.

Affected product: FastapiAdmin. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111642/ (Markdown: https://insights.sbomify.com/CVE-2026-111642/index.md)
```

## Sources

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

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