A flaw was found in pki-core. The certificate authority (CA) renewal request path does not perform the realm-based authorization check that the enrollment path performs, allowing an authenticated user entitled to one realm to cause a certificate belonging to a different realm to be renewed without that realm's authorization.
CVE-2026-17039
Score 3.1 from GitHub Security Advisory (severity: LOW) published 2026-07-24. a secondary CVSS source baseline 3.1; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.1
- EG Score
- 3.1(high)
- EG Risk
- 14(Track)EG Risk 14/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity31% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 11%
- KEV
- Not listed
Published
July 24, 2026
Last Modified
July 25, 2026
References (8)
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2021-20179
- secalert@redhathttps://access.redhat.com/security/cve/CVE-2026-17039
- secalert@redhathttps://bugzilla.redhat.com/show_bug.cgi?id=2506720
- secalert@redhathttps://github.com/dogtagpki/pki/blob/master/base/ca/database/ds/acl.ldif
- secalert@redhathttps://github.com/dogtagpki/pki/blob/master/base/ca/src/main/java/com/netscape/cms/servlet/cert/EnrollmentProcessor.java
- secalert@redhathttps://github.com/dogtagpki/pki/blob/master/base/ca/src/main/java/com/netscape/cms/servlet/cert/RenewalProcessor.java
- secalert@redhathttps://github.com/dogtagpki/pki/blob/master/base/ca/src/main/java/org/dogtagpki/server/ca/rest/v2/CertServlet.java
- secalert@redhathttps://github.com/dogtagpki/pki/commit/e2de26769761af04b9c56071bd1a1926903c49b6
Vendor Advisories for CVE-2026-17039(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-30 01:30 UTCEPSS rescore
- 2026-07-29 03:55 UTCEG score recompute
- 2026-07-29 03:55 UTCGHSA enrichment
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 14:54 UTCEPSS rescore
- 2026-07-26 03:00 UTCEG score recompute
- 2026-07-26 02:59 UTCGHSA enrichment
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-25 14:17 UTCEPSS rescore
- 2026-07-24 15:42 UTCEG score recompute
- 2026-07-24 15:41 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-17039?
When was CVE-2026-17039 disclosed?
Is CVE-2026-17039 actively exploited?
What is the CVSS score of CVE-2026-17039?
How do I remediate CVE-2026-17039?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-17039
Is Your Infrastructure Affected by CVE-2026-17039?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.