CVE-2026-17039

LOWPre-NVD 3.13.1—
EchelonGraph scoreMEDIUM confidence

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.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
3.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 3.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
3.1
EG Score
3.1(medium)
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 computed
Severity31% × 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)

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.

Affected Packages

(1 across 1 ecosystem)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
dogtag-pki10.10.2-3 ... 11.2.1-2 (11 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 40× 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.

  1. 2026-09-13 23:18 UTCEG score recompute
  2. 2026-09-13 23:18 UTCGHSA enrichment
  3. 2026-09-13 16:46 UTCEPSS rescore
  4. 2026-09-12 15:00 UTCEPSS rescore
  5. 2026-09-11 14:52 UTCEPSS rescore
  6. 2026-09-11 09:36 UTCEPSS rescore
  7. 2026-09-10 22:23 UTCEG score recompute
  8. 2026-09-10 22:23 UTCGHSA enrichment
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 21:26 UTCEG score recompute
  12. 2026-09-07 21:26 UTCGHSA enrichment
  13. 2026-09-07 16:01 UTCEPSS rescore
  14. 2026-09-06 13:47 UTCEPSS rescore
  15. 2026-09-04 12:53 UTCEG score recompute
  16. 2026-09-04 12:53 UTCGHSA enrichment
  17. 2026-09-04 05:06 UTCEPSS rescore
  18. 2026-09-02 14:11 UTCEPSS rescore
  19. 2026-09-01 13:53 UTCEPSS rescore
  20. 2026-09-01 04:39 UTCEPSS rescore
  21. 2026-08-30 19:17 UTCEPSS rescore
  22. 2026-08-30 01:22 UTCEPSS rescore
  23. 2026-08-30 00:19 UTCEG score recompute
  24. 2026-08-30 00:19 UTCGHSA enrichment
  25. 2026-08-28 21:41 UTCEPSS rescore
Show 55 more
  1. 2026-08-27 14:25 UTCEPSS rescore
  2. 2026-08-26 14:46 UTCEPSS rescore
  3. 2026-08-25 13:48 UTCEPSS rescore
  4. 2026-08-25 12:08 UTCEG score recompute
  5. 2026-08-25 12:08 UTCGHSA enrichment
  6. 2026-08-23 00:19 UTCEPSS rescore
  7. 2026-08-22 11:13 UTCEG score recompute
  8. 2026-08-22 11:13 UTCGHSA enrichment
  9. 2026-08-21 23:49 UTCEPSS rescore
  10. 2026-08-20 22:55 UTCEPSS rescore
  11. 2026-08-19 17:03 UTCEPSS rescore
  12. 2026-08-19 10:18 UTCEG score recompute
  13. 2026-08-19 10:18 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 14:56 UTCEPSS rescore
  17. 2026-08-16 09:23 UTCEG score recompute
  18. 2026-08-16 09:23 UTCGHSA enrichment
  19. 2026-08-16 02:14 UTCEPSS rescore
  20. 2026-08-15 01:30 UTCEPSS rescore
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-13 08:29 UTCEG score recompute
  23. 2026-08-13 08:28 UTCGHSA enrichment
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 13:42 UTCEPSS rescore
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 07:34 UTCEG score recompute
  28. 2026-08-10 07:34 UTCGHSA enrichment
  29. 2026-08-09 13:46 UTCEPSS rescore
  30. 2026-08-08 16:37 UTCEPSS rescore
  31. 2026-08-07 06:39 UTCEG score recompute
  32. 2026-08-07 06:39 UTCGHSA enrichment
  33. 2026-08-06 13:46 UTCEPSS rescore
  34. 2026-08-05 19:17 UTCEPSS rescore
  35. 2026-08-04 15:10 UTCEPSS rescore
  36. 2026-08-04 10:38 UTCEPSS rescore
  37. 2026-08-04 05:45 UTCEG score recompute
  38. 2026-08-04 05:45 UTCGHSA enrichment
  39. 2026-08-03 10:35 UTCEPSS rescore
  40. 2026-08-02 02:26 UTCEPSS rescore
  41. 2026-08-01 04:50 UTCEG score recompute
  42. 2026-08-01 04:50 UTCGHSA enrichment
  43. 2026-08-01 04:15 UTCEPSS rescore
  44. 2026-07-30 01:30 UTCEPSS rescore
  45. 2026-07-29 03:55 UTCEG score recompute
  46. 2026-07-29 03:55 UTCGHSA enrichment
  47. 2026-07-27 14:13 UTCEPSS rescore
  48. 2026-07-26 14:54 UTCEPSS rescore
  49. 2026-07-26 14:54 UTCEPSS rescore
  50. 2026-07-26 03:00 UTCEG score recompute
  51. 2026-07-26 02:59 UTCGHSA enrichment
  52. 2026-07-25 14:17 UTCEPSS rescore
  53. 2026-07-25 14:17 UTCEPSS rescore
  54. 2026-07-24 15:42 UTCEG score recompute
  55. 2026-07-24 15:41 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-17039?
CVE-2026-17039 is a low vulnerability published on July 24, 2026. 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…
When was CVE-2026-17039 disclosed?
CVE-2026-17039 was first published in the National Vulnerability Database on July 24, 2026, with the most recent update on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17039 actively exploited?
CVE-2026-17039 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 88.6% of all scored CVEs.
What is the CVSS score of CVE-2026-17039?
CVE-2026-17039 has a CVSS v3 base score of 3.1 (NVD).
How do I remediate CVE-2026-17039?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17039, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-17039

Explore →

Is Your Infrastructure Affected by CVE-2026-17039?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs