CVE-2026-65922

HIGHNVD 5.47.1
EchelonGraph scoreMEDIUM confidence

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-27. NVD baseline CVSS 5.4; sources differ by 1.7.

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

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

An authorization weakness in JFrog Artifactory internal metadata handling could allow a user with limited repository access to write to restricted internal metadata areas under specific conditions. Successful abuse is limited to integrity and availability impact at a low level; confidentiality is not affected.

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

Published

July 27, 2026

Last Modified

July 30, 2026

Advisory Details (2)

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

Vendor Advisories for CVE-2026-65922(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 29× in last 7d / 34× 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-03 22:11 UTCEG score recompute
  2. 2026-08-03 22:11 UTCGHSA enrichment
  3. 2026-08-03 10:36 UTCEPSS rescore
  4. 2026-08-03 09:16 UTCGHSA enrichment
  5. 2026-08-02 20:19 UTCGHSA enrichment
  6. 2026-08-02 07:25 UTCEG score recompute
  7. 2026-08-02 07:25 UTCGHSA enrichment
  8. 2026-08-02 02:27 UTCEPSS rescore
  9. 2026-08-01 18:30 UTCGHSA enrichment
  10. 2026-08-01 05:35 UTCEG score recompute
  11. 2026-08-01 05:35 UTCGHSA enrichment
  12. 2026-08-01 04:16 UTCEPSS rescore
  13. 2026-07-31 16:39 UTCGHSA enrichment
  14. 2026-07-31 03:43 UTCEG score recompute
  15. 2026-07-31 03:43 UTCGHSA enrichment
  16. 2026-07-30 16:28 UTCEPSS rescore
  17. 2026-07-30 14:49 UTCEG score recompute
  18. 2026-07-30 14:49 UTCGHSA enrichment
  19. 2026-07-30 14:48 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  20. 2026-07-30 14:40 UTCEG score recompute
  21. 2026-07-30 14:40 UTCGHSA enrichment
  22. 2026-07-30 01:39 UTCEG score recompute
  23. 2026-07-30 01:38 UTCGHSA enrichment
  24. 2026-07-30 01:30 UTCEPSS rescore
  25. 2026-07-29 12:29 UTCGHSA enrichment
Show 9 more
  1. 2026-07-28 23:34 UTCEG score recompute
  2. 2026-07-28 23:33 UTCGHSA enrichment
  3. 2026-07-28 15:37 UTCEPSS rescore
  4. 2026-07-28 10:37 UTCGHSA enrichment
  5. 2026-07-27 21:36 UTCEG score recompute
  6. 2026-07-27 21:36 UTCGHSA enrichment
  7. 2026-07-27 20:19 UTCEG score recompute
  8. 2026-07-27 19:55 UTCEG score recompute
  9. 2026-07-27 19:54 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65922?
CVE-2026-65922 is a high vulnerability published on July 27, 2026. An authorization weakness in JFrog Artifactory internal metadata handling could allow a user with limited repository access to write to restricted internal metadata areas under specific conditions. Successful abuse is limited to integrity and availability impact at a low level; confidentiality is…
When was CVE-2026-65922 disclosed?
CVE-2026-65922 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-65922 actively exploited?
CVE-2026-65922 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 92.6% of all scored CVEs.
What is the CVSS score of CVE-2026-65922?
CVE-2026-65922 has a CVSS v3 base score of 5.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.1.
How do I remediate CVE-2026-65922?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65922, 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-65922

Explore →

Is Your Infrastructure Affected by CVE-2026-65922?

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