CVE-2026-41246
Contour: Lua code injection in cookieRewrite enables RCE
Is CVE-2026-41246 being exploited?
Not confirmed. CVE-2026-41246 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-41246?
CVE-2026-41246 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-41246?
Yes. A fix has been recorded for CVE-2026-41246. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-41246 affect?
CVE-2026-41246 affects Contour Kubernetes Ingress Controller <1.33.4, Envoy proxy used by Contour. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-41246?
Upgrade to patched Contour release; review RBAC on HTTPProxy
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
RCE in Envoy via Lua filter; RBAC to HTTPProxy can affect multi-tenant deployments, with potential credential access or DoS.
Patch when possible
- affected>= 1.33.0 and < 1.33.4
- affected>= 1.32.0 and < 1.32.5
- affected>= 1.19.0 and < 1.31.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.