OpenShift Router Header Spoofing Bypasses TLS Authentication

A flaw was found in the OpenShift Router. When a Route has `insecureEdgeTerminationPolicy` set to Allow, the HTTP frontend does not remove `X-SSL-Client-*` headers from incoming requests. This allows an unauthenticated attacker to send plain HTTP requests with crafted `X-SSL-Client-*` headers. As a result, backends relying on these headers for mutual TLS (Transport Layer Security) authentication can be bypassed, enabling the attacker to impersonate client certificate identities.

Casky was already ahead

This CVE exploits attack patterns that Casky's 261matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-46579 exposes a critical authentication bypass in OpenShift Router configurations where `insecureEdgeTerminationPolicy` is set to Allow. The vulnerability stems from the HTTP frontend failing to sanitize incoming `X-SSL-Client-*` headers, which are typically set only by legitimate TLS termination points during mutual TLS (mTLS) handshakes. An unauthenticated attacker can craft plain HTTP requests with forged certificate headers, allowing them to impersonate authenticated clients and bypass mTLS authentication controls entirely. This affects any organization running OpenShift with Routes configured for insecure edge termination and relying on X-SSL-Client headers for backend authentication, potentially exposing sensitive services and data to unauthorized access.

Casky's 261 matched security skills leverage Claude's extended reasoning to detect attack patterns associated with TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky will see findings correlated with header injection detection, abnormal header patterns in HTTP traffic, and authentication mechanism bypass attempts. The platform's skills map to CWE-287 (Improper Authentication) and flag suspicious `X-SSL-Client-*` header usage in unauthenticated requests, anomalous certificate claims without corresponding TLS handshakes, and unauthorized privilege escalation following header manipulation. By analyzing traffic patterns and authentication context, Casky helps teams identify when attackers are attempting to spoof client identities through header injection, enabling rapid response before sensitive backend systems are compromised.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

261 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-46579.

analyzing-cloud-storage-access-patterns

cloud security · low

Run

analyzing-kubernetes-audit-logs

container security · low

Run

analyzing-malicious-url-with-urlscan

phishing defense · medium

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-46579

Casky has 261 skills that investigate the attack patterns behind CVE-2026-46579. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn