CVE-2026-32280VulnerabilityPublished 12 May 2026Updated 30 Oct 2026

Red Hat Security Advisory: Kiali 2.11.10 for Red Hat OpenShift Service Mesh 3.1

Affects Red HatSource GCVE Database

Compare

Mentioned vulnerabilities

Authoritative record:CVE-2026-32280· High 7.5

Not known to be exploited · CVSS 7.5 High : upgrade Red Hat x509 to 1.26.2 or 1.25.9 soon.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.26.2, 1.25.9

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade crypto/x509 to 1.26.2 or 1.25.9.

Affected software

Product	Affected	Fixed in
Go standard librarycrypto/x509	Affected >=1.26.0-0 <1.26.2	Fixed in 1.26.2
Go standard librarycrypto/x509	Affected <1.25.9	Fixed in 1.25.9
Gocrypto/x509`pkg:golang/crypto/x509`Other threats	Affected <1.25.9 >=1.26.0-0 <1.26.2	Fixed in 1.25.9 1.26.2
Gogithub.com/golang/go/src/crypto/x509`pkg:golang/github.com/golang/go/src/crypto/x509`Other threats	Affected =0 =1.26.0-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

A fixed version, Kiali 2.11.10 for Red Hat OpenShift Service Mesh 3.1, is available and should be deployed to remediate these vulnerabilities. Users should update to this version following Red Hat's official documentation at https://docs.redhat.com/en/documentation/red_hat_openshift_service_mesh/3.1/html/observability/kiali-operator-provided-by-red-hat. No additional mitigations are specified by the vendor advisory. Red Hat Product Security rates this update as critical and recommends prompt application of the fix.

Description

Kiali 2.11.10, for Red Hat OpenShift Service Mesh 3.1, provides observability for the service mesh by offering a visual representation of the mesh topology and metrics, helping users monitor, trace, and manage efficiently. Security Fix(es): * CVE-2026-32280 Go: Denial of Service vulnerability in certificate chain building (OSSM-13247) * CVE-2026-40895 follow-redirects: Information disclosure via cross-domain redirects (OSSM-13555, OSSM-13559) * CVE-2026-42033 Axios: HTTP Transport Hijacking via Prototype Pollution (OSSM-13692, OSSM-13696) * CVE-2026-42035 Axios: Arbitrary HTTP header injection via prototype pollution (OSSM-13601, OSSM-13602) * CVE-2026-42043 Axios: NO_PROXY bypass via crafted URL (OSSM-13714, OSSM-13718) * CVE-2026-42039 Axios: Denial of Service via unbounded recursion in toFormData with deeply nested request data (OSSM-13728, OSSM-13732) * CVE-2026-42041 Axios: Authentication bypass due to prototype pollution of HTTP error handling (OSSM-13742, OSSM-13746) * CVE-2026-42044 Axios: Invisible JSON Response Tampering via Prototype Pollution Gadget (OSSM-13781, OSSM-13782) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Impact

The vulnerabilities can cause denial of service conditions by exhausting system resources during TLS certificate chain processing or HTTP request handling. Prototype pollution in Axios can lead to HTTP transport hijacking, arbitrary HTTP header injection, authentication bypass, and invisible JSON response tampering, potentially compromising the integrity and availability of affected services. Information disclosure via cross-domain redirects may expose sensitive data. These impacts affect systems running Kiali 2.11.10 in Red Hat OpenShift Service Mesh 3.1 environments.

Summary

Kiali 2.11.10 for Red Hat OpenShift Service Mesh 3.1 fixes several security vulnerabilities. Notably, CVE-2026-32280 is a denial of service vulnerability in the Go standard library's crypto/x509 and crypto/tls packages caused by excessive intermediate certificates during certificate chain building, leading to resource exhaustion. Additional vulnerabilities involve the Axios HTTP client library, including prototype pollution that enables HTTP transport hijacking, arbitrary header injection, NO_PROXY bypass, denial of service via unbounded recursion, authentication bypass, and JSON response tampering. Another vulnerability involves information disclosure via cross-domain redirects in the follow-redirects package. Red Hat rates these issues as critical and provides updated container images and documentation for remediation.

CWE-770Allocation of Resources Without Limits or Throttling (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #25
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
Requirements
Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
Architecture and Design
Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.4 (opens in a new tab)
V13.4.1 (opens in a new tab)
V11.1.4 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Exponential Data Expansion (opens in a new tab)
Serialized Data Parameter Blowup (opens in a new tab)
Serialized Data with Nested Payloads (opens in a new tab)
Oversized Serialized Data Payloads (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-212Improper Removal of Sensitive Information Before Storage or Transfer (opens in a new tab)
Base weakness
The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
Requirements
Clearly specify which information should be regarded as private or sensitive, and require that the product offers functionality that allows the user to cleanse the sensitive information from the resource before it is published or exported to other parties.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
Implementation · Operation · Attack Surface Reduction
Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed.
OWASP ASVS 4.0.3
V8.3.2 (opens in a new tab)
Attack patterns
Windows ::DATA Alternate Data Stream (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-915Improperly Controlled Modification of Dynamically-Determined Object Attributes (opens in a new tab)
Base weaknessOWASP Top 10 A08:2025: Software or Data Integrity Failures (opens in a new tab)
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
Implementation
If available, use features of the language or framework that allow specification of allowlists of attributes or fields that are allowed to be modified. If possible, prefer allowlists over denylists.
Architecture and Design · Implementation
If available, use the signing/sealing features of the programming language to assure that deserialized data has not been tainted. For example, a hash-based message authentication code (HMAC) could be used to ensure that data has not been modified.
Implementation · Input Validation
For any externally-influenced input, check the input against an allowlist of internal object attributes or fields that are allowed to be modified.
OWASP Cheat Sheets
Mass Assignment (opens in a new tab)
Software Supply Chain Security (opens in a new tab)
Infrastructure as Code (opens in a new tab)
OWASP ASVS 4.0.3
V5.1.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-918Server-Side Request Forgery (opens in a new tab)
Base weaknessCWE Top 25 (2025): #22OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Implementation · Operation
If there is a known list of applications, IP, hostname, and/or domains to which the product is allowed to communicate, then use allowlists to ensure that outgoing requests are restricted to these known entities. The allowlists could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Operation
If the product is expected to be able to connect to arbitrary IP addresses or domains, consider using a denylist that includes private network addresses, internal domain names, etc. The denylist could be in the application code or possibly enforced by firewalls or network segmentation.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Server Side Request Forgery Prevention (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
Cross Site Scripting Prevention (opens in a new tab)
DOM based XSS Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.6.1 (opens in a new tab)
V5.2.6 (opens in a new tab)
Attack patterns
Server Side Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 14 Aug 2026, 23:29 UTC

WeaknessesCWE-770, CWE-212, CWE-915 +1

Technical details

References

Community reviews

Related threats