NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
MEDIUM severity

CVE-2022-36888 — hashicorp-vault-plugin

MEDIUMFix: jenkinsci/hashicorp-vault-plugin@3b38d76

CVE-2022-36888 is a medium-severity (CVSS 4.2) CWE-862 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.

Jenkins HashiCorp Vault Plugin does not perform permission checks in several HTTP endpoints that perform Vault connection tests

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.00%0.41%0.82%1.22%0.4%0.7%May 26Sep 26Nov 26

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

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

A missing permission check in Jenkins HashiCorp Vault Plugin 354.vdb_858fd6b_f48 and earlier allows attackers with Overall/Read permission to obtain credentials stored in Vault with attacker-specified path and keys.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavencom.datapipe.jenkins.plugins:hashicorp-vault-pluginall versions355.v3b_38d767a_b_a_8com.datapipe.jenkins.plugins:hashicorp-vault-plugin:355.v3b_38d767a_b_a_8

Affected Products

1 product · 1 configurations
Application
hashicorp vaultjenkins
≤ 354.vdb_858fd6b_f48
range

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. Fix

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

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

A missing permission check in Jenkins HashiCorp Vault Plugin 354.vdb_858fd6b_f48 and earlier allows attackers with Overall/Read permission to obtain credentials stored in Vault with attacker-specified path and keys.
O3 Security · Impact-Aware SCA

Is CVE-2022-36888 in your dependencies?

Find it across Maven, including transitive dependencies.

CVE-2022-36888: hashicorp-vault-plugin — Fix Available