How severe is CVE-2021-21645?

CVE-2021-21645 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-21645?

CVE-2021-21645 affects the following packages: org.jenkins-ci.plugins:config-file-provider (Maven). Ecosystems affected: Maven.

How do I fix CVE-2021-21645?

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

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

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

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

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

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

CVE-2021-21645 was published on April 21, 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-21645 — config-file-provider

MEDIUMFix: jenkinsci/config-file-provider-plugin@b7f3c51

CVE-2021-21645 is a medium-severity (CVSS 4.3) vulnerability in org.jenkins-ci.plugins:config-file-provider. A fix is available for org.jenkins-ci.plugins:config-file-provider — see the affected versions and patch details below.

Missing permission checks in Jenkins Config File Provider Plugin allow enumerating configuration file IDs

Also known asGHSA-2959-fj73-hm8p

Published

Apr 21, 2021

Updated

Oct 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% 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:config-file-provider

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 Config File Provider Plugin 3.7.0 and earlier does not perform permission checks in several HTTP endpoints.

This allows attackers with Overall/Read permission to enumerate configuration file IDs.

An enumeration of configuration file IDs in Jenkins Config File Provider Plugin 3.7.1 requires the appropriate permissions.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:config-file-provider`	all versions	3.7.1`org.jenkins-ci.plugins:config-file-provider:3.7.1`

Affected Products

1 product · 1 configurations

Application

config file providerjenkins

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

Product	Fixed in	Advisory
Red Hat Migration Toolkit for Containers 1.4	`rhmtc/openshift-migration-controller-rhel8:v1.4.6-4`	RHBA-2021:2854
Red Hat OpenShift Container Platform 3.11	`jenkins-2-plugins-0:3.11.1624366838-1.el7`	RHSA-2021:2517
Red Hat OpenShift Container Platform 4.5	`jenkins-2-plugins-0:4.5.1623326336-1.el7`	RHSA-2021:2431
Red Hat OpenShift Container Platform 4.6	`jenkins-2-plugins-0:4.6.1623162648-1.el8`	RHBA-2021:2407
Red Hat OpenShift Container Platform 4.7	`cri-o-0:1.20.2-12.rhaos4.7.git9f7be76.el7`	RHSA-2021:2122
Red Hat OpenShift Container Platform 4.8	`atomic-openshift-service-idler-0:4.8.0-202106281541.p0.git.39cfc66.assembly.stream.el8`	RHSA-2021:2437

Frequently Asked Questions

Jenkins Config File Provider Plugin 3.7.0 and earlier does not perform permission checks in several HTTP endpoints. This allows attackers with Overall/Read permission to enumerate configuration file IDs. An enumeration of configuration file IDs in Jenkins Config File Provider Plugin 3.7.1 requires the appropriate permissions.

O3 Security · Impact-Aware SCA

Is CVE-2021-21645 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

Low

Integrity

None

Availability

None

Raw vector

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

Weaponization

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

Timeline

Disclosed

Apr 21, 2021

Last updated

Oct 24, 2026

Identifiers

CVE-2021-21645

GHSA-2959-fj73-hm8p

References

Advisoryopenwall.com Advisoryjenkins.io · 2021 04 21 Advisorynvd.nist.gov · CVE 2021 21645 Webgithub.com · b7f3c5150ad557e86414122c69be20075aee27fa Packagegithub.com · config file provider plugin

Related vulnerabilities

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

CVE-2023-40339CVE-2021-21643CVE-2021-21644CVE-2021-21642CVE-2018-1000414CVE-2018-1000413CVE-2017-1000104CVE-2019-1003014

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026

CVE-2021-21645 — config-file-provider

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-21645 in your dependencies?