How severe is CVE-2022-25186?

CVE-2022-25186 has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2022-25186?

CVE-2022-25186 affects the following packages: com.datapipe.jenkins.plugins:hashicorp-vault-plugin (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-25186?

Update com.datapipe.jenkins.plugins:hashicorp-vault-plugin to 336.v182c0fbaaeb7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25186 is resolved across your whole dependency graph.

How do I detect CVE-2022-25186 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datapipe.jenkins.plugins:hashicorp-vault-plugin. 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.

How do I mitigate CVE-2022-25186 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.

How does O3 Security protect against CVE-2022-25186?

O3 pinpoints whether CVE-2022-25186 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2022-25186 actively exploited in the wild?

No public exploit code has been indexed for CVE-2022-25186 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 CVE-2022-25186 published, and has it been updated?

CVE-2022-25186 was published on February 16, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

CVE-2022-25186

LOW

CVE-2022-25186 is a low-severity (CVSS 3.1) vulnerability in com.datapipe.jenkins.plugins:hashicorp-vault-plugin. O3 Security confirms whether CVE-2022-25186 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Agent-to-controller security bypass in Jenkins HashiCorp Vault Plugin

Published

Feb 16, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

☕com.datapipe.jenkins.plugins:hashicorp-vault-plugin

Real-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 3.8.0 and earlier implements functionality that allows agent processes to retrieve any Vault secrets for use on the agent, allowing attackers able to control agent processes to obtain Vault secrets for an attacker-specified path and key.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.datapipe.jenkins.plugins:hashicorp-vault-plugin`	all versions	336.v182c0fbaaeb7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.datapipe.jenkins.plugins:hashicorp-vault-plugin. 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 com.datapipe.jenkins.plugins:hashicorp-vault-plugin to 336.v182c0fbaaeb7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-25186 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 CVE-2022-25186 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 CVE-2022-25186. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-25186 in your dependencies?

O3 detects CVE-2022-25186 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works