Quick answers
- Is CVE-2026-25555 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-25555 being exploited in the wild.
- How severe is CVE-2026-25555?
- Critical severity, with a CVSS score of 9.8, published 8 June 2026.
- Which products and versions are affected?
- OpenBullet2 through 0.3.2.
- Is there a fix for CVE-2026-25555?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-25555 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-25555?
- Check whether you run OpenBullet2 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An authentication bypass vulnerability exists in the API key authentication middleware of OpenBullet2 versions up to and including 0.3.2. The root cause is a logic error where the middleware compares a user-supplied 'X-Api-Key' header against a default 'AdminApiKey' string that may be empty. By providing an empty value in the 'X-Api-Key' header, a remote, unauthenticated attacker can satisfy the authentication condition. Successful exploitation grants full access to the administrative console and all API endpoints, allowing for complete system takeover.
Affected products
- OpenBullet2 OpenBullet2 through 0.3.2
Timeline
- 2026-06-08: advisory: NVD and VulnCheck published the advisory