CVE-2026-17039

LOWPre-NVD 3.13.1
EchelonGraph scoreHIGH 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 — 4 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(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 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

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.

  1. 2026-07-30 01:30 UTCEPSS rescore
  2. 2026-07-29 03:55 UTCEG score recompute
  3. 2026-07-29 03:55 UTCGHSA enrichment
  4. 2026-07-27 14:13 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:54 UTCEPSS rescore
  7. 2026-07-26 03:00 UTCEG score recompute
  8. 2026-07-26 02:59 UTCGHSA enrichment
  9. 2026-07-25 14:17 UTCEPSS rescore
  10. 2026-07-25 14:17 UTCEPSS rescore
  11. 2026-07-24 15:42 UTCEG score recompute
  12. 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.5% 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

Explore the affected products and dependency analysis for 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.