Summary
@mittwald/kubernetes's secret contents leaked via debug logging
Workarounds
Disable debug logging entirely, or exclude the kubernetes:client debug item (for example, using DEBUG=*,-kubernetes:client).
References
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).
GHSA-G35X-J6JJ-8G7J has a CVSS score of 4.4 (Medium). The vector is requires local access, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.5.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Upgrade to 3.5.0 or newer.
Frequently Asked Questions
- What is GHSA-G35X-J6JJ-8G7J? GHSA-G35X-J6JJ-8G7J is a medium-severity security vulnerability in @mittwald/kubernetes (npm), affecting versions < 3.5.0. It is fixed in 3.5.0.
- How severe is GHSA-G35X-J6JJ-8G7J? GHSA-G35X-J6JJ-8G7J has a CVSS score of 4.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @mittwald/kubernetes are affected by GHSA-G35X-J6JJ-8G7J? @mittwald/kubernetes (npm) versions < 3.5.0 is affected.
- Is there a fix for GHSA-G35X-J6JJ-8G7J? Yes. GHSA-G35X-J6JJ-8G7J is fixed in 3.5.0. Upgrade to this version or later.
- Is GHSA-G35X-J6JJ-8G7J exploitable, and should I be worried? Whether GHSA-G35X-J6JJ-8G7J is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-G35X-J6JJ-8G7J is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-G35X-J6JJ-8G7J? Upgrade
@mittwald/kubernetesto 3.5.0 or later.