CVE-2025-59530VulnerabilityPublished 4 Dec 2025Updated 5 Nov 2026

Red Hat Security Advisory: Submariner v0.22 security fixes and container updates

Affects Red Hat Submariner v0.22Source GCVE Database

Compare

Not known to be exploited.

Data as of 5 Nov 2026, 20:48 UTC

Severity

Medium

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

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Dec 2025
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 5 Nov 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

AI-suggested

Red Hat has released updated Submariner v0.22 container images and security fixes as part of Red Hat Advanced Cluster Management for Kubernetes v2.15. Users should apply these official updates to remediate the vulnerability. Refer to the Red Hat advisory RHSA-2025:22784 and the upstream Submariner release notes for detailed upgrade instructions. No additional mitigation actions are indicated beyond applying the provided updates.

Description

Red Hat has issued a security advisory for Submariner v0.22, a Kubernetes operator enabling cross-cluster connectivity for services and pods. The advisory addresses security fixes and container updates with a moderate security impact. Submariner implements the Multi-Cluster Services API (KEP-1645) to allow direct networking between pods and services across Kubernetes clusters. The update is part of Red Hat Advanced Cluster Management for Kubernetes v2.15. No known exploits in the wild have been reported. The advisory provides updated container images and references upstream release notes for details.

Impact

The vulnerability has a moderate security impact as rated by Red Hat Product Security. It affects the ability of Submariner to securely enable cross-cluster connectivity between Kubernetes pods and services. No active exploitation has been observed. The update mitigates potential risks associated with this vulnerability by providing security fixes and updated container images.

Summary

This advisory concerns Submariner v0.22, a Kubernetes operator facilitating cross-cluster networking by implementing KEP-1645. Red Hat's update includes security fixes and updated container images to address vulnerabilities rated as moderate impact. The advisory is specific to Red Hat Advanced Cluster Management for Kubernetes v2.15. The update resolves downstream-specific issues and is documented in Red Hat's official errata and product documentation. There are no known active exploits targeting this vulnerability (CVE-2025-59530).

CWE-617Reachable Assertion (opens in a new tab)
Base weakness
The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.
Implementation
If the assertion statement is required (e.g., for security or reliability), change the invoking code to avoid the conditions that trigger the assertion.
Implementation
Consider changing the assertion to some other less "fatal" error. This might not be easy to implement, since other code may be needed to handle the error.
Implementation
Make sensitive open/close operations non-reachable from directly user-controlled data (e.g. open/close resources)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 5 Nov 2026, 20:48 UTC

WeaknessesCWE-617

Technical details

References

Community reviews

Related threats