LiveActive security incident?Get immediate response
CVE Record

CVE-2026-28217: IDOR in GraphQL userCollection Query Exposes Other Users' Private Collections

hoppscotch is an open source API development ecosystem. Prior to version 2026.2.0, the `userCollection` GraphQL query accepts an arbitrary collection ID and returns the full collection data — including title, type, and the serialized `data` field containing HTTP requests with headers and potentially secrets — to any authenticated user, without verifying that the requesting user owns the collection. This is an Insecure Direct Object Reference (IDOR) caused by a missing authorization check that exists on every other operation in the same resolver. Version 2026.2.0 fixes the issue.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Hoppscotch before 2026.2.0 could let any logged-in user view another user’s private collection if they know or obtain its collection ID. Collections may include API request details, headers, and possible secrets. This is primarily a confidentiality risk, not a system takeover issue.

Executive priority

Treat as a timely confidentiality fix. Prioritize environments with many users, shared workspaces, or stored API secrets. Upgrade during the next urgent maintenance window, and rotate any secrets that may have been stored in private collections.

Technical view

CVE-2026-28217 is a CWE-862 missing authorization check in the Hoppscotch GraphQL `userCollection` query. The query accepted arbitrary collection IDs and returned full collection data without verifying ownership. CVSS is 6.5: network-accessible, low complexity, authenticated access required, high confidentiality impact, no integrity or availability impact.

Likely exposure

Self-hosted or managed Hoppscotch deployments running versions earlier than 2026.2.0 are potentially exposed. Risk depends on whether untrusted or broad user populations have authenticated access and whether collections contain sensitive headers, tokens, or API data.

Exploitation context

Sources do not report active exploitation, and the CVE is not marked KEV. Exploitation requires authentication and a valid collection ID. If collection identifiers are exposed through logs, sharing workflows, URLs, or prior access, the confidentiality impact could be significant.

Researcher notes

The advisory states the missing ownership check affected `userCollection`, while other operations in the resolver had authorization checks. Evidence supports authenticated IDOR with high confidentiality impact. No public source in the bundle confirms exploit activity or additional affected products.

Mitigation direction

  • Upgrade Hoppscotch to version 2026.2.0 or later.
  • Review vendor advisory and release notes for deployment-specific guidance.
  • Rotate secrets stored in exposed or sensitive Hoppscotch collections.
  • Limit Hoppscotch access to trusted users until patched.

Validation and detection

  • Inventory Hoppscotch instances and confirm running version.
  • Identify whether any instance is below 2026.2.0.
  • Review collection contents for tokens, headers, or credentials.
  • Check access logs for unusual authenticated collection access patterns.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · medium confidence lookup

CWE-862: 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 lookup
cve · low confidence lookup

CVE-2026-28217 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2026-28217Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
hoppscotchhoppscotch< 2026.2.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.