CVE-2026-87719

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-12. a secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: 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 EE affecting all versions from 18.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials using a specially crafted GraphQL subscription argument to bypass serialization and perform server object lookup.

CVSS v3
9.9
EG Score
9.9(high)
EG Risk
45(Track)
EG Risk 45/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
Severity99% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

September 12, 2026

Last Modified

September 16, 2026

Advisory Details (1)

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

Work items · GitLab.org / GitLab · GitLab

https://gitlab.com/gitlab-org/gitlab/-/work_items/628160

Vendor Advisories for CVE-2026-87719(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 57× in last 7d / 63× 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-09-19 10:06 UTCGHSA enrichment
  2. 2026-09-19 05:50 UTCGHSA enrichment
  3. 2026-09-19 01:33 UTCGHSA enrichment
  4. 2026-09-18 21:17 UTCEG score recompute
  5. 2026-09-18 21:17 UTCGHSA enrichment
  6. 2026-09-18 19:28 UTCEPSS rescore
  7. 2026-09-18 16:57 UTCGHSA enrichment
  8. 2026-09-18 12:41 UTCGHSA enrichment
  9. 2026-09-18 08:25 UTCGHSA enrichment
  10. 2026-09-18 04:09 UTCGHSA enrichment
  11. 2026-09-17 23:53 UTCGHSA enrichment
  12. 2026-09-17 19:37 UTCEG score recompute
  13. 2026-09-17 19:37 UTCGHSA enrichment
  14. 2026-09-17 19:32 UTCEPSS rescore
  15. 2026-09-17 12:58 UTCGHSA enrichment
  16. 2026-09-17 08:27 UTCGHSA enrichment
  17. 2026-09-17 04:10 UTCGHSA enrichment
  18. 2026-09-16 23:53 UTCGHSA enrichment
  19. 2026-09-16 19:37 UTCGHSA enrichment
  20. 2026-09-16 18:59 UTCGHSA enrichment
  21. 2026-09-16 14:43 UTCEG score recompute
  22. 2026-09-16 14:43 UTCGHSA enrichment
  23. 2026-09-16 14:09 UTCEPSS rescore
  24. 2026-09-16 10:26 UTCGHSA enrichment
  25. 2026-09-16 06:11 UTCEG score recompute
Show 38 more
  1. 2026-09-16 06:11 UTCGHSA enrichment
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-16 01:54 UTCGHSA enrichment
  4. 2026-09-15 21:37 UTCGHSA enrichment
  5. 2026-09-15 17:17 UTCGHSA enrichment
  6. 2026-09-15 13:00 UTCGHSA enrichment
  7. 2026-09-15 08:43 UTCGHSA enrichment
  8. 2026-09-15 04:25 UTCEG score recompute
  9. 2026-09-15 04:25 UTCGHSA enrichment
  10. 2026-09-15 04:04 UTCEG score recompute
  11. 2026-09-15 04:04 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 02:42 UTCGHSA enrichment
  14. 2026-09-14 22:26 UTCGHSA enrichment
  15. 2026-09-14 18:09 UTCGHSA enrichment
  16. 2026-09-14 13:29 UTCEG score recompute
  17. 2026-09-14 13:29 UTCGHSA enrichment
  18. 2026-09-14 13:10 UTCEG score recompute
  19. 2026-09-14 13:10 UTCGHSA enrichment
  20. 2026-09-14 10:52 UTCGHSA enrichment
  21. 2026-09-14 06:36 UTCGHSA enrichment
  22. 2026-09-14 02:20 UTCGHSA enrichment
  23. 2026-09-13 22:04 UTCGHSA enrichment
  24. 2026-09-13 17:48 UTCEG score recompute
  25. 2026-09-13 17:48 UTCGHSA enrichment
  26. 2026-09-13 13:32 UTCGHSA enrichment
  27. 2026-09-13 09:15 UTCGHSA enrichment
  28. 2026-09-13 04:59 UTCGHSA enrichment
  29. 2026-09-13 00:43 UTCGHSA enrichment
  30. 2026-09-12 20:27 UTCGHSA enrichment
  31. 2026-09-12 16:11 UTCEG score recompute
  32. 2026-09-12 16:11 UTCGHSA enrichment
  33. 2026-09-12 11:55 UTCGHSA enrichment
  34. 2026-09-12 07:38 UTCEG score recompute
  35. 2026-09-12 07:38 UTCGHSA enrichment
  36. 2026-09-12 03:20 UTCEG score recompute
  37. 2026-09-12 02:54 UTCEG score recompute
  38. 2026-09-12 02:53 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-87719?
CVE-2026-87719 is a critical vulnerability published on September 12, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 18.3 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that under certain conditions could allow an authenticated user with Duo Chat access to obtain Advanced Search instance configurations and sensitive credentials…
When was CVE-2026-87719 disclosed?
CVE-2026-87719 was first published in the National Vulnerability Database on September 12, 2026, with the most recent update on September 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-87719 actively exploited?
CVE-2026-87719 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.1% of all scored CVEs.
What is the CVSS score of CVE-2026-87719?
CVE-2026-87719 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-87719?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-87719, 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-87719

Explore →

Is Your Infrastructure Affected by CVE-2026-87719?

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