How severe is GHSA-fcxq-v2r3-cc8h?

No CVSS score has been assigned to GHSA-fcxq-v2r3-cc8h yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-fcxq-v2r3-cc8h?

GHSA-fcxq-v2r3-cc8h affects the following packages: github.com/external-secrets/external-secrets (Go). Ecosystems affected: Go.

How do I fix GHSA-fcxq-v2r3-cc8h?

Update github.com/external-secrets/external-secrets to 0.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fcxq-v2r3-cc8h is resolved across your whole dependency graph.

How do I detect GHSA-fcxq-v2r3-cc8h in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/external-secrets/external-secrets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-fcxq-v2r3-cc8h if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-fcxq-v2r3-cc8h?

O3 pinpoints whether GHSA-fcxq-v2r3-cc8h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-fcxq-v2r3-cc8h actively exploited in the wild?

No public exploit code has been indexed for GHSA-fcxq-v2r3-cc8h 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-fcxq-v2r3-cc8h?

GHSA-fcxq-v2r3-cc8h has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 24th 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-fcxq-v2r3-cc8h?

GHSA-fcxq-v2r3-cc8h is classified as CWE-284 (CWE-284). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-fcxq-v2r3-cc8h published, and has it been updated?

GHSA-fcxq-v2r3-cc8h was published on August 13, 2025 and was last updated on August 18, 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

GHSA-fcxq-v2r3-cc8h

External Secrets Operator's Missing Namespace Restriction Allows Unauthorized Secret Access

Also known asCVE-2025-55196GO-2025-3885

Published

Aug 13, 2025

Updated

Aug 18, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk24th percentile+0.22%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

1 pkg affected

🐹github.com/external-secrets/external-secrets

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

A vulnerability was discovered in the External Secrets Operator where the List() calls for Kubernetes Secret and SecretStore resources performed by the PushSecret controller did not apply a namespace selector.
This flaw allowed an attacker to use label selectors to list and read secrets/secret-stores across the cluster, bypassing intended namespace restrictions.

Impact

An attacker with the ability to create or update PushSecret resources and control SecretStore configurations could exploit this vulnerability to exfiltrate sensitive data from arbitrary namespaces.
This could lead to full disclosure of Kubernetes secrets, including credentials, tokens, and other sensitive information stored in the cluster.

Exploitability

To exploit this vulnerability, an attacker must:

Have permissions to create or update PushSecret resources.
Control one or more SecretStore resources.

With these conditions met, the attacker could leverage label selectors to list secrets from any namespace and retrieve their contents.

Affected Versions

Vulnerable: v0.15.0 – v0.19.1
Not Vulnerable: v0.19.2 and later

Fix

The vulnerability was addressed in v0.19.2 by adding namespace restrictions to the List() calls for both PushSecret and SecretStore controllers.
This ensures that only secrets in the intended namespace are accessible.

Relevant fixes:

#5133 – Enforce namespace selector for PushSecret List() calls
#5109 – Enforce namespace selector for SecretStore List() calls

Mitigation

If upgrading to v0.19.2 or later is not immediately possible, the following mitigations are recommended:

Restrict RBAC permissions so that only trusted service accounts can create or update PushSecret and SecretStore resources.
Audit existing PushSecret and SecretStore resources to ensure they are controlled by trusted parties.
Review Network Policies to prevent data exfiltration

Credit

This vulnerability was reported by @gracedo and @moolen

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/external-secrets/external-secrets`	≥ 0.15.0&&< 0.19.2	0.19.2

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/external-secrets/external-secrets. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/external-secrets/external-secrets to 0.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fcxq-v2r3-cc8h is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-fcxq-v2r3-cc8h is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-fcxq-v2r3-cc8h. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## Summary A vulnerability was discovered in the External Secrets Operator where the `List()` calls for Kubernetes Secret and SecretStore resources performed by the `PushSecret` controller did not apply a namespace selector. This flaw allowed an attacker to use label selectors to list and read secrets/secret-stores across the cluster, bypassing intended namespace restrictions. --- ## Impact An attacker with the ability to create or update `PushSecret` resources and control `SecretStore` configurations could exploit this vulnerability to exfiltrate sensitive data from arbitrary namespaces.

O3 Security · Impact-Aware SCA

Is GHSA-fcxq-v2r3-cc8h in your dependencies?

O3 detects GHSA-fcxq-v2r3-cc8h across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works