CVE-2022-35507: CRLF injection in Proxmox VE and PMG web interface
- Vendor
- Proxmox
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
References
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.
Recent activity
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.