CVE-2022-20621: Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file o

Q: How do I fix CVE-2022-20621?

metrics: upgrade to newer than 4.0.2.8. Exact commands for each OS are on this page.

Q: Is CVE-2022-20621 being exploited?

CVE-2022-20621 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-20621 affect?

CVE-2022-20621 affects metrics. Severity is medium (CVSS 5.5). Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

Q: How urgent is CVE-2022-20621?

Priority 25/100. No elevated risk signals yet.

Routine

MEDIUM 5.5UPGRADE

CVE-2022-20621 is a medium-severity flaw (CVSS 5.5) affecting metrics. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	5.5 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 75%)
CISA exploited list	No
Weakness	CWE-522
Published	2022-01-12
Last modified	2026-06-17

Publisher (CNA): Jenkins Project · Vendor: jenkins

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-01-12 20:15 UTCPublished CVE record published
2026-06-17 04:24 UTCUpdated Record last modified

jenkins metrics UPGRADE

Affected: <= 4.0.2.8

Fixed in: newer than 4.0.2.8

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy metrics || rpm -q metrics || metrics --version

2. UPGRADE to newer than 4.0.2.8 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade metrics

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade metrics

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-20621?

metrics: upgrade to newer than 4.0.2.8. Exact commands for each OS are on this page.

Is CVE-2022-20621 being exploited?

CVE-2022-20621 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-20621 affect?

CVE-2022-20621 affects metrics. Severity is medium (CVSS 5.5). Jenkins Metrics Plugin 4.0.2.8 and earlier stores an access key unencrypted in its global configuration file on the Jenkins controller where it can be viewed by users with access to the Jenkins controller file system.

How urgent is CVE-2022-20621?

Priority 25/100. No elevated risk signals yet.

Software pages

Jenkins vulnerabilities

Related CVEs

CVE-2022-4860 MEDIUM 5.5 UPGRADE A vulnerability was found in KBase Metrics

References

← Back to latest CVEs