Companies / Semgrep / incidents

Semgrep: Scan failures with exit code 7 due to invalid rule

Impact: majorStatus: resolvedStarted Resolved (56 min)3 updatesSource: stspg.io (opens in new tab)
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 archived incident (Sol). Check the timeline before relying on it.

Affected components: Scans and CI/CDsemgrep.dev - Scans and CI/CDManaged Scanssemgrep.dev - Managed Scans

Timeline of updates

  1. identified

    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

    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

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

Rewindex changes for this incident

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab). Semgrep profile · Recent Semgrep incidents · Markdown · JSON