# CVE-2026-28216: hoppscotch has IDOR in updateUserEnvironment / deleteUserEnvironment

> Authenticated attackers can read, modify, or delete other users' API environments containing secrets due to missing ownership checks.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-72rv-vc3j-5vqr

## What is CVE-2026-28216?

CVE-2026-28216 is a high-severity missing authorization vulnerability in hoppscotch, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-28216?

It affects 1 product.


Products: Hoppscotch Hoppscotch.

## How do I fix CVE-2026-28216?

No fix has been published for CVE-2026-28216 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-28216 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28216 exists.

## Other vulnerabilities in hoppscotch

- [CVE-2026-50160](https://insights.sbomify.com/CVE-2026-50160/): Mass Assignment via Onboarding Endpoint Allows Unauthenticated JWT_SECRET Overwrite (critical 10.0)
- [CVE-2026-28215](https://insights.sbomify.com/CVE-2026-28215/): hoppscotch Vulnerable to Unauthenticated Onboarding Config Takeover (critical 9.1)
- [CVE-2026-34931](https://insights.sbomify.com/CVE-2026-34931/): hoppscotch: Improper loopback redirect_uri validation in device-login flow (high 8.5)
- [CVE-2026-34932](https://insights.sbomify.com/CVE-2026-34932/): hoppscotch: Stored XSS via mock server responses on backend origin (high 8.5)
- [CVE-2022-0121](https://insights.sbomify.com/CVE-2022-0121/): Cross-site Scripting in hoppscotch/hoppscotch (high 8.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-28216 and fix it if it is affected.

What it is: CVE-2026-28216 is a high-severity missing authorization vulnerability in hoppscotch, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-28216 exists.

Affected product: hoppscotch. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-28216/ (Markdown: https://insights.sbomify.com/CVE-2026-28216/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-28216
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-28216
- OSV: https://osv.dev/vulnerability/CVE-2026-28216

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-28216/
Summaries are generated and may contain mistakes; the official description above is the record.