What is CVE-2025-64171?

CVE-2025-64171 is a high-severity missing authorization vulnerability in github.com/3scale-sre/marin3r (go), affecting versions <= 0.13.3. It is fixed in 0.13.4. The application does not perform an authorization check before performing a sensitive operation.

Which versions of github.com/3scale-sre/marin3r are affected by CVE-2025-64171?

github.com/3scale-sre/marin3r (go) versions <= 0.13.3 is affected.

Is there a fix for CVE-2025-64171?

Yes. CVE-2025-64171 is fixed in 0.13.4. Upgrade to this version or later.

Is CVE-2025-64171 exploitable, and should I be worried?

Whether CVE-2025-64171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-64171 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-64171 in github.com/3scale-sre/marin3r

Q: Which versions of github.com/3scale-sre/marin3r are affected by CVE-2025-64171?

github.com/3scale-sre/marin3r (go) versions <= 0.13.3 is affected.

Q: Is there a fix for CVE-2025-64171?

Yes. CVE-2025-64171 is fixed in 0.13.4. Upgrade to this version or later.

Q: Is CVE-2025-64171 exploitable, and should I be worried?

Whether CVE-2025-64171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-64171 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-64171?

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

Summary

MARIN3R: Cross-Namespace Vulnerability in the Operator

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

Workarounds

Restrict DiscoveryServiceCertificate create permissions to cluster administrators
only until patched version is deployed.

Credit

Thanks to @debuggerchen for the responsible disclosure.

Impact

Users with permission to create DiscoveryServiceCertificate resources in one
namespace can indirectly read Secrets from other namespaces, completely
bypassing Kubernetes RBAC security boundaries.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

github.com/3scale-sre/marin3r (<= 0.13.3)

Security releases

github.com/3scale-sre/marin3r → 0.13.4 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade github.com/3scale-sre/marin3r to 0.13.4 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-64171? CVE-2025-64171 is a high-severity missing authorization vulnerability in github.com/3scale-sre/marin3r (go), affecting versions <= 0.13.3. It is fixed in 0.13.4. The application does not perform an authorization check before performing a sensitive operation.
Which versions of github.com/3scale-sre/marin3r are affected by CVE-2025-64171? github.com/3scale-sre/marin3r (go) versions <= 0.13.3 is affected.
Is there a fix for CVE-2025-64171? Yes. CVE-2025-64171 is fixed in 0.13.4. Upgrade to this version or later.
Is CVE-2025-64171 exploitable, and should I be worried? Whether CVE-2025-64171 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-64171 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-64171? Upgrade github.com/3scale-sre/marin3r to 0.13.4 or later.