# CVE-2025-54376: Hoverfly's WebSocket endpoint `/api/v2/ws/logs` reachable without authentication even when --auth is enabled.

> Unauthenticated attackers can access the WebSocket log endpoint to view sensitive application logs and internal data when authentication is enabled.

- **Severity:** High 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Sep 2025
- **Updated:** 10 Sep 2025
- **Also known as:** GHSA-jxmr-2h4q-rhxp, GO-2025-3945

## What is CVE-2025-54376?

CVE-2025-54376 is a high-severity missing authorization vulnerability in SpectoLabs hoverfly, published on 10 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hoverfly is an open source API simulation tool. In versions 1.11.3 and prior, 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) and/or gain insight into internal file paths, request/response bodies, and other potentially sensitive data emitted in logs. Version 1.12.0 contains a fix for the issue.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File), CWE-287 (Improper Authentication), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-54376?

3 open source packages ship an affected version, including github.com/SpectoLabs/hoverfly. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/SpectoLabs/hoverfly` | Go | All versions | 1.12.0 |
| `github.com/SpectoLabs/hoverfly` | Go | All versions | 1.12.0 |
| `github.com/SpectoLabs/hoverfly` | Go | All versions | 1.12.0 |

Products: Hoverfly Hoverfly.

## How do I fix CVE-2025-54376?

Upgrade github.com/SpectoLabs/hoverfly to 1.12.0 or later.

## Is CVE-2025-54376 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54376 exists.

## Other vulnerabilities in SpectoLabs hoverfly

- [CVE-2025-54123](https://insights.sbomify.com/CVE-2025-54123/): Hoverfly is vulnerable to Remote Code Execution through an insecure middleware implementation (critical 9.8)
- [CVE-2024-45388](https://insights.sbomify.com/CVE-2024-45388/): Arbitrary file read in the `/api/v2/simulation` endpoint in hoverfly (`GHSL-2023-274`) (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-54376 and fix it if it is affected.

What it is: CVE-2025-54376 is a high-severity missing authorization vulnerability in SpectoLabs hoverfly, published on 10 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-54376 exists.

Affected packages and fixed versions:
- github.com/SpectoLabs/hoverfly (Go): affected all versions; fixed in 1.12.0
- github.com/SpectoLabs/hoverfly (Go): affected all versions; fixed in 1.12.0
- github.com/SpectoLabs/hoverfly (Go): affected all versions; fixed in 1.12.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-54376/ (Markdown: https://insights.sbomify.com/CVE-2025-54376/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-54376
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-54376
- OSV: https://osv.dev/vulnerability/CVE-2025-54376

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-54376/
Summaries are generated and may contain mistakes; the official description above is the record.