No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 27 Feb 2026 19:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 27 Feb 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:hoppscotch:hoppscotch:*:*:*:*:*:*:*:* |
Fri, 27 Feb 2026 09:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Hoppscotch
Hoppscotch hoppscotch |
|
| Vendors & Products |
Hoppscotch
Hoppscotch hoppscotch |
Thu, 26 Feb 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | hoppscotch is an open source API development ecosystem. Prior to version 2026.2.0, any logged-in user can read, modify or delete another user's personal environment by ID. `user-environments.resolver.ts:82-109`, `updateUserEnvironment` mutation uses `@UseGuards(GqlAuthGuard)` but is missing the `@GqlUser()` decorator entirely. The user's identity is never extracted, so the service receives only the environment ID and performs a `prisma.userEnvironment.update({ where: { id } })` without any ownership filter. `deleteUserEnvironment` does extract the user but the service only uses the UID to check if the target is a global environment. Actual delete query uses WHERE { id } without AND userUid. hoppscotch environments store API keys, auth tokens and secrets used in API requests. An authenticated attacker who obtains another user's environment ID can read their secrets, replace them with malicious values or delete them entirely. The environment ID format is CUID, which limits mass exploitation but insider threat and combined info leak scenarios are realistic. Version 2026.2.0 fixes the issue. | |
| Title | hoppscotch has IDOR in updateUserEnvironment / deleteUserEnvironment | |
| Weaknesses | CWE-639 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-02-27T18:43:16.218Z
Reserved: 2026-02-25T15:28:40.649Z
Link: CVE-2026-28216
Updated: 2026-02-27T18:43:11.472Z
Status : Analyzed
Published: 2026-02-26T23:16:36.100
Modified: 2026-02-27T15:51:42.330
Link: CVE-2026-28216
No data.
OpenCVE Enrichment
Updated: 2026-02-27T09:03:51Z