# CVE-2025-8415: Cryostat: authentication bypass if network policies are disabled

> Unauthenticated attackers can access the Cryostat HTTP API if network policies are disabled, potentially compromising the environment.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Aug 2025
- **Updated:** 23 Dec 2025
- **Also known as:** GHSA-h2p8-37qr-qfr9

## What is CVE-2025-8415?

CVE-2025-8415 is a medium-severity authentication bypass vulnerability in Cryostat, published on 20 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability was found in the Cryostat HTTP API. Cryostat's HTTP API binds to all network interfaces, allowing possible external visibility and access to the API port if Network Policies are disabled, allowing an unauthenticated, malicious attacker to jeopardize the environment.

Weakness: CWE-289 (Authentication Bypass by Alternate Name)

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


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

No fix has been published for CVE-2025-8415 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-8415 being exploited?

There is no known exploitation of CVE-2025-8415 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-8415 is a medium-severity authentication bypass vulnerability in Cryostat, published on 20 Aug 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-8415 in the wild and no public exploit code.

Affected product: Cryostat. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-8415/ (Markdown: https://insights.sbomify.com/CVE-2025-8415/index.md)
```

## Sources

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

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