Skip to main content
VulnerabilityPublished Updated

CVE-2025-64171: MARIN3R · Cross-Namespace Vulnerability in the Operator

Affects github.com/3scale-sre/marin3rSource GCVE Database

0
Compare
Authoritative record:CVE-2025-64171· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 0.13.4 soon.

Data as of 13 Nov 2026, 19:44 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 0.13.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Nov 2025

  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 13 Nov 2026.

What to do

Upgrade github.com/3scale-sre/marin3r to 0.13.4.

Affected software

ProductAffectedFixed in
Gogithub.com/3scale-sre/marin3rAffected
  • <0.13.4
Fixed in
  • 0.13.4

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

AI-suggested

A patch is available in version 0.13.4 and later; upgrading to this version or beyond fully remediates the vulnerability. If you cannot patch yet, restrict permissions to create DiscoveryServiceCertificate resources to cluster administrators only to mitigate the risk.

Description

A cross-namespace secret access vulnerability exists in the DiscoveryServiceCertificate resource of the marin3r operator before version 0.13.4. This flaw allows users with permission to create DiscoveryServiceCertificate resources in one namespace to bypass Kubernetes RBAC controls and read Secrets from other namespaces. The issue is fixed in version 0.13.4 and later. Until patched, it is recommended to restrict DiscoveryServiceCertificate creation permissions to cluster administrators only.

References

Community reviews

Loading reviews…