Namespace secret disclosure via automounted service-account token
Published Jun 10, 2026 · Updated Jun 10, 2026
Privilege management flaw in Fission before 1.23.0 allows remote attackers to read namespace secrets through deployed function code. The pool-manager and new-deploy builders assign fission-fetcher to runtime pods, so Kubernetes mounts its namespace-wide token in the untrusted function container. Creating or updating a function is required, and the inherited access covers secrets and configmaps readable by that service account.
Summary
What happened
Privilege management flaw in Fission before 1.23.0 allows remote attackers to read namespace secrets through deployed function code. The pool-manager and new-deploy builders assign fission-fetcher to runtime pods, so Kubernetes mounts its namespace-wide token in the untrusted function container. Creating or updating a function is required, and the inherited access covers secrets and configmaps readable by that service account.
The record
- CVE
- CVE-2026-46617
- Published
- Jun 10, 2026
- Updated
- Jun 10, 2026
- Vendor
- Fission
- Product
- Fission
- Classifications
- CWE-538, CWE-269, CWE-250, T1552.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2026CVE publishedPublication date reported by the CVE source.
- Jun 10, 2026Record 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=< 1.23.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
No public exploit references are available in this record.
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