CVE-2026-61559

CRITICALPre-NVD 9.69.6
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-80004 (ENISA EUVD) · GHSA-2h44-8472-frjj (GitHub Security Advisories)Source: ENISA EUVD

9.6EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 9.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

@zereight/mcp-gitlab is a Model Context Protocol server for GitLab. Starting in version 0.0.1 and prior to version 2.1.27, when the environment variable ENABLE_DYNAMIC_API_URL=true is set, the server reads the X-GitLab-API-URL HTTP request header and uses it as the base URL for all outbound GitLab API calls made within that request. The server validates that the value is a well-formed URL (new URL(dynamicApiUrl)) but applies no allowlist or hostname restriction. The server then attaches the victim's Private-Token to every outbound fetch that uses the redirected URL. Any caller who can reach the HTTP transport can set X-GitLab-API-URL to an attacker-controlled host. The next GitLab API call the server makes delivers the victim's token to that host. Version 2.1.27 contains a patch.

CVSS v3
9.6
EG Score
9.6CRITICALmedium confidence
EG Risk
59
EG Risk 59/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity96% × 45%
Impact severity (EG Severity): CVSS 9.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
37th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.6): severity, escalated by confirmed exploitation. This CVE's 9.6 is its impact severity (EG Severity), not escalated.

EG Severity
9.6 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 15, 2026

Last Modified

September 30, 2026

Advisory Details (4)

Auto-updated Oct 2, 2026
Patch available. Sources: github_commit, github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

Server-Side Request Forgery (SSRF) in zereight/mcp-gitlab · Advisory · zereight/gitlab-mcp · GitHub

https://github.com/zereight/gitlab-mcp/security/advisories/GHSA-2h44-8472-frjj
GitHub release Patch Available

v2.1.27

Patch available: zereight/gitlab-mcp v2.1.27

https://github.com/zereight/gitlab-mcp/releases/tag/v2.1.27
GitHub pull request Patch Available

fix: add remediation hints for GHSA-2h44-8472-frjj dynamic URL rejections

