CVE-2025-25209 json
Rhcl: sharedsecretref can be used to leak secrets severity
published 2025-06-09 17 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-17428
- cvss
- 5.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
The AuthPolicy metadata on Red Hat Connectivity Link contains an object which stores secretes, however it assumes those secretes are already in the kuadrant-system instead of copying it to the referred namespace. This creates space for a malicious actor with a developer persona access to leak those secrets over HTTP connection, as long the attacker knows the name of the targeted secrets and those secrets are limited to one line only.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2025-25209 updated cvss 5.7
RHCL: sharedSecretRef Can Be Used To Leak Secrets Severity
-
Red Hat Connectivity Link 1 rhcl-1/rhcl-operator-containeraffected: workaround, no fix available “There's no known mitigation for this issue.”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 17 mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.7 | CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L |
Affected products
- Red Hat Red Hat Connectivity Link 1
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
References
-
access.redhat.com
/security/cve/CVE-2025-25209
vdb-entry
-
bugzilla.redhat.com
/show_bug.cgi?id=2347438
issue-tracking
Sources
- CVE List CVE-2025-25209
- NVD CVE-2025-25209
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.