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

- Impact (vendor’s label): minor
- Status: identified · edited after publishing
- Started: 2026-10-19 21:00 UTC · Resolved: not resolved · Duration: ongoing
- Updates: 2 · Affected components: Scans and CI/CD, semgrep.dev - Scans and CI/CD
- [Vendor status page: https://stspg.io/41kxx3zgjhzx](https://stspg.io/41kxx3zgjhzx)
- [Company: Semgrep](https://rewindex.com/company/semgrep.md)

## Timeline of updates

- **investigating** 2026-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.
- **identified** 2026-10-19 21:20 UTC: We have identified the issue and are working on a fix.

## Rewindex changes for this incident

- 2026-10-19 21:23 UTC: [Incident updated: Elevated 400 Bad Request errors when completing scans with Semgrep 1.181.0](https://rewindex.com/change/r347b63fc5fd3a8.md)


---
Canonical: https://rewindex.com/company/semgrep/incidents/k81hzf4f7d75 · Markdown: https://rewindex.com/company/semgrep/incidents/k81hzf4f7d75.md · JSON: https://rewindex.com/api/v1/companies/semgrep/incidents/k81hzf4f7d75 · Generated 2026-10-19T22:47:41.114Z