CVE-2026-41246

Contour: Lua code injection via Cookie Path Rewrite Policy

HIGH
8.1
CVSS Score
Published: April 23, 2026 at 06:44 PM UTC
Updated: October 26, 2026 at 10:10 PM UTC
1 product affected across 1 vendorContour

Using contour by projectcontour?

Get instant alerts when new vulnerabilities affect contour - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.1
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

Contour is a Kubernetes ingress controller using Envoy proxy. From v1.19.0 to before v1.33.4, v1.32.5, and v1.31.6, Contour's Cookie Rewriting feature is vulnerable to Lua code injection. An attacker with RBAC permissions to create or modify HTTPProxy resources can craft a malicious value in spec.routes[].cookieRewritePolicies[].pathRewrite.value or spec.routes[].services[].cookieRewritePolicies[].pathRewrite.value that results in arbitrary code execution in the Envoy proxy. The cookie rewriting feature is internally implemented using Envoy's HTTP Lua filter. User-controlled values are interpolated into Lua source code using Go text/template without sufficient sanitization. The injected code only executes when processing traffic on the attacker's own route, which they already control. However, since Envoy runs as shared infrastructure, the injected code can also read Envoy's xDS client credentials from the filesystem or cause denial of service for other tenants sharing the Envoy instance. This vulnerability is fixed in v1.33.4, v1.32.5, and v1.31.6.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.19.0 ≤ v < 1.31.61.32.0 ≤ v < 1.32.51.33.0 ≤ v < 1.33.4
Affected range stops below 1.31.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.32.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.33.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (7)

x_refsource_CONFIRMPatchVendor Advisory
Source: cverecord
https://github.com/projectcontour/contour/security/advisories/GHSA-x4mj-7f9g-29h4
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/projectcontour/contour/releases/tag/v1.31.6
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/projectcontour/contour/releases/tag/v1.32.5
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/projectcontour/contour/releases/tag/v1.33.4
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-41246
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2461257

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.1HIGHGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-94

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card