CVE-2026-84739

HIGHPre-NVD 8.78.7—
EchelonGraph scoreHIGH confidence

Score 8.7 from GitHub Security Advisory (severity: HIGH) published 2026-09-29. A secondary CVSS source baseline 8.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.7EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.7Exploit: None knownExposed services: Not assessed

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

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.11 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary JavaScript in the context of another user's browser session due to improper sanitization of path components in the merge request diff viewer.

CVSS v3
8.7
EG Score
8.7HIGHhigh confidence
EG Risk
39
EG Risk 39/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
27th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 29, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Sep 29, 2026
No patch confirmed yet.
generic

GitLab Critical Patch Release: 19.4.1, 19.3.3, 19.2.7 | GitLab Docs

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

Vendor Advisories for CVE-2026-84739(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 24× in last 7d / 24× 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-10-04 07:16 UTCGHSA enrichment
  2. 2026-10-03 18:09 UTCEG score recompute
  3. 2026-10-03 18:08 UTCGHSA enrichment
  4. 2026-10-03 14:26 UTCEPSS rescore
  5. 2026-10-03 05:00 UTCEG score recompute
  6. 2026-10-03 05:00 UTCGHSA enrichment
  7. 2026-10-02 17:57 UTCEPSS rescore
  8. 2026-10-02 15:52 UTCGHSA enrichment
  9. 2026-10-02 02:45 UTCEG score recompute
  10. 2026-10-02 02:45 UTCGHSA enrichment
  11. 2026-10-01 19:50 UTCEPSS rescore
  12. 2026-10-01 13:34 UTCGHSA enrichment
  13. 2026-10-01 00:27 UTCEG score recompute
  14. 2026-10-01 00:27 UTCGHSA enrichment
  15. 2026-09-30 15:04 UTCEPSS rescore
  16. 2026-09-30 11:17 UTCGHSA enrichment
  17. 2026-09-29 22:10 UTCGHSA enrichment
  18. 2026-09-29 15:24 UTCEG score recompute
  19. 2026-09-29 15:24 UTCGHSA enrichment
  20. 2026-09-29 15:09 UTCEG score recompute
  21. 2026-09-29 15:09 UTCGHSA enrichment
  22. 2026-09-29 10:33 UTCEG score recompute
  23. 2026-09-29 09:44 UTCEG score recompute
  24. 2026-09-29 09:43 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-84739?
CVE-2026-84739 is a high vulnerability published on September 29, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 13.11 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to execute arbitrary JavaScript in the context of another user's browser session due to…
When was CVE-2026-84739 disclosed?
CVE-2026-84739 was first published on September 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-84739 actively exploited?
CVE-2026-84739 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (27th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-84739?
CVE-2026-84739 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-84739?
No fix for CVE-2026-84739 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-84739 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-84739

Explore →

Is Your Infrastructure Affected by CVE-2026-84739?

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

Book a Demo →Browse All CVEs