Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2022-35507: CRLF injection in Proxmox VE and PMG web interface

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.
CVSS7.1High · v3.1
EPSS1.5%75th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Proxmox
IdentifiersCVE-2022-35507CWE-113

A response-header CRLF injection vulnerability in the Proxmox Virtual Environment (PVE) and Proxmox Mail Gateway (PMG) web interface allows remote manipulation of HTTP response headers. The issue is in HTTP error handling in perl5/PVE/APIServer/AnyEvent.pm, where sanitization only matched the first line of an error message and blocked LF but not standalone CR characters. As a result, attacker-controlled input containing %0d could be reflected into the response in a way that Chromium-based browsers interpreted as injected response headers. The documented exploitation path allows an attacker to set oversized cookies for the victim’s browser, leading to a client-side denial of service against the Proxmox web UI. The issue was fixed in pve-http-server 4.1-3.

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 enables HTTP response header injection in affected browsers, specifically Chromium-based browsers such as Chrome, Edge, and Opera under the described conditions. The practical impact described in the source material is client-side denial of service: the attacker can cause the victim browser to store cookies longer than the server expects, after which subsequent requests to the Proxmox web interface exceed the server’s 8192-byte header limit and are rejected. This can prevent the victim from using the web UI until the offending cookies are cleared. No server-side code execution or privilege escalation is described for this CVE.

Mitigation

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

If immediate patching is not possible, reduce exposure of the web interface to untrusted users and networks, restrict access to the management UI, and avoid workflows where attacker-controlled input can be reflected into error responses. Because the described exploit path depends on browser behavior, limiting use of affected Chromium-based browsers for administrative access and clearing malicious cookies can reduce impact. Restricting or disabling third-party cookie acceptance may also hinder the documented attack path.

Remediation

Patch, then assume compromise.

Upgrade to pve-http-server version 4.1-3 or later, which patches the CRLF injection by adding additional checks for CRLF handling in the affected HTTP error-processing path. Apply the vendor-provided updates for affected Proxmox VE and PMG installations.

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-35507 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2022-35507 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2022-35507?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2022-35507.
Is there a patch for CVE-2022-35507?
Upgrade to pve-http-server version 4.1-3 or later, which patches the CRLF injection by adding additional checks for CRLF handling in the affected HTTP error-processing path. Apply the vendor-provided updates for affected Proxmox VE and PMG installations.
What products are affected by CVE-2022-35507?
Proxmox Mail Gateway, Proxmox Virtual Environment, and Proxmox Pve Http Server.
How severe is CVE-2022-35507?
CVE-2022-35507 has a CVSS v3.1 score of 7.1 (High) and an EPSS score of 1.5% (75th 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 activity2Community discussion across Reddit, Mastodon, and other social sources.