Jenkins Static Analysis Utilities Plugin is vulnerable to Cross-site request forgery vulnerabilityGHSA-3v9f-4vff-rx42
MEDIUMFix: jenkinsci/analysis-core-plugin@3d7a0c7GHSA-3v9f-4vff-rx42 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in org.jvnet.hudson.plugins:analysis-core. A fix is available for org.jvnet.hudson.plugins:analysis-core — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jvnet.hudson.plugins:analysis-coreReal-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 analysis-core Plugin has the capability to allow other plugins to display trend graphs for their static analysis results. analysis-core Plugin provides the configuration form for the default settings of each graph.
The configuration form and form submission handler did not perform a permission check, allowing attackers with Job/Read access to change the per-job graph configuration defaults for all users.
Additionally, the form submission handler did not require POST requests, resulting in a cross-site request forgery vulnerability.
analysis-core Plugin now requires Job/Configure permission and POST requests to configure the per-job graph defaults for all users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jvnet.hudson.plugins:analysis-core | all versions | 1.96org.jvnet.hudson.plugins:analysis-core:1.96 |
Affected Products
static analysis utilitiesjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jvnet.hudson.plugins:analysis-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jvnet.hudson.plugins:analysis-core to 1.96 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3v9f-4vff-rx42 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
Is GHSA-3v9f-4vff-rx42 in your dependencies?
Find it across Maven, including transitive dependencies.