VYPR
High severity8.8NVD Advisory· Published Jun 2, 2026

CVE-2026-1784

CVE-2026-1784

Description

OpenShift Route resource allows HAProxy configuration injection due to insufficient path validation, potentially leading to unauthorized access.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

OpenShift Route resource allows HAProxy configuration injection due to insufficient path validation, potentially leading to unauthorized access.

Vulnerability

The Route OpenShift resource, which defines routes to expose pods via HAProxy, contains an insufficiency in the validation of the spec.path YAML stanza. This allows for controlled injection of HAProxy configuration.

Exploitation

An attacker with the ability to create or modify Route resources in an OpenShift cluster could exploit this vulnerability. By crafting a malicious spec.path value, an attacker can inject arbitrary HAProxy configuration, potentially leading to unauthorized access or manipulation of traffic routing.

Impact

Successful exploitation allows an attacker to inject HAProxy configuration, which could lead to various security impacts including information disclosure, denial of service, or potentially remote code execution depending on the injected configuration and the cluster's setup. The scope of the impact is tied to the privileges of the attacker within the OpenShift cluster.

Mitigation

Red Hat has addressed this issue. Please refer to the Red Hat Security Advisory [1] for specific details on affected versions and mitigation steps. A fix is available in updated versions of OpenShift.

References
  1. cve-details

AI Insight generated on Jun 2, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

1

Patches

0

No patches discovered yet.

Vulnerability mechanics

No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.

References

2

News mentions

0

No linked articles in our index yet.