Security readout for executives and security teams
Plain-English summary
CVE-2026-28216 lets any authenticated Hoppscotch user access another user’s personal environment if they know its ID. These environments can contain API keys, tokens, and secrets. The ID format reduces broad guessing, but insider access or another information leak could make targeted abuse realistic. Hoppscotch fixed this in version 2026.2.0.
Executive priority
Treat as high priority where Hoppscotch stores production or sensitive API credentials. The issue could expose or alter secrets, enabling downstream compromise beyond Hoppscotch. Upgrade promptly and rotate credentials if affected instances had untrusted or broad user access.
Technical view
Before Hoppscotch 2026.2.0, updateUserEnvironment and deleteUserEnvironment lacked proper object ownership enforcement. updateUserEnvironment did not extract the authenticated user, and deleteUserEnvironment did not constrain deletion by userUid. Operations used environment ID without an ownership filter, creating a CWE-639 IDOR affecting confidentiality, integrity, and limited availability.
Likely exposure
Self-hosted or managed Hoppscotch deployments running versions earlier than 2026.2.0 are affected. Exposure requires a logged-in user and a target environment ID. Environments may contain API credentials, auth tokens, and request secrets.
Exploitation context
No active exploitation is stated in the provided sources, and the CVE is not marked KEV. Exploitation requires authentication and knowledge of another user’s environment ID. CUID IDs reduce mass exploitation, but insider threats and combined information disclosure scenarios remain credible.
Researcher notes
The core issue is broken object-level authorization on personal environment mutations. The advisory notes update by ID without ownership filtering and delete by ID without userUid constraint. Do not assume unauthenticated exposure. Evidence does not establish exploitation in the wild.
Mitigation direction
- Upgrade Hoppscotch to version 2026.2.0 or later.
- Review the GitHub advisory and release notes for vendor guidance.
- Rotate API keys, tokens, and secrets stored in affected environments.
- Review logs for unexpected environment reads, updates, or deletions.
- Limit Hoppscotch accounts to users with a business need.
Validation and detection
- Inventory Hoppscotch instances and confirm deployed versions.
- Identify any instances running versions earlier than 2026.2.0.
- Confirm environment access controls enforce ownership after upgrade.
- Review audit or application logs for unusual environment activity.
- Verify stored secrets were rotated where exposure is plausible.
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-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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 lookupCVE-2026-28216 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
- High
- CVSS
- 8.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
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:L/UI:N/S:U/C:H/I:H/A:L2.85.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
8.3HighVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/hoppscotch/hoppscotch/security/advisories/GHSA-72rv-vc3j-5vqrCVE 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.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
