Semgrep incident

Some scans failing with exit code 7

Resolved after 4 hours 37 minutes, affecting Scans and CI/CD and Managed Scans, on November 24, 2025.

resolved Nov 24, 2025, 11:30 PM UTC

This issue has been resolved. No new Managed Scans since the fix have encountered an unexpected exit code 7. If you are not using Managed Scans and encounter an unexpected scan exit code 7, please re-attempt the scan with Semgrep version 1.142.3 or earlier. If you continue to encounter issues, contact Semgrep Support.

Started
Nov 24, 2025, 06:52 PM UTC
Resolved
Nov 24, 2025, 11:30 PM UTC
Duration
4h 37m
Detected by Pingoru
Nov 24, 2025, 06:52 PM UTC

Affected components

Scans and CI/CDManaged Scans

Update timeline

  1. investigating Nov 24, 2025, 06:52 PM UTC

    We've seen that some scans are failing with exit code 7, indicating an issue with a rule. We are investigating the cause.

  2. monitoring Nov 24, 2025, 08:53 PM UTC

    We have released a fix and are now monitoring the results. We are seeing previously affected scans completing successfully.

  3. monitoring Nov 24, 2025, 09:13 PM UTC

    Most scans are now completing successfully. Some longer-running scans may still exit with code 7. We are continuing to monitor.

  4. resolved Nov 24, 2025, 11:30 PM UTC

    This issue has been resolved. No new Managed Scans since the fix have encountered an unexpected exit code 7. If you are not using Managed Scans and encounter an unexpected scan exit code 7, please re-attempt the scan with Semgrep version 1.142.3 or earlier. If you continue to encounter issues, contact Semgrep Support.

Your product runs on more than Semgrep

Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.

Add your stack →