SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification
Exploited in the wild, in CISA KEV since 29 Jun 2026 (due 2 Jul 2026), with 3 public exploits. Fixed in SimpleHelp 5.5.16 and SimpleHelp 6.0 RC2.
SimpleHelp versions 5.5.15 and prior and 6.0 pre-release versions contain an authentication bypass vulnerability in the OIDC authentication flow. When OIDC authentication is configured, identity tokens submitted during login are accepted without verifying their cryptographic signature. In a vulnerable configuration, a remote, unauthenticated attacker can submit a forged token containing arbitrary identity claims to obtain a fully authenticated technician session. In some configurations, this may also allow bypass of multi-factor authentication. No user interaction is required.
Briefing
Written from the sources below · deepseek-v4.1-flash
SimpleHelp 5.5.15 and prior and 6.0 pre-release versions accept OIDC identity tokens without verifying their cryptographic signature. A remote, unauthenticated attacker can submit a forged token with arbitrary claims to gain a fully authenticated technician session, possibly bypassing MFA.
Why it mattersCVSS 10.0, listed in CISA KEV with confirmed exploitation, public exploit material, and 80% EPSS, so exposed OIDC-enabled instances are at high risk.
ActionUpgrade SimpleHelp to a version later than 5.5.15 or the fixed 6.0 release; apply vendor mitigation if upgrade is not possible.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| SimpleHelp | SimpleHelp | >=5.5.0 <5.5.16, >=6.0 <6.0 RC2 | 5.5.16, 6.0 RC2 |
Exploit evidence
3 public sources
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in SimpleHelp, strongest first
Embed
A live severity badge for an advisory, README or ticket