PatchSiren cyber security CVE debrief
CVE-2023-54391 Proxmox Server Solutions GmbH CVE debrief
CVE-2023-54391 is an authentication bypass vulnerability in Proxmox Virtual Environment (VE) 7.0 through 8.0, affecting libpve-access-control before 8.0.4. This vulnerability allows unauthenticated attackers to authenticate as any existing enabled user without a configured second factor by supplying an arbitrary tfa-challenge value in the API login endpoint.
- Vendor
- Proxmox Server Solutions GmbH
- Product
- Proxmox Virtual Environment (VE)
- CVSS
- CRITICAL 9.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-09-01
- Original CVE updated
- 2026-09-03
- Advisory published
- 2026-09-01
- Advisory updated
- 2026-09-03
Who should care
System administrators and security teams using Proxmox VE 7.0 through 8.0 with libpve-access-control before 8.0.4 should assess exposure and prioritize updating to version 8.0.4 or later.
Why it matters
CVE-2023-54391 is a critical authentication bypass vulnerability in Proxmox Virtual Environment (VE) 7.0 through 8.0. System administrators and security teams should assess exposure and prioritize updating to version 8.0.4 or later to prevent unauthorized access.
- Unauthenticated access to the system
- Potential for lateral movement
- Increased risk of data breaches
- Need for immediate patching or mitigation
Technical summary
The vulnerability exists in the libpve-access-control library before version 8.0.4, used in Proxmox Virtual Environment (VE) 7.0 through 8.0. An unauthenticated attacker can bypass authentication by providing an arbitrary tfa-challenge value in the API login endpoint, allowing access as any existing enabled user without a configured second factor. This vulnerability allows unauthenticated attackers to authenticate as any existing enabled user without a configured second factor by supplying an arbitrary tfa-challenge value in the API login endpoint. Attackers can send a POST request to the access ticket API endpoint with any value in the tfa-challenge parameter to completely skip password verification, gaining
Defensive priority
High priority for systems using Proxmox VE 7.0 through 8.0 with libpve-access-control before 8.0.4
Recommended defensive actions
- Immediately update libpve-access-control to version 8.0.4 or later
- Restrict access to the API login endpoint
- Monitor for suspicious login attempts
- Implement additional authentication measures
- 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
The CVE record and NVD entry provide details on the authentication bypass vulnerability in Proxmox VE. The vulnerability allows unauthenticated access to the system without a second factor. Affected releases are end of life. System administrators and security teams should assess exposure and prioritize updating to version 8.0.4 or later. Evidence is limited to public CVE details and NVD assessments.
Sources and references
Verified primary and authoritative sources
-
CVE-2023-54391 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2023-54391
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2023-54391 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2023-54391
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://forum.proxmox.com/threads/proxmox-virtual-environment-security-advisories.149331/page-4
-
Source reference
Unverified legacy reference
URL: https://www.vulncheck.com/advisories/proxmox-ve-authentication-bypass-via-tfa-challenge-parameter
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.