CVE-2026-34932
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.3.0, there is a stored XSS vulnerability that can lead to CSRF. This issue has been patched in version 2026.3.0.
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 · moderate confidencehoppscotch, an open source API development ecosystem, contains a stored Cross-Site Scripting (XSS) vulnerability prior to version 2026.3.0. The XSS vulnerability can be leveraged to perform Cross-Site Request Forgery (CSRF) attacks against users. This critical vulnerability (CVSS 9.3) has been patched in version 2026.3.0.
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.3.0CVSS 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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/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.
-
Check installed Hoppscotch versionOpen Hoppscotch and navigate to Help > About, or check the application footer for the version number. If using a self-hosted instance, check the package.json or Docker image tag.Affected if The displayed version is any version prior to 2026.3.0 (e.g., 2026.2.0, 2025.x.x, etc.)
-
Verify self-hosted instance versionFor self-hosted deployments, examine the package.json file in the application root directory, or query the API endpoint that returns version information if available.Affected if The version field in package.json or the API response shows a version lower than 2026.3.0
-
Confirm deployment dateCheck when the Hoppscotch instance was last deployed or updated. Review deployment records, CI/CD logs, or container image timestamps.Affected if The deployment occurred before the 2026.3.0 release date and has not been updated since.
If the installed Hoppscotch version is any release prior to 2026.3.0, the environment is affected by this stored XSS vulnerability.
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.3.0
Upgrade hoppscotch to version 2026.3.0 or later to remediate this vulnerability.
2026.3.0
- Upgrade Hoppscotch to version 2026.3.0 or later by obtaining the updated release from the official Hoppscotch repository or distribution channel appropriate to your deployment method (e.g., npm, Docker, or direct download)
- After upgrading, verify the application functions correctly
- Confirm the XSS vulnerability is resolved by testing that user-supplied input in affected areas is properly sanitized or escaped
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34932 — 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-34932 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