WebSocket endpoint /api/v2/ws/logs reachable without authentication even when --auth is enabled

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.8 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:P · score source

EPSS

• CVE-2025-54376: 0.71% estimated exploitation activity in the next 30 days; percentile 53.61 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary Hoverfly’s admin WebSocket endpoint /api/v2/ws/logs is not protected by the same authentication middleware that guards the REST admin API. Consequently, an unauthenticated remote attacker can: - Stream real-time application logs (information disclosure). - Gain insight into internal file paths, request/response bodies, and other potentially sensitive data emitted in logs. PoC 1. Start Hoverfly with authentication enabled: 2. Confirm REST API requires credentials: 3. Connect to the WebSocket endpoint without credentials: Impact Authentication bypass; an attacker receives full application logs, including proxied request/response bodies, tokens, file paths, etc.

Published by the source

10 Sep 2025, 20:43 UTC

Last modified by the source

24 Sep 2025, 21:14 UTC

Source last checked

26 Oct 2026, 15:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-jxmr-2h4q-rhxp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-54376

Advisory: WebSocket endpoint `/api/v2/ws/logs` reachable without authentication even when --auth is enabled
IDs: CVE-2025-54376, GHSA-jxmr-2h4q-rhxp
Record: https://patchnext.com/advisories/cve-2025-54376 (revision 1, source checked 26 Oct 2026, 15:10 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/SpectoLabs/hoverfly 1.12.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/SpectoLabs/hoverfly: affected < 1.12.0; fixed in 1.12.0

## Suggested inspection (read-only)
- Go github.com/SpectoLabs/hoverfly: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/SpectoLabs/hoverfly.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-jxmr-2h4q-rhxp (GitHub-reviewed advisory GHSA-jxmr-2h4q-rhxp lists affected ranges: Go github.com/SpectoLabs/hoverfly >=0 <1.12.0)

Commands are suggestions: review each one before running it.