CVE-2026-111642 fastapiadmin CVE debrief

Who should care

Defenders and administrators of FastapiAdmin instances should assess exposure and prioritize remediation due to the potential for unauthorized access and privilege escalation. Security teams and vulnerability management teams should review and update authentication and authorization configurations to prevent exploitation.

Why it matters

CVE-2026-111642 allows low-privileged users to forge tokens impersonating the superuser, potentially leading to unauthorized access and privilege escalation.

• Potential for unauthorized access to sensitive data
• Possible elevation of privileges for low-privileged users
• Need for review and update of authentication and authorization configurations

Technical summary

FastapiAdmin through 3.0 contains a hard-coded JWT signing secret in backend/app/config/setting.py, allowing low-privileged users to forge tokens impersonating the superuser. Attackers can exploit this by registering via the unauthenticated /api/v1/system/user/register endpoint, logging in, and forging an HS256 token with their session_id but naming the superuser in user_name to gain superuser privileges. This vulnerability requires review and update of authentication and authorization configurations to prevent potential unauthorized access and privilege escalation.

Defensive priority

High priority for authentication and authorization system review

Recommended defensive actions

• Review and update authentication and authorization configurations
• Implement additional logging and monitoring for suspicious activity
• Verify and update FastapiAdmin to the latest version
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

Official CVE Program record and NIST NVD detail page provide vulnerability metadata. Supplemental sources describe technical details and potential exploitation. The CVE record was published on 2026-10-16T17:39:12.365Z and has not been modified since then. Evidence is limited to public sources and may not reflect the full scope or technical details of the vulnerability.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.