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.

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

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. 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

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.