Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2023-54391: Authentication bypass in Proxmox VE libpve-access-control

Published Sep 1, 2026 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v4
EPSS3.0%88th percentile
CISA KEVNoNot listed
In the wildReported6 exploitation records in Mallory
Vendor
Proxmox
IdentifiersCVE-2023-54391CWE-304 · Missing Critical Step in…

CVE-2023-54391 is an authentication-bypass vulnerability affecting Proxmox Virtual Environment 7.0–7.4 and the initial 8.0 release, using libpve-access-control versions 7.0-7 through 8.0.3. The authentication logic treats the presence of a tfa-challenge parameter as evidence that password verification has already succeeded, without validating the challenge for accounts lacking a configured second factor. An unauthenticated attacker can submit a crafted API login request to impersonate any existing enabled account without two-factor authentication, including the host root account. The vulnerability was fixed in libpve-access-control 8.0.4; all affected Proxmox VE releases are end of life.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation bypasses password verification and grants the privileges of the impersonated account. Compromise of the host root account can provide administrative control over the Proxmox host, virtual machines, containers, disks, backups, storage settings, and shared cluster configuration. Potential consequences include data theft, unauthorized configuration changes, malicious virtual-machine deployment, and destructive actions. Recorded matching requests establish exploitation attempts but do not, by themselves, establish successful compromise.

Mitigation

If you can’t patch tonight, do this now.

Restrict the management interface on TCP port 8006 to trusted administrative networks or a VPN, and enable two-factor authentication on every enabled account, particularly privileged accounts. Protecting one account with a second factor does not protect other accounts without one. A vendor temporary mitigation that validates authentication challenges is reported for affected end-of-life installations, although the supplied advisory does not specify a workaround; verify its applicability with the vendor and use it only as a bridge to migration. Network restrictions do not prevent exploitation from a compromised system with management-network access, and rate limiting alone does not stop a single valid-looking exploit request.

Remediation

Patch, then assume compromise.

Upgrade every host to a supported, fully updated Proxmox VE release and verify that libpve-access-control is version 8.0.4 or later on every cluster node. Proxmox VE 7.x did not receive the fix and requires migration; upgrading only to another end-of-life release is not a permanent solution. Investigate previously exposed hosts for unauthorized users, API tokens, virtual machines, and persistence. If compromise is suspected, rotate administrative credentials, API tokens, SSH keys, and potentially exposed guest credentials.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 2 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2023-54391-RCEThe supplied repository contains one standalone Python exploit, CVE-2023-54391.py (3,789 bytes), and README.md (2,205 bytes). The README documents the claimed vulnerability, affected versions, usage, mitigation, and external references. No exploit framework is present. The script accepts a target URL and submits a passwordless root@pam login with an arbitrary tfa-challenge value. It extracts the authentication ticket and CSRF token, enumerates nodes, requests a terminal proxy on the first node, and connects to its WebSocket terminal. Concurrent asynchronous tasks forward operator input and display terminal output. This is an exploitation attempt rather than a detection-only script; command execution relies on access to the legitimate root terminal after authentication bypass, not on a separate command-injection vulnerability. HTTPS and WebSocket certificate verification are disabled. Reliability limitations include treating HTTP 200 alone as authentication success, continuing after a failed login, assuming successful JSON responses and a nonempty node list, requiring an explicit target port for WebSocket URL construction, and assuming received terminal messages are bytes. Dependencies are imported but no dependency manifest is supplied. Static inspection found no obvious local destructive commands, attacker callback, or exfiltration destination. Exploit effectiveness and the README's CVE/version claims were not independently verified. The repository URL, git reference, and archive size were not supplied; blank strings and zero represent unavailable metadata, while the listed files total 5,994 bytes.alexand0www · Disclosed Oct 6, 2026 · python · network · webOperationalCVE-2023-54391-RCEThe supplied repository contains two files: CVE-2023-54391.py (3,789 bytes), a standalone Python exploit, and README.md (2,205 bytes), documentation covering the claimed vulnerability, affected versions, usage, and mitigation. The script uses requests for management API calls and asyncio/websockets for interactive terminal transport. It is not integrated with an exploit framework and is more than a detection script: it attempts passwordless authentication as the hardcoded root@pam account, retrieves authentication and CSRF tokens, enumerates nodes, creates a terminal proxy on the first node, and bridges operator input and terminal output over WebSocket. The root command-execution capability comes from authenticated management functionality rather than a separate command-injection payload. All operational destinations derive from the operator-supplied target URL; no external callback, persistence, destructive command, or exfiltration endpoint appears in the code. HTTPS and WebSocket certificate verification are disabled. Reliability limitations include proceeding after failed authentication, assuming expected JSON fields and a nonempty node list, lacking request timeouts, assuming WebSocket output is bytes, and constructing the WebSocket URL with an explicit parsed port. The README's CVE attribution, version range, and testing claim are not independently verified by the supplied material. No repository URL, git reference, archive location, or archive size was provided; empty repository strings and a zero size represent unavailable metadata.alexandrov666 · Disclosed Oct 6, 2026 · python · network · webOperational
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
ProxmoxVirtual Environmentapplication
FAQ

Frequently asked questions

Is CVE-2023-54391 exploited in the wild?
Yes. As of Oct 9, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2023-54391?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2023-54391, the earliest disclosed Oct 6, 2026.
Is there a patch for CVE-2023-54391?
Upgrade every host to a supported, fully updated Proxmox VE release and verify that libpve-access-control is version 8.0.4 or later on every cluster node. Proxmox VE 7.x did not receive the fix and requires migration; upgrading only to another end-of-life release is not a permanent solution.
What products are affected by CVE-2023-54391?
Proxmox Virtual Environment.
How severe is CVE-2023-54391?
CVE-2023-54391 has a CVSS v4 score of 9.3 (Critical) and an EPSS score of 3.0% (88th percentile) as of Oct 9, 2026.
Activity feed

Recent activity

26 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
codebyNews · Oct 8, 2026Proxmox VE Auth Bypass CVE-2023-54391: root@pam Auth Bypass - Форум информационной безопасности - Codeby.netAccording to the content, supplying the tfa-challenge parameter to the Proxmox authentication endpoint bypasses password verification for existing enabled accounts without two-factor authentication. An unauthenticated attacker can obtain an authentication ticket for accounts including root@pam, gaining control over the host, its virtual machines and containers, and the shared cluster filesystem. The reported CVSS v3.1 score is 9.8. The content identifies libpve-access-control 8.0.4 as the fixed version and recommends restricting management access, enabling two-factor authentication, applying the vendor stop-gap where necessary, and upgrading unsupported releases.Read more ↗cert pyNews · Oct 6, 2026Vulnerabilidad en productos PROXMOX - CERT-PYThe content reports a critical authentication bypass in Proxmox VE's libpve-access-control session-processing logic, rated CVSS v3.1 9.8. It states that unauthenticated attackers can send crafted HTTP requests to bypass credential checks, obtain an active management session, and take administrative control of the virtualized environment.Read more ↗bleeping computerNews · Sep 22, 2026Chinese hackers exploit WordPress, Zyxel flaws to steal govt dataA vulnerability affecting Proxmox VE that was targeted by the observed threat cluster.Read more ↗cyberveilleNews · Sep 21, 2026Un acteur chinois vole 18 000 dossiers gouvernementaux via WordPress et exploite ZyXEL GS1900 | CyberVeilleVulnerability in Proxmox VE targeted during the reported multi-vector exploitation campaign.Read more ↗
+5 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence3Every report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity17Community discussion across Reddit, Mastodon, and other social sources.