# CVE-2026-25555: OpenBullet2 0.3.2 Authentication Bypass via X-Api-Key Header

> Unauthenticated attackers can gain admin access to OpenBullet2 by sending an empty X-Api-Key header, bypassing authentication checks.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jun 2026
- **Updated:** 14 Jul 2026
- **Also known as:** GHSA-54jj-4v6g-j34h

## What is CVE-2026-25555?

CVE-2026-25555 is a critical authentication bypass vulnerability in openbullet2, published on 8 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenBullet2 through version 0.3.2 contains an authentication bypass vulnerability in the API key authentication middleware that allows unauthenticated attackers to gain admin access by supplying an empty X-Api-Key header value. Attackers can exploit the middleware's comparison of the supplied header against an empty AdminApiKey default string to access the admin console and all API endpoints without valid credentials.

Weakness: CWE-305 (Authentication Bypass by Primary Weakness)

## Which versions are affected by CVE-2026-25555?


## How do I fix CVE-2026-25555?

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

## Is CVE-2026-25555 being exploited?

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

Public exploit code:

- OpenBullet2 <= 0.3.2 - Authentication Bypass (nuclei): http/cves/2026/CVE-2026-25555.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-25555 and fix it if it is affected.

What it is: CVE-2026-25555 is a critical authentication bypass vulnerability in openbullet2, published on 8 Jun 2026. 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-2026-25555 exists.

Affected product: openbullet2. 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-2026-25555/ (Markdown: https://insights.sbomify.com/CVE-2026-25555/index.md)
```

## Sources

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

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