CVE-2026-33814 is an infinite-loop vulnerability in an HTTP/2 transport implementation. When the transport processes a peer SETTINGS frame that sets SETTINGS_MAX_FRAME_SIZE to zero, it can repeatedly write HTTP/2 CONTINUATION frames without making progress. The malformed but attacker-controlled SETTINGS value therefore causes non-terminating frame-generation behavior.
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.
117 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Go HTTP/2 denial-of-service vulnerability in golang.org/x/net caused by malformed SETTINGS_MAX_FRAME_SIZE frames. It affects packages included in the Red Hat build of MicroShift 4.19.46 on Red Hat Enterprise Linux CoreOS 4.
A vulnerability addressed by the EulerOS_SA-2026-3264 advisory/plugin; no technical vulnerability description is provided.
Unknown
A network-accessible denial-of-service vulnerability in Go's HTTP/2 implementation (golang.org/x/net), triggered by a malformed SETTINGS_MAX_FRAME_SIZE frame. It affects packages included in Red Hat build of MicroShift 4.22.13 on Red Hat Enterprise Linux CoreOS 4.
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.