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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A CRLF injection vulnerability in Proxmox VE that allows response header injection via carriage return characters in error messages, enabling a client-side denial-of-service scenario in Chromium-based browsers.
A CRLF injection vulnerability in Proxmox VE's HTTP response handling that allows header injection using carriage return characters, enabling browser-dependent abuse including client-side denial of service.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.