No exploitation reportedFix available

CVE-2021-20179

Q: Is CVE-2021-20179 actively exploited?

Active exploitation of CVE-2021-20179 has not been confirmed. Its EPSS score was 1.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

Q: What is the CVSS score for CVE-2021-20179?

CVE-2021-20179 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.

No exploitation reported by the sources we read.

Published2021-03-15
Fixed in10.11.0 · 10.10.0 · 10.9.0 · 10.8.0 · 10.5.0
WeaknessCWE-863

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A flaw was found in pki-core. An attacker who has successfully compromised a key could use this flaw to renew the corresponding certificate over and over again, as long as it is not explicitly revoked. The highest threat from this vulnerability is to data confidentiality and integrity.

Timeline

dates in UTC

2021-03-1513:15CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC

Indicators tagged with this CVE, per day0 indicators over 7 days

Block these indicators

Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2021-20179?format=txt
CSV export: https://api.ismalicious.com/edl/cve/CVE-2021-20179?format=csv
TAXII collection of exploited CVEs
The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD

Dogtagpki

Branch	Affected	Fixed in	Source
10.x	≥ 10.10.1, < 10.11.0	10.11.0	NVD
10.x	≥ 10.9.1, < 10.10.0	10.10.0	NVD
10.x	≥ 10.8.1, < 10.9.0	10.9.0	NVD
10.x	≥ 10.5.1, < 10.8.0	10.8.0	NVD
10.5	< 10.5.0	10.5.0	NVD

Fedoraproject fedora

Branch	Affected	Fixed in	Source
32.x	= 32	no fix published	NVD
33.x	= 33	no fix published	NVD
34.x	= 34	no fix published	NVD

Redhat enterprise linux

Branch	Affected	Fixed in	Source
7.0	= 7.0	no fix published	NVD
8.0	= 8.0	no fix published	NVD

1 more product in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Update Dogtagpki to 10.11.0 · 10.10.0 · 10.9.0 · 10.8.0 · 10.5.0

Advisories and patches

Detection

Nuclei template: none so far
Exploit-DB: no entry
Proof-of-concept repositories: none listed

Sources

NVDCVSS 3.18.1read 2026-10-23
NVDCVSS 2.05.5read 2026-10-23
CNAweakness (CWE)CWE-863read 2026-10-23
NVDweakness (CWE)CWE-863read 2026-10-23
FIRST EPSSEPSS score1.2 %2026-10-22

Technical details

CVSS v3 Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Published: 2021-03-15
Last Modified: 2026-06-17
NVD status: Modified

Frequently asked questions

What is CVE-2021-20179?

Is CVE-2021-20179 actively exploited?

Active exploitation of CVE-2021-20179 has not been confirmed. Its EPSS score was 1.2% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2021-20179?

CVE-2021-20179 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this product CISA KEV additions, October 2026 Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database