CVE-2026-48558
SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification
Description
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.
In plain language
AI Act nowSimpleHelp (RMM) versions 5.5.15 and earlier (and 6.0 pre-releases) can be tricked into treating fake login tokens as real, letting an attacker get fully logged-in technician access—so yes, a typical small business using SimpleHelp should act now.
CVE-2026-48558 is an authentication bypass in SimpleHelp’s OIDC login flow where identity tokens are accepted without verifying their JWT signature, enabling remote unauthenticated attackers to forge tokens and obtain fully authenticated technician sessions (and in some cases bypass MFA).
What to do now
- Check your installed SimpleHelp version and confirm whether you are running SimpleHelp 5.5.15 or earlier, or a 6.0 pre-release.
- If you are on an affected version, plan an immediate upgrade to the fixed release (SimpleHelp fixed in 5.5.16, or 6.0 RC2).
- After upgrading, verify your OIDC login configuration still functions normally for technicians and that unauthorized login attempts are no longer possible.
- If upgrading right away is blocked, restrict network access to SimpleHelp (only allow trusted admin networks/IPs) and review for signs of compromise while you prepare the upgrade.
CVSS Vector Breakdown
AV:NAttack VectorAC:LAttack ComplexityPR:NPrivileges RequiredUI:NUser InteractionS:CScopeC:HConfidentialityI:HIntegrityA:HAvailabilityWeaknesses
Affected Products
Exploitability
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.
Attack Graph
Click technique nodes for MITRE ATT&CK details · drag to pan · Ctrl/⌘ + scroll to zoom, or go fullscreen.
MITRE ATT&CK
1 techniqueReferences
Unlock Complete Vulnerability Intelligence
Get the full picture for CVE-2026-48558 and every CVE in our database. Create a free account — no credit card required.
Create Free Account