How severe is GHSA-gf93-xccm-5g6j?

No CVSS score has been assigned to GHSA-gf93-xccm-5g6j yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gf93-xccm-5g6j?

GHSA-gf93-xccm-5g6j affects the following packages: github.com/3scale-sre/marin3r (Go). Ecosystems affected: Go.

How do I fix GHSA-gf93-xccm-5g6j?

Update github.com/3scale-sre/marin3r to 0.13.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gf93-xccm-5g6j is resolved across your whole dependency graph.

How do I detect GHSA-gf93-xccm-5g6j in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/3scale-sre/marin3r, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gf93-xccm-5g6j if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-gf93-xccm-5g6j actively exploited in the wild?

No public exploit code has been indexed for GHSA-gf93-xccm-5g6j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gf93-xccm-5g6j?

GHSA-gf93-xccm-5g6j has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 12th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gf93-xccm-5g6j?

GHSA-gf93-xccm-5g6j is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gf93-xccm-5g6j published, and has it been updated?

GHSA-gf93-xccm-5g6j was published on November 4, 2025 and was last updated on November 17, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

MARIN3R: Cross-Namespace Vulnerability in the OperatorGHSA-gf93-xccm-5g6j

Fix: 3scale-sre/marin3r#294

GHSA-gf93-xccm-5g6j is a CWE-862 vulnerability in github.com/3scale-sre/marin3r. A fix is available for github.com/3scale-sre/marin3r — see the affected versions and patch details below.

Also known asCVE-2025-64171GO-2025-4093

Published

Nov 4, 2025

Updated

Nov 17, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gf93-xccm-5g6j.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs12th percentile — riskier than 12% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐹github.com/3scale-sre/marin3r

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/3scale-sre/marin3r`	all versions	0.13.4`go get github.com/3scale-sre/marin3r@v0.13.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/3scale-sre/marin3r, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/3scale-sre/marin3r to 0.13.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gf93-xccm-5g6j is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

The severity is considered Moderate, because exploitation can be done over the network via the K8s API (AV:N), no unusual conditions are required for the attack (AC:L), however, the attacker must already hold permissions to create DiscoveryServiceCertificate objects in some namespace, without requiring elevated…

Workaround published by Red Hat

As an interim workaround, restrict permissions so that only trusted cluster administrators can create DiscoveryServiceCertificate resources until the update is applied

Source: Red Hat security advisory for GHSA-gf93-xccm-5g6j (CC BY 4.0)

Frequently Asked Questions

## 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.

O3 Security · Impact-Aware SCA

Is GHSA-gf93-xccm-5g6j in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works