Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2022-35508: SSRF and Arbitrary File Disclosure in Proxmox VE and Proxmox Mail Gateway

Published Dec 4, 2022 · 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.8Critical · v3.1
EPSS1.3%70th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Proxmox
IdentifiersCVE-2022-35508CWE-918 · Server-Side Request Forgery (SSRF)

CVE-2022-35508 affects Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) in the HTTP proxying logic between pve/pmgproxy and pve/pmgdaemon. A low-privileged authenticated user can craft requests to cluster-related API endpoints so that attacker-controlled path components influence the backend URL used for proxied requests, resulting in post-authentication server-side request forgery (SSRF). The issue was demonstrated against APIs including GET /api2/json/nodes/{node_name}/tasks/{upid}/log in PVE and a similar node/proxying path in PMG. The SSRF can then be chained into arbitrary file disclosure because the server trusts a pvestreamfile response header from the proxied response and passes its value to sysopen, causing the proxy worker to open and return local files from the server filesystem. The file read occurs in the pveproxy or pmgproxy worker context as uid 33 (www-data). In PMG, if the backup feature has been used, readable backup archives such as /var/lib/pmg/backup/pmg-backup_YYYY_MM_DD_*.tgz may contain the PMG authentication private key, enabling further compromise.

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 allows an authenticated but unprivileged attacker to coerce the server into making internal HTTP requests and to disclose arbitrary files readable by the proxy process on the target host. This exposes sensitive local data and configuration material. In PMG specifically, if backup archives containing pmg-authkey.key are present and readable, the attacker can recover the authentication signing key, forge PMGAuthCookie tickets, and escalate privileges to root@pam. The practical impact therefore ranges from sensitive file disclosure in both PVE and PMG to full administrative compromise of PMG under the documented backup-file condition.

Mitigation

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

Until patched, restrict access to the affected web interfaces to trusted administrators only and minimize the ability of low-privilege users to authenticate to PVE/PMG. Review and harden permissions on PMG backup archives under /var/lib/pmg/backup/ so they are not readable by unprivileged service accounts, and remove old backups containing auth keys where possible. Monitor for suspicious requests to node/proxying API paths and unexpected access to local sensitive files. If PMG backup archives may have exposed pmg-authkey.key, treat the key as compromised and rotate it.

Remediation

Patch, then assume compromise.

Upgrade pve-http-server to version 4.1-3 or later, which fixes the SSRF and related file disclosure issue. In PMG environments, also ensure backup archives created by the backup feature are no longer world-readable and remove or protect any existing backup files that may contain authentication key material. Rotate exposed authentication keys/tickets if compromise is suspected, especially the PMG auth key if backup archives may have been disclosed.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
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
ProxmoxProxmox Mail Gatewayapplication
ProxmoxPve Http Serverapplication
ProxmoxVirtual Environmentapplication
FAQ

Frequently asked questions

Is CVE-2022-35508 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-35508 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-35508?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-35508.
Is there a patch for CVE-2022-35508?
Upgrade pve-http-server to version 4.1-3 or later, which fixes the SSRF and related file disclosure issue. In PMG environments, also ensure backup archives created by the backup feature are no longer world-readable and remove or protect any existing backup files that may contain authentication key material.
What products are affected by CVE-2022-35508?
Proxmox Mail Gateway, Proxmox Virtual Environment, and Proxmox Pve Http Server.
How severe is CVE-2022-35508?
CVE-2022-35508 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 1.3% (70th percentile) as of Oct 16, 2026.
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 evidenceEvery 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 activityCommunity discussion across Reddit, Mastodon, and other social sources.