CVE-2026-42016

HIGHNVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 89% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 5 sources updated this week
8.8EG
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.8Exploit: None knownExposed: 0

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

JFrog Artifactory (Self Hosted) versions before 7.133.11 are vulnerable to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.

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

Published

July 27, 2026

Last Modified

July 30, 2026

Advisory Details (2)

Auto-updated Jul 27, 2026
No patch confirmed yet.
generic

Artifactory Self-Managed Releases

https://docs.jfrog.com/releases/docs/artifactory-self-managed-releases
generic

JFrog Security Advisories

https://docs.jfrog.com/releases/docs/jfrog-security-advisories

Vendor Advisories for CVE-2026-42016(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 18× in last 7d / 18× 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 16:28 UTCEPSS rescore
  2. 2026-07-30 14:49 UTCEG score recompute▲ 0.70
  3. 2026-07-30 14:49 UTCGHSA enrichment
  4. 2026-07-30 14:48 UTCNVD updateCVSS v3 → 8.8
  5. 2026-07-30 02:10 UTCEG score recompute
  6. 2026-07-30 02:10 UTCGHSA enrichment
  7. 2026-07-30 01:30 UTCEPSS rescore
  8. 2026-07-29 13:04 UTCGHSA enrichment
  9. 2026-07-28 23:58 UTCEG score recompute
  10. 2026-07-28 23:57 UTCGHSA enrichment
  11. 2026-07-28 15:36 UTCEPSS rescore
  12. 2026-07-28 10:47 UTCGHSA enrichment
  13. 2026-07-27 21:38 UTCEG score recompute
  14. 2026-07-27 21:37 UTCGHSA enrichment
  15. 2026-07-27 20:41 UTCEG score recompute
  16. 2026-07-27 20:20 UTCEG score recompute
  17. 2026-07-27 19:55 UTCEG score recompute
  18. 2026-07-27 19:54 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-42016?
CVE-2026-42016 is a high vulnerability published on July 27, 2026. JFrog Artifactory (Self Hosted) versions before 7.133.11 are vulnerable to a privilege escalation attack due to a validation check of the token signature/issuer and not the token’s scope.
When was CVE-2026-42016 disclosed?
CVE-2026-42016 was first published in the National Vulnerability Database on July 27, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-42016 actively exploited?
CVE-2026-42016 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-42016?
CVE-2026-42016 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-42016?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-42016, 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-42016

Explore →

Is Your Infrastructure Affected by CVE-2026-42016?

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

Start Free Scan →Browse All CVEs