Skip to main content
VulnerabilityPublished

CVE-2026-114217: konflux-ci · CWE-312

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-114217· High 8.6

Not known to be exploited · CVSS 8.6 High.

Data as of 31 Oct 2026, 10:38 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (redhat)CVSS 3.18.6
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
konflux-ciAffected
  • >=0.2.2 <=0.2.2
  • >=0.2.3-rc.0 <=0.2.3-rc.0
Fixed in–
GitHubkonflux-cipkg:github/konflux-ciOther threatsAffected
  • >=0.2.2 <=0.2.2
  • >=0.2.3-rc.0 <=0.2.3-rc.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

According to the Red Hat advisory, no mitigation is currently available or meets the criteria for ease of use, applicability, and stability. Users should be aware that this vulnerability requires local code execution access on the CI runner, so restricting access to CI environments and runners is critical. Monitor vendor advisories for any future patches or mitigations.

Description

A vulnerability in konflux-ci's Continuous Integration automation scripts causes sensitive GitHub access tokens to be stored in plaintext on the runner without cleanup after execution. A local attacker with access to the CI environment can read these tokens and gain unauthorized repository access, potentially modifying source code or release artifacts. Exploitation requires prior code execution access on the CI runner. No effective mitigation or patch is currently available according to the vendor advisory.

References

Community reviews

Loading reviews…