Unauthenticated configuration takeover via unguarded onboarding
Published Feb 26, 2026 · Updated Feb 26, 2026
Authentication bypass in Hoppscotch before 2026.2.0 allows remote attackers to overwrite self-hosted infrastructure configuration. The POST /v1/onboarding/config controller applies only rate limiting, then persists untrusted settings without authentication or a completed-onboarding check. Any network client that can reach the backend can replace OAuth and SMTP settings and obtain a recovery token that reveals stored secrets.
Summary
What happened
Authentication bypass in Hoppscotch before 2026.2.0 allows remote attackers to overwrite self-hosted infrastructure configuration. The POST /v1/onboarding/config controller applies only rate limiting, then persists untrusted settings without authentication or a completed-onboarding check. Any network client that can reach the backend can replace OAuth and SMTP settings and obtain a recovery token that reveals stored secrets.
The record
- CVE
- CVE-2026-28215
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- Hoppscotch
- Product
- Hoppscotch
- Classifications
- CWE-284, CWE-287, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 26, 2026CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2026.2.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub advisory onboarding takeover proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo