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

Published Feb 26, 2026
·
Updated

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.

Affected Software

2 affected components
npm/hoppscotch<2026.2.0
hoppscotch hoppscotch<2026.2.0

Event History

Feb 26, 2026
CVE Published
via MITRE·10:34 PM
Data Sourced
via MITRE·10:34 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:16 PM
DescriptionSeverityWeaknessAffected Software
Jun 27, 58142
Event
via FIRST·07:46 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-28215?

CVE-2026-28215 is considered a high-severity vulnerability due to the potential for unauthorized configuration takeover.

2

How do I fix CVE-2026-28215?

To fix CVE-2026-28215, upgrade Hoppscotch to version 2026.2.0 or above.

3

Who is affected by CVE-2026-28215?

CVE-2026-28215 affects self-hosted instances of Hoppscotch prior to version 2026.2.0.

4

What kind of attack is possible with CVE-2026-28215?

An unauthenticated attacker can exploit CVE-2026-28215 to overwrite the infrastructure configuration of Hoppscotch.

5

Does CVE-2026-28215 require authentication to exploit?

No, CVE-2026-28215 can be exploited without authentication.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203