CVE-2026-25555
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenBullet2 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenBullet2 through 0.3.2 has an authentication bypass in its API key middleware where supplying an empty X-Api-Key header matches against a default empty AdminApiKey string, allowing unauthenticated attackers to gain admin access to the console and all API endpoints.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify OpenBullet2 installation and versionLocate the OpenBullet2 web application files or running process. Check the assembly version, DLL metadata, or application's reported version information. Compare against the affected range: versions 0.3.2 and prior.Affected if OpenBullet2 version 0.3.2 or any prior version is installed.
-
Locate application configuration fileFind the configuration file where AdminApiKey is stored (typically appsettings.json or a similar configuration source in the application root or config directory).Affected if The configuration file exists and contains an AdminApiKey setting.
-
Inspect AdminApiKey valueOpen the configuration file and examine the AdminApiKey setting. Determine if the value is empty, null, or unset versus a non-empty string.Affected if AdminApiKey is set to an empty string, null, or is not defined, leaving the default empty value in place.
-
Test API authentication with empty X-Api-KeySend an HTTP request to any protected API endpoint (such as /api/config or /admin) with the header X-Api-Key set to an empty value (X-Api-Key: ). Observe the response.Affected if The request is accepted and returns admin-level data or successful authentication, indicating the bypass is functional.
-
Verify admin console accessAccess the web-based admin console (typically at /admin or similar path) using a browser or HTTP client with no X-Api-Key header or an empty X-Api-Key header.Affected if The admin console is accessible without providing a valid API key, confirming the authentication bypass.
If OpenBullet2 version 0.3.2 or prior is running with an empty or unset AdminApiKey configuration, the environment is vulnerable to complete authentication bypass.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to a patched version and ensure the AdminApiKey is set to a strong, non-empty value rather than defaulting to an empty string.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25555 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25555 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data