CVE
Konflux-ci: unvalidated hostname fields enable caddyfile config injection in the konflux ui proxy generator, allowing an unauthenticated…
Affects konflux-ci up to and including 0.2.2 for anyone with write access to the KonfluxUI custom resource hostname fields. No vendor rating or fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- No fix listed
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Write access to the KonfluxUI custom resource hostname fields (spec hostname values for tektonResults, kite, kubeArchive, watson). Affected code is the konflux-ci UI proxy config generator at main branch and v0.2.2.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Konflux-ci's UI proxy inserts hostname values from the KonfluxUI custom resource into its configuration files without adequate validation. An attacker over the network who already has permission to modify that resource can inject configuration directives to bypass authentication and authorization and reach internal backend services, or send malformed input that stops the proxy from starting, causing denial of service.
Read the original description
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.
Who should check
Teams running konflux-ci (Konflux UI proxy) where admins or GitOps pipelines can modify KonfluxUI custom resource hostname fields.
Read the source excerpt
“Reproduced against konflux-ci/konflux-ci, main branch, v0.2.2”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.2/10CVSS 7.2
- No patch5/5No patch listed yet
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
- Would score about 27 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Write access to the KonfluxUI custom resource hostname fields (spec hostname values for tektonResults, kite, kubeArchive, watson). Affected code is the konflux-ci UI proxy config generator at main branch and v0.2.2.Workaround: Limit write access to the KonfluxUI custom resource hostname fields, since the issue requires that access. The checked facts give no other workaround.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-125637 (Konflux-ci: unvalidated hostname fields enable caddyfile config injection in the konflux ui proxy generator, allowing an unauthenticated…), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-125637 (entry last updated 2026-11-11):
Affected:
- konflux-ci: through 0.2.2
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Write access to the KonfluxUI custom resource hostname fields (spec hostname values for tektonResults, kite, kubeArchive, watson). (source: https://bugzilla.redhat.com/show_bug.cgi?id=2569294)
- Affected code is the konflux-ci UI proxy config generator at main branch and v0.2.2. (source: https://bugzilla.redhat.com/show_bug.cgi?id=2569294)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-125637 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125637 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2569294
- https://access.redhat.com/security/cve/CVE-2026-125637
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-125637
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125637"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- konflux-ci
through 0.2.2
Evidence 4
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Write-ups · 1
Establishes: Technical detail and context.
- Report
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-125637
Is CVE-2026-125637 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The proxy config generator does not validate hostname fields in the KonfluxUI custom resource, so injected text can alter the generated Caddyfile. This can bypass the proxy's authentication and impersonation checks, giving unauthenticated access to internal backend services and the Kubernetes API. A malformed hostname can also stop the proxy from starting.Source: bugzilla.redhat.com, access.redhat.com
Which versions are affected by CVE-2026-125637?
konflux-ci: through 0.2.2.Source: cve.now feed data
Am I affected, and how do I check?
The checked facts list konflux-ci versions from 0 through 0.2.2, and the issue was reproduced on the main branch and v0.2.2. Check the installed konflux-ci version and who holds write access to the KonfluxUI custom resource's hostname fields (tektonResults, kite, kubeArchive, watson).Source: bugzilla.redhat.com, access.redhat.com
How do I fix CVE-2026-125637?
The checked facts do not name a fixed release, so no upgrade target can be given from them. Check the konflux-ci advisory for a patched version.Source: bugzilla.redhat.com, access.redhat.com
What if there's no patch?
Limit write access to the KonfluxUI custom resource hostname fields, since the issue requires that access. The checked facts give no other workaround.Source: bugzilla.redhat.com, access.redhat.com