CVE-2026-65616

HIGHPre-NVD 8.88.8
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
Trending — 3 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: CVSS: 8.8Exploit: None knownExposed: 0

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

Incorrect authorization validation in refresh token signature allows non-admin users to obtain a signed JFrog administrator token.

CVSS v3
8.8
EG Score
8.8(high)
EG Risk
44(Track)
EG Risk 44/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%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
EPSS %ILE
KEV
Not listed

Published

July 27, 2026

Last Modified

July 27, 2026

Advisory Details (2)

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

Vendor Advisories for CVE-2026-65616(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 5× in last 7d / 5× 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-27 21:37 UTCEG score recompute
  2. 2026-07-27 21:37 UTCGHSA enrichment
  3. 2026-07-27 20:20 UTCEG score recompute
  4. 2026-07-27 19:55 UTCEG score recompute
  5. 2026-07-27 19:54 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-65616?
CVE-2026-65616 is a high vulnerability published on July 27, 2026. Incorrect authorization validation in refresh token signature allows non-admin users to obtain a signed JFrog administrator token.
When was CVE-2026-65616 disclosed?
CVE-2026-65616 was first published in the National Vulnerability Database on July 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-65616?
CVE-2026-65616 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-65616?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65616, 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-65616

Explore →

Is Your Infrastructure Affected by CVE-2026-65616?

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