CVE-2025-67642 — hashicorp-vault-plugin
MEDIUMCVE-2025-67642 is a medium-severity (CVSS 4.3) CWE-282 vulnerability in com.datapipe.jenkins.plugins:hashicorp-vault-plugin. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Jenkins HashiCorp Vault Plugin exposes system-scoped Vault credentials
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-67642.
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
com.datapipe.jenkins.plugins:hashicorp-vault-pluginReal-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 HashiCorp Vault Plugin 371.v884a_4dd60fb_6 and earlier does not set the appropriate context for Vault credentials lookup, allowing attackers with Item/Configure permission to access and potentially capture Vault credentials they are not entitled to.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.datapipe.jenkins.plugins:hashicorp-vault-plugin | all versions | No fix |
Affected Products
hashicorp vaultjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datapipe.jenkins.plugins:hashicorp-vault-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of com.datapipe.jenkins.plugins:hashicorp-vault-plugin for CVE-2025-67642. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
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 CVE-2025-67642 in your dependencies?
Find it across Maven, including transitive dependencies.