CVE-2026-30825
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedhoppscotch is an open source API development ecosystem. Prior to version 2026.2.1, the DELETE /v1/access-tokens/revoke endpoint allows any authenticated user to delete any other user's PAT by providing its ID, with no ownership verification. This issue has been patched in version 2026.2.1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe DELETE /v1/access-tokens/revoke endpoint in hoppscotch suffers from an Insecure Direct Object Reference (IDOR) vulnerability. Any authenticated user can revoke any other user's Personal Access Token (PAT) by providing its ID, as the endpoint only verifies authentication but not token ownership.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.2.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Hoppscotch versionCheck the version displayed in the Hoppscotch application UI (usually in Settings > About) or query the backend API version endpoint if availableAffected if The version is lower than 2026.2.1 (e.g., 2026.2.0, 2026.1.x, etc.)
-
Verify the backend API is reachableConfirm the Hoppscotch backend server is accessible and responding to requestsAffected if The backend API is running and accessible to users
-
Check if authentication is enabled on the revoke endpointSend an authenticated request to DELETE /v1/access-tokens/revoke with any valid token ID to confirm the endpoint accepts authenticated requestsAffected if The endpoint accepts authenticated requests and processes revocation without validating token ownership
-
Confirm users can access other users token IDsDetermine whether users can enumerate or obtain token IDs belonging to other users through API responses or other endpointsAffected if Token IDs of other users are accessible or guessable through the API
You are affected if your Hoppscotch instance version is below 2026.2.1 and the revoke endpoint is accessible to authenticated users without ownership verification.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.2.1
Upgrade to hoppscotch version 2026.2.1 or later, which implements proper ownership verification before allowing token revocation.
2026.2.1
- 1. Identify the current Hoppscotch version currently deployed in your environment
- 2. Back up any critical data such as existing access tokens and user configurations
- 3. Upgrade Hoppscotch to version 2026.2.1 or later, following the official upgrade instructions for your deployment method
- 4. Verify the upgrade was successful by checking the version number
- 5. Test the DELETE /v1/access-tokens/revoke endpoint to confirm it now properly validates token ownership before allowing revocation
- 6. Ensure all users re-authenticate if necessary after the patch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-30825 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-30825 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data