How severe is CVE-2021-21670?

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

Which packages are affected by CVE-2021-21670?

CVE-2021-21670 affects the following packages: org.jenkins-ci.main:jenkins-core (Maven), org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21670?

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

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

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

How do I mitigate CVE-2021-21670 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-2021-21670 actively exploited in the wild?

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

CVE-2021-21670 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 81th 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-2021-21670 published, and has it been updated?

CVE-2021-21670 was published on June 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-21670 — jenkins-core

MEDIUMFix: jenkinsci/jenkins@86b7d7e

CVE-2021-21670 is a medium-severity (CVSS 4.3) vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.

Improper permission checks allow canceling queue items and aborting builds in Jenkins

Also known asBIT-jenkins-2021-21670GHSA-q4wp-8c99-69pw

Published

Jun 30, 2021

Updated

Oct 24, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs81th percentile — riskier than 81% 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

2 pkgs affected

☕org.jenkins-ci.main:jenkins-core☕org.jenkins-ci.main:jenkins-core

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 2.300, LTS 2.289.2 requires that users have Item/Read permission for applicable types in addition to Item/Cancel permission.

As a workaround on earlier versions of Jenkins, do not grant Item/Cancel permission to users who do not have Item/Read permission.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	2.289.2`org.jenkins-ci.main:jenkins-core:2.289.2`
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 2.292&&< 2.300	2.300`org.jenkins-ci.main:jenkins-core:2.300`

Affected Products

1 product · 2 configurations

Application

jenkinsjenkins

< 2.300

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.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.289.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21670 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

Workaround published by Red Hat

As a workaround on earlier versions of Jenkins, do not grant Item/Cancel permission to users who do not have Item/Read permission.

Source: Red Hat security advisory for CVE-2021-21670 (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat OpenShift Container Platform 4.6	`jenkins-0:2.289.2.1629437819-1.el8`	RHBA-2021:3396
Red Hat OpenShift Container Platform 4.7	`jenkins-0:2.289.2.1628252553-1.el8`	RHBA-2021:3033
Red Hat OpenShift Container Platform 4.8	`jenkins-0:2.289.3.1633554819-1.el8`	RHSA-2021:3820

Frequently Asked Questions

Jenkins 2.299 and earlier, LTS 2.289.1 and earlier allows users to cancel queue items and abort builds of jobs for which they have Item/Cancel permission even when they do not have Item/Read permission. Jenkins 2.300, LTS 2.289.2 requires that users have Item/Read permission for applicable types in addition to Item/Cancel permission. As a workaround on earlier versions of Jenkins, do not grant Item/Cancel permission to users who do not have Item/Read permission.

O3 Security · Impact-Aware SCA

Is CVE-2021-21670 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.3/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Raw vector

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

Weaponization

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

OpenSSF Scorecard

Package health score

jenkins

6.4/10

Code-Review6/10

Maintained10/10

Branch-Protection3/10

Assessed Oct 26, 2026

Timeline

Disclosed

Jun 30, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-21670

GHSA-q4wp-8c99-69pw

BIT-jenkins-2021-21670

References

Advisoryopenwall.com Advisoryjenkins.io · 2021 06 30 Advisorynvd.nist.gov · CVE 2021 21670 Webgithub.com · 86b7d7e789586575522650c60d591605facb1d70 Packagegithub.com · jenkins

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting jenkins-core are rated as high or higher (top: high).

CVE-2026-53436CVE-2026-53437CVE-2026-53440CVE-2026-53441CVE-2026-53439CVE-2026-53435CVE-2026-53442CVE-2026-53438

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-21670 — jenkins-core

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

Fixing This On Your OS

Frequently Asked Questions

Is CVE-2021-21670 in your dependencies?