CVE-2026-48529

MEDIUMPre-NVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 89% 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, secondary
6.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 6.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

GitHub MCP Server is GitHub's official MCP Server. From 0.22.0 until 1.1.2, when running in HTTP mode with --lockdown-mode enabled, the RepoAccessCache is implemented as a process-global singleton initialized with the first authenticated user's GraphQL client. All subsequent requests from different users share this singleton and their lockdown-related GraphQL queries are executed using the first user's credentials. The singleton is never updated to reflect later users' tokens. This vulnerability is fixed in 1.1.2.

CVSS v3
6.0
EG Score
6.0MEDIUMmedium confidence
EG Risk
32
EG Risk 32/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
Severity60% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
9th
KEV
Not listed

Published

June 25, 2026

Last Modified

June 27, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Lockdown mode singleton in HTTP server causes cross-user GraphQL client confusion · Advisory · github/github-mcp-server · GitHub

https://github.com/github/github-mcp-server/security/advisories/GHSA-pjp5-fpmr-3349

Vendor Advisories for CVE-2026-48529(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)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/github/github-mcp-server—
  • 0.22.0 up to 1.1.2: fixed in 1.1.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× 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.

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

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

Related CVEs(same product + same CWE)

Same product

1 shown

Go:github.com/github/github-mcp-server

Frequently asked(5)

What is CVE-2026-48529?
CVE-2026-48529 is a medium vulnerability published on June 25, 2026. GitHub MCP Server is GitHub's official MCP Server. From 0.22.0 until 1.1.2, when running in HTTP mode with --lockdown-mode enabled, the RepoAccessCache is implemented as a process-global singleton initialized with the first authenticated user's GraphQL client. All subsequent requests from different…
When was CVE-2026-48529 disclosed?
CVE-2026-48529 was first published on June 25, 2026, with the most recent update on June 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48529 actively exploited?
CVE-2026-48529 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-48529?
CVE-2026-48529 has a CVSS base score of 6.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-48529?
A fix for CVE-2026-48529 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-48529 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-48529

Explore →

Is Your Infrastructure Affected by CVE-2026-48529?

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

Book a Demo →Browse All CVEs