GHSA-fh5w-p2j4-4p8x
MEDIUMExposure of Sensitive Information to an Unauthorized Actor in Jenkins Kubernetes Plugin
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.csanchez.jenkins.plugins:kubernetes☕org.csanchez.jenkins.plugins:kubernetes☕org.csanchez.jenkins.plugins:kubernetes☕org.csanchez.jenkins.plugins:kubernetesReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins Kubernetes Plugin prior to 1.27.4, 1.26.5, 1.25.4.1, and 1.21.6 includes a feature to replace placeholders in pod template and container template fields with environment variable values.
This feature allows low-privilege users to access possibly sensitive Jenkins controller environment variables.
Kubernetes Plugin 1.27.4, 1.26.5, 1.25.4.1, and 1.21.6 disables this feature.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.csanchez.jenkins.plugins:kubernetes | ≥ 1.27.0&&< 1.27.4 | 1.27.4 |
| ☕Maven | org.csanchez.jenkins.plugins:kubernetes | ≥ 1.26.0&&< 1.26.5 | 1.26.5 |
| ☕Maven | org.csanchez.jenkins.plugins:kubernetes | ≥ 1.22.0&&< 1.25.4.1 | 1.25.4.1 |
| ☕Maven | org.csanchez.jenkins.plugins:kubernetes | all versions | 1.21.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.csanchez.jenkins.plugins:kubernetes. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.csanchez.jenkins.plugins:kubernetes to 1.27.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fh5w-p2j4-4p8x 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.
How O3 protects you
O3 pinpoints whether GHSA-fh5w-p2j4-4p8x is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-fh5w-p2j4-4p8x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fh5w-p2j4-4p8x in your dependencies?
O3 detects GHSA-fh5w-p2j4-4p8x across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.