MARIN3R: Cross-Namespace Vulnerability in the Operator

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

8.7 · 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 · score source

EPSS

• CVE-2025-64171: 0.22% estimated exploitation activity in the next 30 days; percentile 12.17 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Cross-namespace Secret access vulnerability in DiscoveryServiceCertificate allows users to bypass RBAC and access Secrets in unauthorized namespaces. Affected Versions All versions prior to v0.13.4 Patched Versions v0.13.4 and later Impact Users with permission to create DiscoveryServiceCertificate resources in one namespace can indirectly read Secrets from other namespaces, completely bypassing Kubernetes RBAC security boundaries. Workarounds Restrict DiscoveryServiceCertificate create permissions to cluster administrators only until patched version is deployed. Credit Thanks to @debuggerchen for the responsible disclosure.

Published by the source

4 Nov 2025, 15:43 UTC

Last modified by the source

6 Nov 2025, 15:30 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-gf93-xccm-5g6j

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64171

Advisory: MARIN3R: Cross-Namespace Vulnerability in the Operator
IDs: CVE-2025-64171, GHSA-gf93-xccm-5g6j
Record: https://patchnext.com/advisories/cve-2025-64171 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/3scale-sre/marin3r 0.13.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/3scale-sre/marin3r: affected <= 0.13.3; fixed in 0.13.4

## Suggested inspection (read-only)
- Go github.com/3scale-sre/marin3r: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/3scale-sre/marin3r.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gf93-xccm-5g6j (GitHub-reviewed advisory GHSA-gf93-xccm-5g6j lists affected ranges: Go github.com/3scale-sre/marin3r >=0 <=0.13.3)

Commands are suggestions: review each one before running it.