# CVE-2026-116199: Snipe-IT authentication bypass in Google SSO callback

Source: https://junglewise.ai/threats/cve-2026-116199-snipe-it-before-8-6-3-contains-an-authentication-bypass-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-25. Updated: 2026-10-25  
License: CC BY 4.0 with a link back

CVE-2026-116199 · Severity: high · CVSS 8.1 · Published 2026-10-25

Snipe-IT is an asset management system used to track company equipment and resources. An attacker can sign in as a deactivated user if that user still has an active Google account and their Snipe-IT username matches their email address. This allows unauthorized access to company data and administrative functions at the permission level the user had before being deactivated.

Technologies: [Grokability Snipe-IT](https://junglewise.ai/threats/technologies/grokability-snipe-it). Vendors: [Grokability](https://junglewise.ai/threats/vendors/grokability).

## Quick answers

**Is CVE-2026-116199 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-116199 being exploited in the wild.

**How severe is CVE-2026-116199?** High severity, with a CVSS score of 8.1, published 25 October 2026.

**Which products and versions are affected?** Grokability Snipe-IT before 8.6.3.

**Is there a fix for CVE-2026-116199?** Yes: fixed in 8.6.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-116199 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-116199?** Check whether you run Grokability Snipe-IT 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.

## How to fix

- Fixed in 8.6.3

## Technical details

The GoogleAuthController::handleGoogleCallback function looks up users by email but fails to check the activated flag before logging them in, unlike all other authentication methods in the application (SAML, LDAP, REMOTE_USER, local password). A deactivated user with a matching email-shaped username and an active Google identity can bypass authentication and regain their original session permissions. The fix adds an activated flag check before calling Auth::login.

## Affected products

- Grokability Snipe-IT before 8.6.3

## Timeline

- 2026-10-08: disclosed
- 2026-10-25: advisory

## References

- [https://github.com/grokability/snipe-it/security/advisories/GHSA-xf36-wx48-5rqp](https://github.com/grokability/snipe-it/security/advisories/GHSA-xf36-wx48-5rqp)
- [https://www.vulncheck.com/advisories/snipe-it-before-8.6.3-authentication-bypass-via-google-sso-callback](https://www.vulncheck.com/advisories/snipe-it-before-8.6.3-authentication-bypass-via-google-sso-callback)

## Related threats

- [Snipe-IT LDAP StartTLS downgrade to cleartext](https://junglewise.ai/threats/cve-2026-116200-snipe-it-before-8-6-3-ignores-the-ldap-start-tls-return-value-in)
- [Snipe-IT missing encryption in API assets endpoint](https://junglewise.ai/threats/cve-2026-116198-snipe-it-before-8-7-0-contains-a-missing-encryption)
- [Snipe-IT server-side request forgery in webhook testing](https://junglewise.ai/threats/cve-2026-114064-snipe-it-before-8-7-0-contains-a-server-side-request-forgery)