Security readout for executives and security teams
Plain-English summary
Self-hosted Hoppscotch instances before 2026.2.0 can have their onboarding configuration overwritten without login. An attacker could redirect future SSO logins through attacker-controlled OAuth apps and obtain sensitive login-related data. The advisory also says a returned recovery token can expose stored secrets in plaintext. Treat exposed self-hosted deployments as urgent.
Executive priority
Prioritize within the current emergency patch cycle for any exposed self-hosted Hoppscotch instance. The issue can compromise login trust and stored secrets without credentials, making delayed remediation risky even without confirmed active exploitation.
Technical view
CVE-2026-28215 affects Hoppscotch before 2026.2.0. The onboarding configuration endpoint lacks authentication and does not verify onboarding completion. This enables unauthenticated replacement of OAuth and SMTP configuration. The advisory reports recovery token exposure that permits reading stored secrets in plaintext. CVSS is 9.1, with network attack vector, low complexity, no privileges, and no user interaction.
Likely exposure
Exposure is most likely in self-hosted Hoppscotch deployments running versions earlier than 2026.2.0, especially if reachable from untrusted networks. SaaS or managed exposure is not established by the provided sources.
Exploitation context
The provided sources describe a remotely reachable, unauthenticated configuration takeover path. CISA KEV is not indicated, and the provided bundle does not cite active exploitation in the wild.
Researcher notes
The root issue is missing authentication and missing onboarding state validation for configuration update behavior. Evidence comes from the GitHub advisory and CVE record. Avoid assuming exploitation telemetry; the supplied sources do not establish active exploitation or affected hosted services.
Mitigation direction
- Upgrade self-hosted Hoppscotch to version 2026.2.0 or later.
- Review vendor advisory and release notes for any additional required actions.
- Rotate OAuth application credentials used by affected Hoppscotch instances.
- Rotate SMTP passwords and other secrets stored in Hoppscotch configuration.
- Review SSO provider logs for unexpected OAuth application activity.
- Restrict external access to administrative or onboarding-related routes where feasible.
Validation and detection
- Inventory all self-hosted Hoppscotch instances and record versions.
- Confirm affected instances are upgraded to 2026.2.0 or later.
- Verify OAuth provider settings match approved application credentials.
- Check whether SMTP and other stored secrets were changed unexpectedly.
- Review authentication logs after the suspected exposure window.
- Document whether the instance was internet-accessible before remediation.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-284: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCWE-287: Credential and account abuse lookup
Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28215 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/hoppscotch/hoppscotch/security/advisories/GHSA-jwv8-867r-q9fgCVE reference · x_refsource_CONFIRM
- https://github.com/hoppscotch/hoppscotch/releases/tag/2026.2.0CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Access Control
Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Authentication
Improper Authentication represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.