Last seen February 24, 2026

Copilot Prompt Injection Vulnerability

Evidence indicates that Copilot is affected by a security issue.

Technical Severity
Low severity
Lifecycle Status

STABLE

What Happened

Evidence indicates that Copilot is affected by a security issue.

Why This Matters

Publisher reporting describes a concrete security event. BugSkan could not yet bind it to a CVE or affected version, so treat the source details as the current record.

Recommended Action

No confirmed vendor remediation is available in the current evidence. Confirm whether Copilot is present in your environment and review the affected configuration.

Exposure

My AI Stack Exposure

Exposure unknown

Recommended Response
Last Seen

Feb 24, 2026 05:30

Exposure reason: This incident does not currently match a technology in My AI Stack.

Exploitation status: UNKNOWN

Primary entities:

GitHubMicrosoftCopilotGitHub CodespacesPrompt InjectionGitHub Codespaces Enabled

Timeline

  • Incident first seen
    Feb 24, 2026 05:30

    BugSkan first recorded this incident.

  • RoguePilot Flaw in GitHub Codespaces Enabled Copilot to Leak GITHUB_TOKEN - The Hacker News
    Feb 24, 2026 05:30

    thehackernews.com · Vulnerability

Sources

RoguePilot Flaw in GitHub Codespaces Enabled Copilot to Leak GITHUB_TOKEN - The Hacker News

thehackernews.com · Feb 24, 2026 05:30

The RoguePilot vulnerability in GitHub Codespaces leveraged passive prompt injection within GitHub issues to manipulate Copilot. This enabled attackers to silently execute malicious commands and exfiltrate sensitive data, specifically the `GITHUB_TOKEN`, to external servers.

Open publisher source

My AI Stack Match

Want personalized relevance?

Create an account to see which incidents overlap with your AI stack.

← Back to incident intelligence