Changes / Semgrep / Scan failures with exit code 7 due to invalid rule
Semgrep: Major incident: Scan failures with exit code 7 due to invalid rule
Summary
Semgrep reported a major incident causing widespread exit code 7 scan failures in Managed Scans and Scans and CI/CD from 2026-06-25 21:32 UTC to 2026-06-25 22:27 UTC (55 min). A bad AI skills rules release caused the failures; Semgrep removed "skills.behavioral.skill-destructive-commands.skill-destructive-commands" and confirmed scans were running normally.
Machine-written from the diff below (Sol; type: incident outage). Check the diff before relying on it.
What changed
Before: not present
After: Scan failures with exit code 7 due to invalid rule
Before: not present
After: major
Before: not present
After: resolved
Before: not present
After: 2026-06-25 21:32 UTC
Before: not present
After: 2026-06-25 22:27 UTC
Before: not present
After: Managed Scans, Scans and CI/CD, semgrep.dev - Managed Scans, semgrep.dev - Scans and CI/CD
Before: not present
After: We have observed widespread scan failures relating to a bad release of AI skills rules. We are working to fix the issue.
To prevent the issue in the meantime, you can disable the "skills.behavioral.skill-destructive-commands.skill-destructive-commands" rule in your Semgrep policies.
Before: not present
After: We have removed the problem rule ("skills.behavioral.skill-destructive-commands.skill-destructive-commands") and we are seeing scan behavior recover. We are continuing to monitor for full recovery.
Before: not present
After: This issue has been resolved. Scans are now running normally.
First version of this incident archived by Rewindex. View the live incident (opens in new tab).
History of this incident
| When (UTC) | Change | Kind |
|---|---|---|
| Major incident: Scan failures with exit code 7 due to invalid rule (this change) Semgrep reported a major incident causing widespread exit code 7 scan failures in Managed Scans and Scans and CI/CD from 2026-06-25 21:32 UTC to 2026-06-25 22:27 UTC (55 min). A bad AI skills rules release caused the failures; Semgrep removed "skills.behavioral.skill-destructive-commands.skill-destructive-commands" and confirmed scans were running normally. | Major incident |