Hoppscotch
Mass Assignment via Onboarding Endpoint Allows Unauthenticated JWT_SECRET Overwrite
Hoppscotch is an API development ecosystem. In self-hosted deployments of hoppscotch-backend from version 2026.4.1 and earlier, the unauthenticated POST /v1/onboarding/config endpoint is vulnerable to mass assignment. The global NestJS ValidationPipe is configured without whitelist: true, so extra properties on the request body that are not declared in SaveOnboardingConfigRequest are not stripped and are iterated in the service layer as if they were legitimate InfraConfig entries. Because keys such as JWT_SECRET and SESSION_SECRET are valid InfraConfigEnum values and are not explicitly rejected during validation, an unauthenticated attacker who can reach a fresh instance before onboarding completes (or when no users exist) can overwrite these values in the database. Overwriting JWT_SECRET gives the attacker control of the JWT signing key, allowing them to forge tokens for any user, including administrators, and results in full server compromise. The issue is fixed in hoppscotch 2026.5.0.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- <= 2026.4.1
Mitigation
The record names no fix. Check the vendor advisory below.
References
Timeline
Days relative to CVE publicationFirst public PoC 38 days after publication; not in CISA KEV. First PoC: nuclei template: Hoppscotch <= 2026.4.1 - Mass Assignment JWT_SECRET Overwrite (nuclei template, 8 Aug 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: Hoppscotch <= 2026.4.1 - Mass Assignment JWT_SECRET Overwrite | 8 Aug 2026 | 14 Nov 2026 |