CVE-2026-47751: Claude Code Action: Malicious MCP Server Configuration in PRs Enables Remote Code Execution and Secret Exfiltration
Claude Code Action is a general-purpose GitHub action that runs Claude Code on GitHub pull requests and issues. Prior to 1.0.74, because the action checked out attacker-controlled pull request head branches, read .mcp.json from the working directory via default setting sources, and unconditionally enabled all project MCP servers via enableAllProjectMcpServers, an attacker who opened a pull request containing a malicious .mcp.json file could achieve arbitrary code execution on the GitHub Actions runner and exfiltrate secrets available to the workflow (such as API keys and tokens) when a privileged user or an automatic trigger invoked the Claude action on the pull request. This issue is fixed in version 1.0.74, which restores .claude/ and .mcp.json from the pull request base branch before the CLI runs.
Security readout for executives and security teams
Plain-English summary
A pull request could change Claude Code Action's MCP configuration before version 1.0.74. If the action ran on that PR with privileged credentials, attacker-supplied configuration could run code on the GitHub Actions runner and expose available workflow secrets.
Executive priority
Prioritize remediation for repositories that run Claude Code Action on external pull requests with secrets or broad GitHub token permissions. The likely business risk is credential exposure and runner-level code execution, not broad internet exploitation.
Technical view
Before 1.0.74, the action checked out the PR head, loaded .mcp.json from the workspace, and enabled all project MCP servers. A malicious PR could influence MCP server execution under the workflow context. Version 1.0.74 restores .claude/ and .mcp.json from the base branch before the CLI runs.
Likely exposure
Exposure is limited to GitHub repositories using anthropics/claude-code-action versions below 1.0.74 where the action runs on pull requests or issues with secrets or privileged tokens available.
Exploitation context
The source bundle does not show known active exploitation or KEV listing. Exploitation requires an attacker-created pull request and invocation of the Claude action under conditions that expose useful workflow secrets or permissions.
Researcher notes
Key conditions are version below 1.0.74, PR head checkout, project MCP settings loaded from the workspace, and automatic enablement of project MCP servers. Evidence supports RCE and secret exfiltration impact, but not observed exploitation.
Mitigation direction
Upgrade anthropics/claude-code-action to version 1.0.74 or later.
Review vendor advisory and release notes for any newer guidance.
Restrict workflow secrets and token permissions for pull request contexts.
Avoid running privileged automation on untrusted pull request content.
Review affected repositories for unexpected MCP configuration changes.
Validation and detection
Inventory GitHub workflows using anthropics/claude-code-action.
Confirm all references resolve to version 1.0.74 or later.
Check whether workflows expose secrets during pull request handling.
Review recent pull requests for modified .mcp.json or .claude/ content.
Validate workflow permissions are least privilege for PR events.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-200: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.