CVE-2026-17603

HIGHPre-NVD 8.78.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.7Exploit: None knownExposed: 0

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

Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on every new connection. On the default H2 database backend, this could be leveraged to achieve remote code execution as the Nexus process user.

CVSS v3
8.7
EG Score
8.7(medium)
EG Risk
39(Track)
EG Risk 39/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
Severity87% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
32%
KEV
Not listed

Published

August 7, 2026

Last Modified

August 7, 2026

Advisory Details (1)

Auto-updated Aug 7, 2026
No patch confirmed yet.
generic

Sonatype Nexus Repository 3.95.0 Release Notes

https://help.sonatype.com/en/sonatype-nexus-repository-3-95-0-release-notes.html

Vendor Advisories for CVE-2026-17603(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 28× in last 7d / 58× 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-08-21 06:31 UTCEG score recompute
  2. 2026-08-21 06:31 UTCGHSA enrichment
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-20 18:36 UTCGHSA enrichment
  5. 2026-08-20 06:42 UTCGHSA enrichment
  6. 2026-08-19 18:47 UTCEG score recompute
  7. 2026-08-19 18:47 UTCGHSA enrichment
  8. 2026-08-19 17:03 UTCEPSS rescore
  9. 2026-08-19 05:45 UTCGHSA enrichment
  10. 2026-08-18 17:51 UTCEG score recompute
  11. 2026-08-18 17:51 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 04:41 UTCGHSA enrichment
  14. 2026-08-17 16:47 UTCEG score recompute
  15. 2026-08-17 16:47 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 04:53 UTCGHSA enrichment
  18. 2026-08-16 16:59 UTCEG score recompute
  19. 2026-08-16 16:59 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 05:05 UTCEG score recompute
  22. 2026-08-16 05:05 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 17:11 UTCGHSA enrichment
  25. 2026-08-15 05:17 UTCEG score recompute
Show 33 more
  1. 2026-08-15 05:17 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 17:22 UTCGHSA enrichment
  4. 2026-08-14 05:20 UTCEG score recompute
  5. 2026-08-14 05:20 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 17:25 UTCGHSA enrichment
  8. 2026-08-13 05:30 UTCGHSA enrichment
  9. 2026-08-12 17:36 UTCEG score recompute
  10. 2026-08-12 17:36 UTCGHSA enrichment
  11. 2026-08-12 13:50 UTCEPSS rescore
  12. 2026-08-12 05:40 UTCGHSA enrichment
  13. 2026-08-11 17:46 UTCEG score recompute
  14. 2026-08-11 17:46 UTCGHSA enrichment
  15. 2026-08-11 13:42 UTCEPSS rescore
  16. 2026-08-11 05:50 UTCEG score recompute
  17. 2026-08-11 05:50 UTCGHSA enrichment
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-10 17:56 UTCGHSA enrichment
  20. 2026-08-10 05:57 UTCGHSA enrichment
  21. 2026-08-09 18:03 UTCEG score recompute
  22. 2026-08-09 18:03 UTCGHSA enrichment
  23. 2026-08-09 13:46 UTCEPSS rescore
  24. 2026-08-09 06:09 UTCGHSA enrichment
  25. 2026-08-08 18:15 UTCEG score recompute
  26. 2026-08-08 18:15 UTCGHSA enrichment
  27. 2026-08-08 16:37 UTCEPSS rescore
  28. 2026-08-08 06:20 UTCGHSA enrichment
  29. 2026-08-07 18:26 UTCEG score recompute
  30. 2026-08-07 18:07 UTCEG score recompute
  31. 2026-08-07 17:25 UTCEG score recompute
  32. 2026-08-07 16:27 UTCEG score recompute
  33. 2026-08-07 16:27 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17603?
CVE-2026-17603 is a high vulnerability published on August 7, 2026. Nexus Repository 3 did not sufficiently restrict which HikariCP connection-pool properties could be set through the DataStore configuration API. A user holding the nx-datastores-update permission could set the connectionInitSql property to execute arbitrary SQL against the configured database on…
When was CVE-2026-17603 disclosed?
CVE-2026-17603 was first published in the National Vulnerability Database on August 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17603 actively exploited?
CVE-2026-17603 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 67.9% of all scored CVEs.
What is the CVSS score of CVE-2026-17603?
CVE-2026-17603 has a CVSS v3 base score of 8.7 (NVD).
How do I remediate CVE-2026-17603?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17603, 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-17603

Explore →

Is Your Infrastructure Affected by CVE-2026-17603?

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

Start Free Scan →Browse All CVEs