CVE-2026-13320

HIGHNVD 5.47.3
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-07-08. NVD baseline CVSS 5.4; sources differ by 1.9.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.3EG
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.

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user's browser session due to improper sanitization of user-supplied input.

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

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (1)

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

GitLab Patch Release: 19.1.2, 19.0.4, 18.11.7 | GitLab Docs

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/

Vendor Advisories for CVE-2026-13320(2)

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 13× in last 7d / 42× 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 00:37 UTCEG score recompute
  2. 2026-07-27 00:37 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 12:25 UTCEG score recompute
  6. 2026-07-26 12:25 UTCGHSA enrichment
  7. 2026-07-25 14:17 UTCEPSS rescore
  8. 2026-07-24 14:17 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:05 UTCEG score recompute
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-21 15:24 UTCEPSS rescore
  13. 2026-07-20 17:08 UTCEPSS rescore
  14. 2026-07-19 02:28 UTCEPSS rescore
  15. 2026-07-18 10:04 UTCEPSS rescore
  16. 2026-07-17 00:28 UTCGHSA enrichment
  17. 2026-07-16 17:02 UTCEPSS rescore
  18. 2026-07-16 12:13 UTCGHSA enrichment
  19. 2026-07-16 00:01 UTCGHSA enrichment
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 11:49 UTCGHSA enrichment
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 23:37 UTCGHSA enrichment
  24. 2026-07-14 11:25 UTCGHSA enrichment
  25. 2026-07-13 23:13 UTCGHSA enrichment
Show 17 more
  1. 2026-07-13 22:30 UTCEPSS rescore
  2. 2026-07-13 11:01 UTCGHSA enrichment
  3. 2026-07-13 06:12 UTCEPSS rescore
  4. 2026-07-12 22:49 UTCGHSA enrichment
  5. 2026-07-12 10:37 UTCGHSA enrichment
  6. 2026-07-12 05:46 UTCEPSS rescore
  7. 2026-07-11 22:23 UTCGHSA enrichment
  8. 2026-07-11 10:11 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-10 22:00 UTCGHSA enrichment
  11. 2026-07-10 09:48 UTCGHSA enrichment
  12. 2026-07-09 21:46 UTCNVD updateCVSS v3 → 5.4 · severity → MEDIUM
  13. 2026-07-09 21:36 UTCGHSA enrichment
  14. 2026-07-09 19:10 UTCEPSS rescore
  15. 2026-07-09 09:25 UTCGHSA enrichment
  16. 2026-07-08 21:13 UTCEG score recompute
  17. 2026-07-08 21:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13320?
CVE-2026-13320 is a high vulnerability published on July 8, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.7 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user to execute arbitrary scripts in another user's browser session due to improper…
When was CVE-2026-13320 disclosed?
CVE-2026-13320 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13320 actively exploited?
CVE-2026-13320 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 74.3% of all scored CVEs.
What is the CVSS score of CVE-2026-13320?
CVE-2026-13320 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.3.
How do I remediate CVE-2026-13320?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13320, 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-13320

Explore →

Is Your Infrastructure Affected by CVE-2026-13320?

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