Skip to main content
CVE-2026-25639VulnerabilityPublished Updated

Red Hat Security Advisory: Kiali 2.17.4 for Red Hat OpenShift Service Mesh 3.2

Affects Red HatSource GCVE Database

0
Compare

Not known to be exploited.

Data as of 30 Oct 2026, 06:00 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 23 Feb 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 29 Oct 2026.

What to do

AI-suggested

Red Hat has released Kiali 2.17.4 for OpenShift Service Mesh 3.2 which includes the fix for this vulnerability. Users should upgrade to this version to remediate the issue. No effective mitigations that meet Red Hat's criteria for ease of use and applicability are currently available other than upgrading. Red Hat manages remediation through this updated release.

Description

A denial of service vulnerability exists in the Axios npm package used by Kiali 2.17.4 for Red Hat OpenShift Service Mesh 3.2. The flaw occurs in the mergeConfig function, which crashes with a TypeError when processing configuration objects containing the __proto__ key. An unauthenticated remote attacker can exploit this by supplying malicious JSON configuration objects, causing backend services that use Axios to crash and become unavailable. This issue affects server-side Node.js applications that dynamically merge untrusted JSON input into Axios configurations. Browser-based frontends and static configurations are not affected. Red Hat has released Kiali 2.17.4 to address this vulnerability.

References

Community reviews

Loading reviews…