How severe is CVE-2021-21632?

CVE-2021-21632 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-21632?

CVE-2021-21632 affects the following packages: org.jenkins-ci.plugins:dependency-track (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21632?

Update org.jenkins-ci.plugins:dependency-track to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21632 is resolved across your whole dependency graph.

How do I detect CVE-2021-21632 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:dependency-track, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-21632 if there is no patch (or I can't update yet)?

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.

Is CVE-2021-21632 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-21632 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-2021-21632?

CVE-2021-21632 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 65th 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.

What type of vulnerability is CVE-2021-21632?

CVE-2021-21632 is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-21632 published, and has it been updated?

CVE-2021-21632 was published on March 30, 2021 and was last updated on October 24, 2026. 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

MEDIUM severity

CVE-2021-21632 — dependency-track

MEDIUMFix: jenkinsci/dependency-track-plugin@70e7b82

CVE-2021-21632 is a medium-severity (CVSS 6.5) CWE-862 vulnerability in org.jenkins-ci.plugins:dependency-track. A fix is available for org.jenkins-ci.plugins:dependency-track — see the affected versions and patch details below.

Missing permission checks in Jenkins OWASP Dependency-Track Plugin allow capturing credentials

Also known asGHSA-xfrw-pcmc-r2p3

Published

Mar 30, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

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

☕org.jenkins-ci.plugins:dependency-track

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 OWASP Dependency-Track Plugin 3.1.0 and earlier does not perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing "Secret text" credentials stored in Jenkins. If no credentials ID is specified, the globally configured credential is used, if set up, and can likewise be captured.

Jenkins OWASP Dependency-Track Plugin 3.1.1 requires appropriate permissions for the affected HTTP endpoints.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:dependency-track`	all versions	3.1.1`org.jenkins-ci.plugins:dependency-track:3.1.1`

Affected Products

1 product · 1 configurations

Application

owasp dependency-trackjenkins

≤ 3.1.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 org.jenkins-ci.plugins:dependency-track, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:dependency-track to 3.1.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21632 is resolved across your whole dependency graph.
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

Jenkins OWASP Dependency-Track Plugin 3.1.0 and earlier does not perform permission checks in several HTTP endpoints. This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing \"Secret text\" credentials stored in Jenkins. If no credentials ID is specified, the globally configured credential is used, if set up, and can likewise be captured. Jenkins OWASP Dependency-Track Plugin 3.1.1 requires appropriate permissions for the affected HTTP endpoints.

O3 Security · Impact-Aware SCA

Is CVE-2021-21632 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-862CWE-862

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Mar 30, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-21632

GHSA-xfrw-pcmc-r2p3

References

Advisoryopenwall.com Advisoryjenkins.io · 2021 03 30 Advisorynvd.nist.gov · CVE 2021 21632 Webgithub.com · 70e7b82ad9a10499e628998a0bcb57c1481c66bc Packagegithub.com · dependency track plugin

Related vulnerabilities

Also affects dependency-track

This CVE is medium severity; 1 of 1 other CVE affecting dependency-track is rated as high or higher (top: high).

CVE-2021-21633

Same weakness: CWE-862

This CVE is medium severity; 7 of 7 other CVEs with CWE-862 are rated as high or higher (top: critical).

CVE-2026-103002CVE-2026-94619CVE-2026-85737CVE-2026-94618CVE-2026-102340CVE-2026-77596GHSA-47w9-6r3f-938gBrowse all CWE-862

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-21632 — dependency-track

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-21632 in your dependencies?