@mittwald/kubernetes's secret contents leaked via debug logging
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-532.
Summary
### Impact When debug logging is enabled (via `DEBUG` environment variable), the Kubernetes client may log all response bodies into the debug log -- including sensitive data from `Secret` resources. When running in a Kubernetes cluster, this might expose sensitive information to users who are _not_ authorised to access secrets, but have access to Pod logs (either directly using kubectl, or by Pod logs being shipped elsewhere). ### Patches Upgrade to 3.5.0 or newer. ### Workarounds Disable debug logging entirely, or exclude the `kubernetes:client` debug item (for example, using `DEBUG=*,-kubernetes:client`). ### References - https://cwe.mitre.org/data/definitions/532.html
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | @mittwald/kubernetes (npm) | before 3.5.0 | 3.5.0 | Patch available | GHSA-g35x-j6jj-8g7j |
- @mittwald/kubernetes (npm) Vendor— Affected before 3.5.0 Fixed in 3.5.0 Patch available GHSA-g35x-j6jj-8g7j
Remediation
- Fix · GHSA-g35x-j6jj-8g7j @mittwald/kubernetes (npm) Fixed in 3.5.0 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-g35x-j6jj-8g7j
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences