Semgrep incident

Scan failures with exit code 7 due to invalid rule

Major Resolved View vendor source →

Semgrep experienced a major incident on June 25, 2026 affecting Scans and CI/CD and Managed Scans, lasting 55m. The incident has been resolved; the full update timeline is below.

Started
Jun 25, 2026, 09:32 PM UTC
Resolved
Jun 25, 2026, 10:27 PM UTC
Duration
55m
Detected by Pingoru
Jun 25, 2026, 09:32 PM UTC

Affected components

Scans and CI/CDManaged Scans

Update timeline

  1. identified Jun 25, 2026, 09:32 PM UTC

    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.

  2. monitoring Jun 25, 2026, 10:14 PM UTC

    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.

  3. resolved Jun 25, 2026, 10:27 PM UTC

    This issue has been resolved. Scans are now running normally.