Quick answers
- Is CVE-2026-18639 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-18639 being exploited in the wild.
- How severe is CVE-2026-18639?
- High severity, with a CVSS score of 7.3, published 11 August 2026.
- Which products and versions are affected?
- Velociraptor Velociraptor before 0.77.2.
- Is there a fix for CVE-2026-18639?
- A patch was published on 2026-08-11: Version 0.77.2 released to address this and multiple other CVEs Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-18639 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-18639?
- Check whether anything you run is named in the advisory. 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
The vulnerability is an authentication bypass in Velociraptor's OIDC integration. The root cause is that Velociraptor uses the email claim from the OIDC token as a username without verifying the email address through the "email_verified" claim. Some OIDC providers do not enforce email verification or allow users to change their email claim without validation. An attacker with access to an OIDC IdP can set their email address to match another user's email, allowing them to authenticate as that user. Attack vector is network-based and requires only that the attacker has valid access to the shared OIDC identity provider. The fix is to update Velociraptor to version 0.77.2 or later, which addresses this vulnerability.
Affected products
- Velociraptor Velociraptor before 0.77.2
Timeline
- 2026-08-11: disclosed
- 2026-08-11: patched: Version 0.77.2 released to address this and multiple other CVEs