Patch available: zereight/gitlab-mcp v2.1.43 (PR #625 merged 2026-07-26)

https://github.com/zereight/gitlab-mcp/pull/625
GitHub commit Patch Available

commit 6ffb4cc70706 (zereight/gitlab-mcp)

Patch available: zereight/gitlab-mcp v2.1.43 (contains commit 6ffb4cc70706)

https://github.com/zereight/gitlab-mcp/commit/6ffb4cc70706fd05b1ab80901676bc2998b6db6d

Vendor Advisories for CVE-2026-61559(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npm@zereight/mcp-gitlab @ 2.1.27 (fixes >= 0.0.1, < 2.1.27)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
@zereight/mcp-gitlab—
  • 0.0.1 up to 2.1.27: fixed in 2.1.27
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 15× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 131 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 31 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 17:10 UTCEchelonGraph re-scored
  2. 2026-11-12 17:10 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  3. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-11 19:24 UTCEchelonGraph re-scored
  5. 2026-11-11 19:24 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  6. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  7. 2026-11-10 21:38 UTCEchelonGraph re-scored
  8. 2026-11-10 21:38 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  9. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  10. 2026-11-09 23:48 UTCEchelonGraph re-scored
  11. 2026-11-09 23:48 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  12. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  13. 2026-11-09 02:02 UTCEchelonGraph re-scored
  14. 2026-11-09 02:02 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  15. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  16. 2026-11-08 04:18 UTCEchelonGraph re-scored
  17. 2026-11-08 04:18 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  18. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  19. 2026-11-07 06:27 UTCEchelonGraph re-scored
  20. 2026-11-07 06:27 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  21. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  22. 2026-11-06 14:25 UTCOSV refresh
  23. 2026-11-06 08:41 UTCEchelonGraph re-scored
  24. 2026-11-06 08:41 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  25. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 37th percentile
Show 75 more
  1. 2026-11-05 10:56 UTCEchelonGraph re-scored
  2. 2026-11-05 10:56 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  3. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.4% · 37th percentile
  4. 2026-11-04 13:10 UTCEchelonGraph re-scored
  5. 2026-11-04 13:10 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  6. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  7. 2026-11-03 15:23 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  8. 2026-11-02 17:38 UTCEchelonGraph re-scored
  9. 2026-11-02 17:38 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  10. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  11. 2026-11-01 19:52 UTCEchelonGraph re-scored
  12. 2026-11-01 19:52 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  13. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  14. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-2h44-8472-frjj · GitHub severity CRITICAL · GitHub CVSS 9.6
  15. 2026-11-01 07:41 UTCEchelonGraph re-scored
  16. 2026-10-31 22:08 UTCEchelonGraph re-scored
  17. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  18. 2026-10-31 00:19 UTCEchelonGraph re-scored
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  20. 2026-10-30 02:34 UTCEchelonGraph re-scored
  21. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  22. 2026-10-29 04:49 UTCEchelonGraph re-scored
  23. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  24. 2026-10-28 07:00 UTCEchelonGraph re-scored
  25. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  26. 2026-10-27 09:15 UTCEchelonGraph re-scored
  27. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  28. 2026-10-26 10:52 UTCEchelonGraph re-scored
  29. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  30. 2026-10-25 14:14 UTCEchelonGraph re-scored
  31. 2026-10-25 13:07 UTCEchelonGraph re-scored
  32. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  33. 2026-10-23 17:36 UTCEchelonGraph re-scored
  34. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  35. 2026-10-22 19:50 UTCEchelonGraph re-scored
  36. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  37. 2026-10-21 22:05 UTCEchelonGraph re-scored
  38. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  39. 2026-10-21 00:11 UTCEchelonGraph re-scored
  40. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  41. 2026-10-20 02:22 UTCEchelonGraph re-scored
  42. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  43. 2026-10-19 01:44 UTCEchelonGraph re-scored
  44. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  45. 2026-10-18 03:25 UTCEchelonGraph re-scored
  46. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  47. 2026-10-17 06:12 UTCEchelonGraph re-scored
  48. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  49. 2026-10-16 07:18 UTCEchelonGraph re-scored
  50. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  51. 2026-10-15 06:13 UTCEchelonGraph re-scored
  52. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-10-14 01:50 UTCEchelonGraph re-scored
  54. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  55. 2026-10-12 22:05 UTCEchelonGraph re-scored
  56. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  57. 2026-10-12 15:50 UTCEchelonGraph re-scored
  58. 2026-10-11 19:34 UTCEchelonGraph re-scored
  59. 2026-10-11 16:49 UTCEchelonGraph re-scored
  60. 2026-10-11 14:11 UTCEchelonGraph re-scored
  61. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  62. 2026-10-10 20:16 UTCEchelonGraph re-scored
  63. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  64. 2026-10-09 23:11 UTCEchelonGraph re-scored
  65. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  66. 2026-10-08 20:54 UTCEchelonGraph re-scored
  67. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  68. 2026-10-08 02:51 UTCEchelonGraph re-scored
  69. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  70. 2026-10-06 18:51 UTCEchelonGraph re-scored
  71. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  72. 2026-10-05 21:49 UTCEchelonGraph re-scored
  73. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 34th percentile
  74. 2026-10-05 00:37 UTCEchelonGraph re-scored
  75. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 34th percentile

Frequently asked(5)

What is CVE-2026-61559?
CVE-2026-61559 is a critical-severity vulnerability; its CVE record was published on September 15, 2026. @zereight/mcp-gitlab is a Model Context Protocol server for GitLab. Starting in version 0.0.1 and prior to version 2.1.27, when the environment variable ENABLE_DYNAMIC_API_URL=true is set, the server reads the X-GitLab-API-URL HTTP request header and uses it as the base URL for all outbound GitLab…
When was the CVE record for CVE-2026-61559 published?
The CVE record for CVE-2026-61559 was published on September 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-61559 actively exploited?
CVE-2026-61559 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61559?
CVE-2026-61559 has a CVSS base score of 9.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61559?
A fix for CVE-2026-61559 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61559 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61559?

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