Loading vulnerability…
Kubernetes kube-apiserver follows HTTP redirects when communicating with admission webhooks configured through MutatingWebhookConfiguration or ValidatingWebhookConfiguration. An actor who can control the webhook endpoint or its responses can cause kube-apiserver to follow a redirect to attacker-chosen destinations on networks reachable from the API server, including private/internal addresses. This creates a server-side request forgery condition from the privileged network position of kube-apiserver. The issue becomes more severe if the attacker can also cause or observe kube-apiserver running at log verbosity 10, because redirected response bodies and headers may be written to logs and exposed to the attacker. Available context indicates this is considered an architectural/design trade-off rather than a fully patchable implementation bug.
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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An unfixed Kubernetes architectural/design issue in kube-apiserver where admission webhook HTTP redirects can be abused to redirect API server requests to internal private networks.
An unpatchable Kubernetes vulnerability that can be used to carry out SSRF attacks on clusters.
A Kubernetes vulnerability that combines an API server SSRF vector with profiling/debug log-level manipulation to let a privileged attacker observe SSRF responses from the kube-apiserver's network position.
Unknown (mentioned only as a future topic; described generally as related to Kubernetes SSRF attacks).
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.