CVE-2026-48558
SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification
- Added
- Jun 29, 2026
- Fix due
- Jul 2, 2026
- Ransomware
- Not known
- Published
- Jun 12, 2026
- Updated
- Oct 7, 2026
- First covered
- Jun 29, 2026
- Latest story
- 4 months ago
Summary
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.
CWE-347Improper Verification of Cryptographic Signature
Attack profile
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCISA required action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Affected products
- SimpleHelp5.5.0 to before 5.5.166.0 to before 6.0 RC2