Kubernetes token disclosure via kubeconfig server redirection
Published Mar 31, 2025 · Updated Mar 31, 2025
Kubernetes token disclosure in JumpServer before 3.10.18 and 4.0.0 through 4.7 allows remote authenticated users to capture cluster tokens. The Kubernetes session passes a user-edited kubeconfig server address to kubectl, which sends the bearer token to the substituted endpoint. A low-privileged account with Kubernetes-session access is sufficient, and the captured token grants the cluster access permitted by that credential.
Summary
What happened
Kubernetes token disclosure in JumpServer before 3.10.18 and 4.0.0 through 4.7 allows remote authenticated users to capture cluster tokens. The Kubernetes session passes a user-edited kubeconfig server address to kubectl, which sends the bearer token to the substituted endpoint. A low-privileged account with Kubernetes-session access is sufficient, and the captured token grants the cluster access permitted by that credential.
The record
- CVE
- CVE-2025-27095
- Published
- Mar 31, 2025
- Updated
- Mar 31, 2025
- Vendor
- JumpServer
- Product
- JumpServer
- Classifications
- CWE-266, T1528
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 2025CVE publishedPublication date reported by the CVE source.
- Mar 31, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.10.18
- Affected versionversion=>= 4.0.0, < 4.8.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Upstream kubeconfig-redirection reproduction stepsproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo