How severe is GHSA-g35x-j6jj-8g7j?

GHSA-g35x-j6jj-8g7j has a CVSS score of 4.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-g35x-j6jj-8g7j?

GHSA-g35x-j6jj-8g7j affects the following packages: @mittwald/kubernetes (npm). Ecosystems affected: npm.

How do I fix GHSA-g35x-j6jj-8g7j?

Update @mittwald/kubernetes to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g35x-j6jj-8g7j is resolved across your whole dependency graph.

How do I detect GHSA-g35x-j6jj-8g7j in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @mittwald/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g35x-j6jj-8g7j if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g35x-j6jj-8g7j actively exploited in the wild?

No public exploit code has been indexed for GHSA-g35x-j6jj-8g7j yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g35x-j6jj-8g7j published, and has it been updated?

GHSA-g35x-j6jj-8g7j was published on May 2, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

MEDIUM severity

@mittwald/kubernetes's secret contents leaked via debug loggingGHSA-g35x-j6jj-8g7j

MEDIUMFix: mittwald/node-kubernetes@04f6809

GHSA-g35x-j6jj-8g7j is a medium-severity (CVSS 4.4) vulnerability in @mittwald/kubernetes. A fix is available for @mittwald/kubernetes — see the affected versions and patch details below.

Published

May 2, 2023

Updated

May 2, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of May 2, 2023 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@mittwald/kubernetesnpm

66downloads / week

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@mittwald/kubernetes`	all versions	3.5.0`npm install @mittwald/kubernetes@3.5.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @mittwald/kubernetes, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @mittwald/kubernetes to 3.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g35x-j6jj-8g7j is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### 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=*,-ku

O3 Security · Impact-Aware SCA

Is GHSA-g35x-j6jj-8g7j in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works