Quick answers
- Is CVE-2026-39908 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39908 being exploited in the wild.
- How severe is CVE-2026-39908?
- Medium severity, with a CVSS score of 6.5, published 8 June 2026.
- Which products and versions are affected?
- OpenBullet2 through 0.3.2.
- Is there a fix for CVE-2026-39908?
- 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-39908 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39908?
- 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
A credential disclosure vulnerability exists in OpenBullet2 (up to v0.3.2) when running on Windows. The application fails to properly validate proxy source paths, allowing an attacker with low privileges to input a Universal Naming Convention (UNC) path (e.g., \\attacker-ip\share). When a job is initiated, the application attempts to load proxies from this path via the SMB protocol. This triggers an automatic Windows authentication attempt, sending the NTLMv2 hash of the user account running the OpenBullet2 process to the attacker-controlled server. The captured hash can subsequently be used in NTLM relay attacks or cracked offline to recover the plaintext password.
Affected products
- OpenBullet2 OpenBullet2 through 0.3.2
Timeline
- 2026-06-08: disclosed
- 2026-06-08: advisory