CVE-2026-50160
CriticalPublic exploitIn 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.
Published Jul 1, 2026 · Updated Aug 12, 2026 · Also known as GHSA-j542-4rch-8hwf
Key Facts
Patch immediately- CVE-2026-50160 is a critical-severity vulnerability (CVSS 10.0 v3.1) affecting Hoppscotch.
- It is not listed in any known-exploited vulnerabilities catalog. Public exploit code is available.
- EPSS estimates a 1.7% probability of exploitation in the next 30 days.
- Fixed versions are available, including Hoppscotch 2026.5.0.
- Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.
CVSS v3.1
10.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
EPSS (30-day exploit likelihood)
1.7%
Higher than 76.8% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
Available
Proof-of-concept or weaponized module
Get the full CVE-2026-50160 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
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 Products
2 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| HoppscotchHoppscotch | >= <= 2026.4.1 | 2026.5.0 |
Patched Releases
Hoppscotch
2026.5.0
Timeline
Publicly disclosed
Jul 1, 2026
Last updated
Aug 12, 2026
Weakness Type
- CWE-915 Improperly Controlled Modification of Dynamically-Determined Object Attributes
References
- advisoryhttps://github.com/CVEProject/cvelistV5/tree/main/cves/2026/50xxx/CVE-2026-50160.json
- advisoryhttps://nvd.nist.gov/vuln/detail/CVE-2026-50160
- otherhttps://github.com/hoppscotch/hoppscotch/pull/6171
- otherhttps://github.com/hoppscotch/hoppscotch/security/advisories/GHSA-j542-4rch-8hwf
- otherhttp://www.openwall.com/lists/oss-security/2026/06/23/7
FAQ
Common Questions.
Hoppscotch is an API development ecosystem.
Affected: Hoppscotch versions >= <= 2026.4.1. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
Public exploit code is available.
Fixed versions are available, including Hoppscotch 2026.5.0.
Brandefense priority: patch immediately, because public exploit code exists for a high-severity flaw.
Is CVE-2026-50160 Running On Your Attack Surface?
Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.
Request A Demo