# CVE-2026-28215: hoppscotch Vulnerable to Unauthenticated Onboarding Config Takeover

> Unauthenticated attackers can overwrite self-hosted Hoppscotch configurations, hijacking OAuth credentials and reading stored secrets via an unprotected onboarding endpoint.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2026
- **Updated:** 2 Mar 2026
- **Also known as:** GHSA-jwv8-867r-q9fg

## What is CVE-2026-28215?

CVE-2026-28215 is a critical missing authorization vulnerability in hoppscotch, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

hoppscotch is an open source API development ecosystem. Prior to version 2026.2.0, an unauthenticated attacker can overwrite the entire infrastructure configuration of a self-hosted Hoppscotch instance including OAuth provider credentials and SMTP settings  by sending a single HTTP POST request with no authentication. The endpoint POST /v1/onboarding/config has no authentication guard and performs no check on whether onboarding was already completed. A successful exploit allows the attacker to replace the instance's Google/GitHub/Microsoft OAuth application credentials with their own, causing all subsequent user logins via SSO to authenticate against the attacker's OAuth app. The attacker captures OAuth tokens and email addresses of every user who logs in after the exploit. Additionally, the endpoint returns a recovery token that can be used to read all stored secrets in plaintext, including SMTP passwords and any other configured credentials. Version 2026.2.0 fixes the issue.

Weakness: CWE-287 (Improper Authentication), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Hoppscotch Hoppscotch.

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

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

## Is CVE-2026-28215 being exploited?

There is no known exploitation of CVE-2026-28215 in the wild and no public exploit code.

## 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-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-2026-28216](https://insights.sbomify.com/CVE-2026-28216/): hoppscotch has IDOR in updateUserEnvironment / deleteUserEnvironment (high 8.3)
- [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-28215 and fix it if it is affected.

What it is: CVE-2026-28215 is a critical missing authorization vulnerability in hoppscotch, published on 26 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-28215 in the wild and no public exploit code.

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-28215/ (Markdown: https://insights.sbomify.com/CVE-2026-28215/index.md)
```

## Sources

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

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