Companies/Semgrep/Incidents

Semgrep: Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Affected components: Scans and CI/CDsemgrep.dev - Scans and CI/CD

Timeline of updates

1. investigating2026-10-19 21:00 UTC

   Some scans with Semgrep 1.181.0 are unable to be successfully reported to the Semgrep AppSec Platform due to a 400 error. The issue may be related to dynamic dependency resolution.

2. identified2026-10-19 21:20 UTC

   We have identified the issue and are working on a fix.

Changes Rewindex caught on this incident

• Oct 19Incident updated: Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0

Impact, status and times are the vendor’s own, as last archived. View on stspg.io (opens in new tab).

Semgrep profileRecent Semgrep incidentsMarkdownJSON