Cross-user content-filter bypass via singleton credentials
Published Jun 26, 2026 · Updated Jun 26, 2026
Improper access control in GitHub MCP Server 0.22.0 through 1.1.1 allows remote authenticated users to bypass content filtering. The process-global RepoAccessCache retains the first request’s GraphQL client, so later users’ access and visibility checks run with stale credentials. Exploitation requires multi-user HTTP mode with lockdown enabled and can expose unsanitized contributor content or interrupt checks after the first token expires.
Summary
What happened
Improper access control in GitHub MCP Server 0.22.0 through 1.1.1 allows remote authenticated users to bypass content filtering. The process-global RepoAccessCache retains the first request’s GraphQL client, so later users’ access and visibility checks run with stale credentials. Exploitation requires multi-user HTTP mode with lockdown enabled and can expose unsanitized contributor content or interrupt checks after the first token expires.
The record
- CVE
- CVE-2026-48529
- Published
- Jun 26, 2026
- Updated
- Jun 26, 2026
- Vendor
- Product
- GitHub MCP Server
- Classifications
- CWE-284
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 26, 2026CVE publishedPublication date reported by the CVE source.
- Jun 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 0.22.0, < 1.1.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- RepoAccessCache singleton proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo