CVE-2026-61462

HIGHPre-NVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 3 sources updated this weekElevated
8.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.5%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

mcp-gitlab contains a path traversal vulnerability in the job_id parameter of build/index.js that allows attackers to redirect GitLab API requests to arbitrary endpoints. Attackers can supply crafted job_id values like ../../../user to escape the intended path prefix and access arbitrary GitLab API resources using the operator's personal access token.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/100

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 (value × EchelonGraph’s weight)
Severity86% × 45%
The EG Score, 8.6 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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.5%
EPSS %ILE
39th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

July 13, 2026

Last Modified

October 8, 2026

Advisory Details (4)

Auto-updated Jul 13, 2026
Patch available. Sources: github_commit.
Web page

mcp-gitlab Path Traversal via job_id Parameter | Advisories | VulnCheck

https://www.vulncheck.com/advisories/mcp-gitlab-path-traversal-via-job-id-parameter
GitHub commit Patch Available

commit e2a81a047ab8 (zereight/gitlab-mcp)

Patch available: zereight/gitlab-mcp v2.1.32 (contains commit e2a81a047ab8)

https://github.com/zereight/gitlab-mcp/commit/e2a81a047ab8750fa5bfa1763b5d85e5616f3994
Web page

GitHub - zereight/gitlab-mcp: First gitlab mcp for you, building together · GitHub

https://github.com/zereight/gitlab-mcp
Web page

Path traversal in job_id turns a job tool into an arbitrary GitLab API request under the operator token · Issue #587 · zereight/gitlab-mcp · GitHub

https://github.com/zereight/gitlab-mcp/issues/587

Vendor Advisories for CVE-2026-61462(1)

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 17× in last 7d / 43× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 224 refreshes 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 124 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-61462?
CVE-2026-61462 is a high-severity vulnerability; its CVE record was published on July 13, 2026. mcp-gitlab contains a path traversal vulnerability in the jobid parameter of build/index.js that allows attackers to redirect GitLab API requests to arbitrary endpoints. Attackers can supply crafted jobid values like ../../../user to escape the intended path prefix and access arbitrary GitLab API…
When was CVE-2026-61462 made public?
CVE-2026-61462 was made public on July 8, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on July 13, 2026. EchelonGraph's copy of the record carries a last-modified date of October 8, 2026; the record at its source may have been updated since.
Is CVE-2026-61462 actively exploited?
CVE-2026-61462 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61462?
CVE-2026-61462 has a CVSS base score of 8.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61462?
A fix for CVE-2026-61462 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61462 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-61462?

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

Book a Demo →Browse All CVEs