Summary
kube-httpcache is vulnerable to Cross-Site Request Forgery (CSRF)
Workarounds
See upstream mitigation hints.
References
Impact
A request forgery attack can be performed on Varnish Cache servers that have the HTTP/2 protocol turned on. An attacker may introduce characters through the HTTP/2 pseudo-headers that are invalid in the context of an HTTP/1 request line, causing the Varnish server to produce invalid HTTP/1 requests to the backend. This may in turn be used to successfully exploit vulnerabilities in a server behind the Varnish server.
-- https://varnish-cache.org/security/VSV00011.html#vsv00011
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This is fixed in Varnish 6.0.11; Varnish 6.0.11 is available in kube-httpcache versions v0.7.1 and later.
Frequently Asked Questions
- What is GHSA-47XH-QXQV-MGVG? GHSA-47XH-QXQV-MGVG is a medium-severity cross-site request forgery (CSRF) vulnerability in github.com/mittwald/kube-httpcache (go), affecting versions < 0.7.1. It is fixed in 0.7.1. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- Which versions of github.com/mittwald/kube-httpcache are affected by GHSA-47XH-QXQV-MGVG? github.com/mittwald/kube-httpcache (go) versions < 0.7.1 is affected.
- Is there a fix for GHSA-47XH-QXQV-MGVG? Yes. GHSA-47XH-QXQV-MGVG is fixed in 0.7.1. Upgrade to this version or later.
- Is GHSA-47XH-QXQV-MGVG exploitable, and should I be worried? Whether GHSA-47XH-QXQV-MGVG is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-47XH-QXQV-MGVG is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-47XH-QXQV-MGVG? Upgrade
github.com/mittwald/kube-httpcacheto 0.7.1 or later.