CVE-2026-44478: Hoppscotch Backend information disclosure in onboarding config

CVE-2026-44478 · Severity: high · CVSS 7.5 · Published 2026-05-13

Hoppscotch is an open-source platform used by developers to build and test APIs. A security flaw in self-hosted versions allows unauthenticated attackers to download sensitive infrastructure secrets, such as OAuth credentials and email server passwords, in plain text. This occurs when the system is configured using environment variables, leaving a recovery token empty and accessible to anyone on the network.

Technologies: Hoppscotch Backend (Self-Hosted). Vendors: Hoppscotch.

Quick answers

Is CVE-2026-44478 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-44478 being exploited in the wild.
How severe is CVE-2026-44478?
High severity, with a CVSS score of 7.5, published 13 May 2026.
Which products and versions are affected?
Hoppscotch Backend (Self-Hosted) >= 2025.7.0, < 2026.4.0.
Is there a fix for CVE-2026-44478?
A patch was published on 2026-04-30: Fixed in version 2026.4.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-44478 attacked?
It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-44478?
Check whether you run Hoppscotch Backend (Self-Hosted) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The vulnerability exists in the GET /v1/onboarding/config endpoint of the Hoppscotch backend. When an instance is configured via environment variables rather than the onboarding wizard, the ONBOARDING_RECOVERY_TOKEN in the database is initialized as an empty string. The NestJS @Query('token') decorator parses a request with an empty token parameter (e.g., ?token=) as an empty string, causing a comparison check in infra-config.service.ts to evaluate as true. Because the endpoint lacks authentication guards, any network-reachable attacker can bypass the token check to retrieve sensitive configuration data, including OAuth client secrets and SMTP credentials. This issue was addressed in version 2026.4.0.

Affected products

  • Hoppscotch Hoppscotch Backend (Self-Hosted) >= 2025.7.0, < 2026.4.0

Timeline

  • 2026-04-30: advisory: GitHub Security Advisory published
  • 2026-05-13: disclosed: CVE published to NVD
  • 2026-04-30: patched: Fixed in version 2026.4.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.