Local secret disclosure via premature run-config expansion
Published May 12, 2025 · Updated May 12, 2025
Sensitive-data exposure in Stacklok ToolHive before 0.0.33 allows local users to read container secrets from run-config files. Before persistence, configureRunConfig expanded secret references into environment-variable values, so SaveState wrote both references and raw values to an unencrypted run config. Access to the initiating user's home folder and an existing config for a container that used secrets are required; unrelated stored secrets remain inaccessible.
Summary
What happened
Sensitive-data exposure in Stacklok ToolHive before 0.0.33 allows local users to read container secrets from run-config files. Before persistence, configureRunConfig expanded secret references into environment-variable values, so SaveState wrote both references and raw values to an unencrypted run config. Access to the initiating user's home folder and an existing config for a container that used secrets are required; unrelated stored secrets remain inaccessible.
The record
- CVE
- CVE-2025-47274
- Published
- May 12, 2025
- Updated
- May 12, 2025
- Vendor
- Stacklok
- Product
- ToolHive
- Classifications
- CWE-311, T1552.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2025CVE publishedPublication date reported by the CVE source.
- May 12, 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=< 0.0.33
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