CVE-2026-50160
CriticalCVSS 10.0Exploitation Probability (EPSS)
Low risk44th percentile — higher than 44% of all known CVEs
Summary
In self-hosted Hoppscotch deployments version 2026.4.1 and earlier, the unauthenticated POST /v1/onboarding/config endpoint is vulnerable to mass assignment. The missing whitelist: true in NestJS ValidationPipe allows extra request properties like JWT_SECRET and SESSION_SECRET to be treated as valid InfraConfig entries, enabling an attacker to overwrite them.
Risk Assessment
An attacker can overwrite JWT_SECRET, gaining control of the JWT signing key, which allows forging tokens for any user including administrators, resulting in full server compromise.
Recommendation
Upgrade Hoppscotch to version 2026.5.0 or later immediately. If upgrading is not possible, restrict access to the /v1/onboarding/config endpoint for unauthenticated users at the firewall or proxy level.
Original NVD description (English source)
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.