Cross-user environment access via missing ownership checks
Published Feb 26, 2026 · Updated Feb 26, 2026
Authorization bypass in Hoppscotch Backend before 2026.2.0 allows remote authenticated users to access other users' environments. The updateUserEnvironment and deleteUserEnvironment paths select records by environment ID without enforcing ownership; the update resolver also omits user extraction. Exploitation requires a valid account and another user's CUID, exposing stored API keys and tokens to reading, replacement, or deletion.
Summary
What happened
Authorization bypass in Hoppscotch Backend before 2026.2.0 allows remote authenticated users to access other users' environments. The updateUserEnvironment and deleteUserEnvironment paths select records by environment ID without enforcing ownership; the update resolver also omits user extraction. Exploitation requires a valid account and another user's CUID, exposing stored API keys and tokens to reading, replacement, or deletion.
The record
- CVE
- CVE-2026-28216
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- Hoppscotch
- Product
- Hoppscotch
- Classifications
- CWE-639
- Attack vector
- network
- Privileges
- authenticated
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
- Vendor advisory cross-user environment 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