Konflux-ci: ui proxy skips backend tls verification on non-openshift clusters, leaking a token that can impersonate anyone
Affects konflux-ci from 0.2.2-rc.2 on non-OpenShift Kubernetes clusters that lack a default service certificate authority. No vendor severity or fix is listed in the checked facts.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- 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, the open-source software-supply-chain platform, is affected in its user interface proxy when deployed on non-OpenShift clusters. The proxy skips TLS certificate checks for backend connections, so an attacker on the local network who intercepts that traffic could steal a cluster-wide token with impersonation rights and gain full administrative control of the cluster.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
A flaw was found in konflux-ci. This vulnerability allows privilege escalation when the user interface proxy automatically disables Transport Layer Security (TLS) certificate verification for connections to internal backend services in environments lacking a default service certificate authority. Because the proxy attaches a cluster-scoped authentication token with user impersonation rights to these requests, an adjacent network attacker capable of intercepting traffic can capture the credentials to gain full administrative control of the cluster.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- konflux-ci
From 0.2.2-rc.2
References 2
access.redhat.com
bugzilla.redhat.com
Questions about CVE-2026-117681
What does this mean?
The UI proxy does not verify the TLS certificate of the backend it connects to on non-OpenShift clusters. An attacker who intercepts the proxy's traffic could capture a cluster-scoped token with user impersonation rights, which the advisory says can give full administrative control of the cluster.Source: access.redhat.com
Am I affected, and how do I check?
The checked facts list konflux-ci from version 0.2.2-rc.2 onward, in deployments on non-OpenShift Kubernetes clusters where the expected service certificate authority is not present by default. To check a setup, confirm the konflux-ci version in use and whether the cluster provides a default service certificate authority.Source: access.redhat.com
What should I do about it?
The checked facts do not name a fixed version, so no upgrade target can be given from them. Check the project's advisory for a fixed release.Source: access.redhat.com
Is it 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 if there's no patch?
The checked facts give no workaround and no fix. Check the project's advisory for any guidance on limiting the affected proxy path until a fix is published.Source: access.redhat.com