CVE-2026-51083: Proxmox VE Auth Bypass Vulnerability

CVE-2026-51083 Overview

CVE-2026-51083 is an incorrect access control vulnerability in Proxmox Virtual Environment (PVE). The flaw resides in the qemu-server package and exposes hashed passwords through the cloudinit/dump API endpoint. Users with limited privileges can invoke the endpoint and retrieve credential material that should be restricted to administrative roles. The vulnerability is tracked under [CWE-284] Improper Access Control and affects the 8.x and 9.x branches of Proxmox VE.

Critical Impact
Authenticated low-privilege users can obtain hashed passwords from cloud-init configuration data through an authorization gap in the cloudinit/dump API, enabling offline credential cracking and lateral movement.

Affected Products

Proxmox Virtual Environment 9.x with qemu-server before 9.1.8
Proxmox Virtual Environment 8.x with qemu-server before 8.4.8
Deployments exposing the PVE API to users with restricted role assignments

Discovery Timeline

2026-07-17 - CVE-2026-51083 published to NVD
2026-07-17 - Last updated in NVD database

Technical Details for CVE-2026-51083

Vulnerability Analysis

Proxmox VE integrates cloud-init to provision virtual machines with configuration data, including user credentials and SSH keys. The qemu-server component exposes a cloudinit/dump API that renders the generated cloud-init configuration for a given VM. This configuration can contain hashed passwords supplied during VM setup.

The vulnerable code path does not enforce sufficient permission checks on this endpoint. Users holding limited roles, such as VM.Audit or similar low-privilege permissions on a VM, can request the dump output and receive fields containing password hashes. The intended behavior restricts credential material to accounts with administrative or configuration privileges.

Root Cause

The defect is an authorization gap in the API handler for cloudinit/dump. The endpoint returns the full rendered cloud-init user-data document without stripping sensitive fields or validating that the caller holds a role authorized to view credentials. Permission checks confirm access to the VM object but do not scope which fields the response may include.

Attack Vector

An attacker requires an authenticated account with limited privileges on a target VM within the Proxmox cluster. The attacker sends an HTTP request to the cloudinit/dump API for that VM and parses hashed password entries from the response. The attacker then performs offline cracking against the recovered hashes. Recovered credentials can enable lateral movement to guest operating systems or reuse against other services.

No verified exploit code is publicly available. See the Proxmox Security Advisory Forum for technical details.

Detection Methods for CVE-2026-51083

Indicators of Compromise

HTTP requests to /api2/json/nodes/{node}/qemu/{vmid}/cloudinit/dump originating from non-administrative user tokens
Access to the cloudinit/dump endpoint by API tokens or PVE users lacking VM.Config.Cloudinit or equivalent permissions
Unexpected read activity on cloud-init metadata for VMs containing password-authenticated accounts

Detection Strategies

Review the Proxmox pveproxy access logs at /var/log/pveproxy/access.log for GET requests targeting cloudinit/dump and correlate the requesting user against the assigned role
Baseline expected callers of the cloudinit/dump API and alert on any deviation, particularly requests from read-only or audit roles
Track offline password cracking indicators such as failed authentication bursts against VM guest services following suspicious API activity

Monitoring Recommendations

Forward pveproxy and pvedaemon logs to a centralized logging platform for retention and correlation
Alert on any use of the cloudinit/dump endpoint by accounts that have not been explicitly permitted to view credential material
Audit PVE role assignments periodically and flag users with VM-level access to systems that store password hashes in cloud-init configurations

How to Mitigate CVE-2026-51083

Immediate Actions Required

Upgrade qemu-server to version 9.1.8 on Proxmox VE 9.x or version 8.4.8 on Proxmox VE 8.x
Rotate any passwords that were provisioned to VMs through cloud-init on affected clusters, assuming the hashes may have been retrieved
Review PVE role assignments and remove unnecessary VM-level permissions from non-administrative accounts

Patch Information

Proxmox has released fixed packages in qemu-server 9.1.8 and 8.4.8. Apply the updates using apt update && apt dist-upgrade on each Proxmox node and restart affected services. Consult the Proxmox Security Advisory Forum for the authoritative advisory and package details.

Workarounds

Avoid storing password hashes in cloud-init configurations on affected versions and provision credentials through SSH keys or a secrets manager instead
Restrict PVE API access at the network layer so that only administrative workstations can reach the management interface
Revoke API tokens and user roles that do not require access to VM configuration endpoints until patches are applied

bash

# Apply the security update on each Proxmox node
apt update
apt install --only-upgrade qemu-server
# Verify the installed version meets the fixed release
dpkg -l qemu-server | awk '/qemu-server/ {print $3}'