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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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.

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.

What is the EPSS score for CVE-2022-25186?

CVE-2022-25186 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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 — hashicorp-vault-plugin

LOW

CVE-2022-25186 is a low-severity (CVSS 3.1) vulnerability in com.datapipe.jenkins.plugins:hashicorp-vault-plugin. A fix is available for com.datapipe.jenkins.plugins:hashicorp-vault-plugin — see the affected versions and patch details below.

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 Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2022-25186 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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`com.datapipe.jenkins.plugins:hashicorp-vault-plugin:336.v182c0fbaaeb7`

Affected Products

1 product · 1 configurations

Application

hashicorp vaultjenkins

≤ 3.8.0

range

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2022-25186 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works