CVE-2026-44895

CRITICALNVD 9.29.2—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.2 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.2Exploit: NoneExposed: 0

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

GitLab MCP Server lets an AI agent talk directly to GitLab. Prior to 0.6.0, the HTTP transport in src/transport.ts ships with no authentication layer at all and a wildcard Access-Control-Allow-Origin: * on every response. The structural defect is that the SSE server stands up a stateful, mutation-capable RPC endpoint that is backed by the operator's GITLAB_PERSONAL_ACCESS_TOKEN without any inbound credential check, then advertises itself to every cross-origin browser context via the wildcard CORS header. The httpServer.listen(port) call at line 97 also passes no host argument, so the bind defaults to 0.0.0.0 and exposes the auth-less surface on every interface. This vulnerability is fixed in 0.6.0.

CVSS v3
9.2
EG Score
9.2(medium)
EPSS
31.3%
KEV
Not listed

Published

May 26, 2026

Last Modified

June 1, 2026

Advisory Details (1)

Auto-updated May 28, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

SSE transport has no authentication and wildcard CORS, exposing all 86 GitLab tools · Advisory · yoda-digital/mcp-gitlab-server · GitHub

https://github.com/yoda-digital/mcp-gitlab-server/security/advisories/GHSA-8jr5-6gvj-rfpf

Vendor Advisories for CVE-2026-44895(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@yoda.digital/gitlab-mcp-server—0.6.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 89× 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.

Showing the most recent 100 of 180 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:16 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 02:30 UTCEPSS rescore
  8. 2026-07-04 06:31 UTCEPSS rescore
  9. 2026-07-01 17:02 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 12:05 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 19:52 UTCEG score recompute
  14. 2026-06-29 14:46 UTCEG score recompute
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 02:43 UTCEG score recompute
  18. 2026-06-28 22:39 UTCEG score recompute
  19. 2026-06-28 16:56 UTCEG score recompute
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 11:41 UTCEG score recompute
  22. 2026-06-28 07:35 UTCEG score recompute
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-28 03:30 UTCEG score recompute
Show 75 more
  1. 2026-06-27 23:26 UTCEG score recompute
  2. 2026-06-27 19:21 UTCEG score recompute
  3. 2026-06-27 15:17 UTCEG score recompute
  4. 2026-06-27 11:07 UTCEG score recompute
  5. 2026-06-27 07:00 UTCEG score recompute
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-26 21:34 UTCEG score recompute
  8. 2026-06-26 17:30 UTCEG score recompute
  9. 2026-06-26 03:09 UTCEG score recompute
  10. 2026-06-25 23:05 UTCEG score recompute
  11. 2026-06-25 18:04 UTCEG score recompute
  12. 2026-06-25 13:58 UTCEG score recompute
  13. 2026-06-25 13:49 UTCEPSS rescore
  14. 2026-06-25 13:49 UTCEPSS rescore
  15. 2026-06-25 09:53 UTCEG score recompute
  16. 2026-06-24 14:05 UTCEPSS rescore
  17. 2026-06-23 21:33 UTCEPSS rescore
  18. 2026-06-22 14:25 UTCEPSS rescore
  19. 2026-06-22 14:25 UTCEPSS rescore
  20. 2026-06-21 14:56 UTCEPSS rescore
  21. 2026-06-21 14:56 UTCEPSS rescore
  22. 2026-06-21 01:59 UTCEPSS rescore
  23. 2026-06-19 19:25 UTCEPSS rescore
  24. 2026-06-18 17:52 UTCEPSS rescore
  25. 2026-06-18 17:52 UTCEPSS rescore
  26. 2026-06-18 03:44 UTCEG score recompute
  27. 2026-06-17 23:38 UTCEG score recompute
  28. 2026-06-17 19:11 UTCEG score recompute
  29. 2026-06-17 17:53 UTCEPSS rescore
  30. 2026-06-17 13:51 UTCEG score recompute
  31. 2026-06-17 09:46 UTCEG score recompute
  32. 2026-06-17 04:53 UTCEG score recompute
  33. 2026-06-17 00:47 UTCEG score recompute
  34. 2026-06-16 20:43 UTCEG score recompute
  35. 2026-06-16 17:52 UTCEPSS rescore
  36. 2026-06-16 16:39 UTCEG score recompute
  37. 2026-06-16 10:42 UTCEG score recompute
  38. 2026-06-16 06:36 UTCEG score recompute
  39. 2026-06-16 02:32 UTCEG score recompute
  40. 2026-06-15 22:27 UTCEG score recompute
  41. 2026-06-15 17:49 UTCEPSS rescore
  42. 2026-06-15 13:40 UTCEG score recompute
  43. 2026-06-15 05:44 UTCEG score recompute
  44. 2026-06-15 01:40 UTCEG score recompute
  45. 2026-06-14 21:35 UTCEG score recompute
  46. 2026-06-14 17:29 UTCEG score recompute
  47. 2026-06-14 13:23 UTCEG score recompute
  48. 2026-06-14 09:19 UTCEG score recompute
  49. 2026-06-14 05:15 UTCEG score recompute
  50. 2026-06-14 01:10 UTCEG score recompute
  51. 2026-06-13 23:00 UTCEPSS rescore
  52. 2026-06-13 21:06 UTCEG score recompute
  53. 2026-06-13 14:03 UTCEG score recompute
  54. 2026-06-13 09:19 UTCEG score recompute
  55. 2026-06-13 05:14 UTCEG score recompute
  56. 2026-06-13 01:09 UTCEG score recompute
  57. 2026-06-12 23:12 UTCEPSS rescore
  58. 2026-06-12 23:12 UTCEPSS rescore
  59. 2026-06-12 21:05 UTCEG score recompute
  60. 2026-06-12 17:00 UTCEG score recompute
  61. 2026-06-12 12:56 UTCEG score recompute
  62. 2026-06-12 08:51 UTCEG score recompute
  63. 2026-06-12 04:48 UTCEG score recompute
  64. 2026-06-12 00:43 UTCEG score recompute
  65. 2026-06-11 20:39 UTCEG score recompute
  66. 2026-06-11 16:36 UTCEG score recompute
  67. 2026-06-11 14:00 UTCEPSS rescore
  68. 2026-06-11 12:18 UTCEG score recompute
  69. 2026-06-11 08:14 UTCEG score recompute
  70. 2026-06-11 04:10 UTCEG score recompute
  71. 2026-06-11 00:05 UTCEG score recompute
  72. 2026-06-10 22:18 UTCEPSS rescore
  73. 2026-06-10 20:01 UTCEG score recompute
  74. 2026-06-10 15:56 UTCEG score recompute
  75. 2026-06-10 13:22 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-44895?
CVE-2026-44895 is a critical vulnerability published on May 26, 2026. GitLab MCP Server lets an AI agent talk directly to GitLab. Prior to 0.6.0, the HTTP transport in src/transport.ts ships with no authentication layer at all and a wildcard Access-Control-Allow-Origin: * on every response. The structural defect is that the SSE server stands up a stateful,…
When was CVE-2026-44895 disclosed?
CVE-2026-44895 was first published in the National Vulnerability Database on May 26, 2026, with the most recent update on June 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44895 actively exploited?
CVE-2026-44895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 31.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44895?
CVE-2026-44895 has a CVSS v3 base score of 9.2 (NVD).
How do I remediate CVE-2026-44895?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44895, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44895

Explore →

Is Your Infrastructure Affected by CVE-2026-44895?

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

Start Free Scan →Browse All CVEs