cve.bz

CVE-2026-125637 Konflux-ci: unvalidated hostname fields enable caddyfile config injection in the konflux ui proxy generator, allowing an unauthenticated route to be spliced ahead of the forward_auth/impersonate authorization chain

7.2 highEPSS 0.7%

High (7.2). EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw was found in the Konflux UI proxy. Hostname values defined in the KonfluxUI custom resource are inserted directly into proxy configuration files without adequate validation or sanitization. An authenticated user with permissions to modify the custom resource can inject malicious configuration directives to bypass authentication and authorization controls, potentially exposing internal backend services. In addition, providing malformed input can cause the configuration generator to fail, resulting in a denial of service (DoS) by preventing the proxy from starting.

Severity

CVSS 3.1

7.2 high
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% estimated probability of exploitation activity in the next 30 days; 54th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-11-12. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
redhat (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-125637 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125637?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125637?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125637 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125637

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125637](https://cve.bz/cve/badge/CVE-2026-125637.svg)](https://cve.bz/cve/CVE-2026-125637)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125637"><img src="https://cve.bz/cve/badge/CVE-2026-125637.svg" alt="CVE-2026-125637"></a>

Versions

From the CNA's record in the CVE List.

ProductAffected
konflux-cithrough 0.2.2

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates this vulnerability as Important because successful exploitation completely circumvents the proxy's authentication and impersonation enforcement, granting unauthenticated access to internal backend services and the Kubernetes API. While triggering the vulnerability requires administrative privileges (which is what limits the scope of impact) to modify the KonfluxUI custom resource or manage GitOps manifests, the resulting compromise undermines the primary security boundary the proxy was designed to establish.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-125637.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON