CVE-2026-44478
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. The fix for CVE-2026-28215 in version 2026.2.0 addresses the unauthenticated POST /v1/onboarding/config endpoint by checking onboardingCompleted and canReRunOnboarding before allowing config overwrites. However, GET /v1/onboarding/config still leaks all infrastructure secrets in plaintext to unauthenticated users when the ONBOARDING_RECOVERY_TOKEN stored in the database is an empty string. This vulnerability is fixed in 2026.4.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 · high confidenceIn hoppscotch versions before 2026.4.0, the GET /v1/onboarding/config endpoint returns all infrastructure secrets in plaintext to unauthenticated users when the ONBOARDING_RECOVERY_TOKEN in the database is an empty string, allowing unauthenticated attackers to steal sensitive infrastructure credentials.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 hoppscotch versionCheck the installed version of hoppscotch (typically in package.json, docker image tag, or the application UI footer). Compare it to the affected range: versions before 2026.4.0Affected if The installed version is any version prior to 2026.4.0
-
Verify database connectionConnect to the hoppscotch database and query the configuration table or wherever ONBOARDING_RECOVERY_TOKEN is storedAffected if The ONBOARDING_RECOVERY_TOKEN value in the database is an empty string or null
-
Check endpoint accessibilitySend a GET request to /v1/onboarding/config without providing any authentication credentialsAffected if The endpoint responds without requiring authentication and exposes secret values in the response body
You are affected if running hoppscotch version before 2026.4.0 AND the ONBOARDING_RECOVERY_TOKEN in the database is empty, which allows unauthenticated access to the /v1/onboarding/config endpoint revealing secrets.
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 · scopedUpgrade hoppscotch to version 2026.4.0 or later to remediate this vulnerability.
2026.4.0
- Identify current Hoppscotch installation version by checking the deployed release tag or package.json
- If running a version between 2026.2.0 and 2026.3.x inclusive, plan for upgrade
- Backup the database and configuration files before upgrading
- Upgrade Hoppscotch to version 2026.4.0 or later
- After upgrade, verify the GET /v1/onboarding/config endpoint no longer returns plaintext secrets to unauthenticated users
- Ensure ONBOARDING_RECOVERY_TOKEN is set to a non-empty value in the database configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44478 — 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-44478 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