Level 3. Significant control incident
Thousands of exposed GitHub repositories, now private, can still be accessed through Copilot
- Developer
- Not established
- Model
- Not established
- When it happened
- February 26, 2025
- When it was disclosed
- Not established
- How well it is stood up
- Not verified yet
- What caused it
- Not established
- Where it stands now
- Not established
What happened
Reported by techcrunch.com. Listed here with a link to their report. Nobody on this side has checked it against that report, so it carries no level and this is not our account of what happened.
Our assessment
- Actual
- 3 of 5Significant control incident
- Potential
- 3 of 5Significant control incident
An important technical, security or permission boundary was crossed, or there were real consequences. The potential level is what the behaviour demonstrated here could credibly have led to, judged from the same evidence.
This level rests on news reports. The developer has not confirmed it here.
Why this level
- Significant data was exposed. Argues for level 3
- Sensitive data was reachable. Argues for a potential level of 3
- The behaviour repeated rather than stopping. Argues for a potential level of 3
What is established, and what is not
Confirmed
Nothing is confirmed yet.
Reported, not confirmed
The behaviour repeated rather than stopping
However, Lasso says that though the caching feature was disabled, Copilot still had access to the data even though it was not visible through traditional web searches, indicating a temporary fix.
Thousands of exposed GitHub repositories, now private, can still be accessed through CopilotSensitive data was reachable
For some affected companies, Copilot could be prompted to return confidential GitHub archives that contain intellectual property, sensitive corporate data, access keys, and tokens, the company said.
Thousands of exposed GitHub repositories, now private, can still be accessed through CopilotSignificant data was exposed
Using Bing’s caching mechanism, the company found more than 20,000 since-private GitHub repositories still had data accessible through Copilot, affecting more than 16,000 organizations.
Thousands of exposed GitHub repositories, now private, can still be accessed through Copilot
Checked, and did not happen
Nothing here was checked and ruled out.
Not confirmed
Nothing is outstanding.
Where this came from
The original report · read September 24, 2026
Thousands of exposed GitHub repositories, now private, can still be accessed through CopilotA structured incident database · read September 19, 2026
AI Failure Index (CC-BY-4.0 data fields)Where we first saw it
AI Failure Index entry FI-0073, not yet readWhere we first saw it
Tens of thousands of once-private GitHub repos are still accessible through Microsoft Copilot (TechCrunch)
The reports above are other people’s. The levels are ours, worked out under our published rules. No organisation that reported this assigned our number, and none of it is legal advice.
Something here is wrong? Tell us. Send us a source we can open, and a person will read it.