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.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.0Exploit: NoneExposed: 0

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

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.0(medium)
EPSS
10.6%
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.
github Patch Available🟡 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 23× 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-07-07 05:08 UTCEG score recompute
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 06:31 UTCEG score recompute
  4. 2026-07-05 07:55 UTCEG score recompute
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 09:19 UTCEG score recompute
  7. 2026-07-04 06:31 UTCEPSS rescore
  8. 2026-07-03 10:43 UTCEG score recompute
  9. 2026-07-02 12:06 UTCEG score recompute
  10. 2026-07-01 15:07 UTCEPSS rescore
  11. 2026-07-01 13:29 UTCEG score recompute
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-30 14:53 UTCEG score recompute
  14. 2026-06-29 16:10 UTCEG score recompute
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-28 17:34 UTCEG score recompute
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 04:56 UTCEPSS rescore
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 18:57 UTCEG score recompute
  22. 2026-06-26 20:21 UTCEG score recompute
  23. 2026-06-25 21:46 UTCEG score recompute

Related CVEs(same CWE)

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 in the National Vulnerability Database 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 10.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-48529?
CVE-2026-48529 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-48529?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48529, 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-48529

Explore →

Is Your Infrastructure Affected by CVE-2026-48529?

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

Start Free Scan →Browse All CVEs