Skip to content
Actively exploitedCVSS 10.0 · CRITICAL

CVE-2026-48558SimpleHelp Authentication Bypass Vulnerability

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

View on NVD

Analysis

Las versiones 5.5.15 y anteriores de SimpleHelp permiten que atacantes remotos no autenticados eviten el proceso de inicio de sesión mediante el envío de tokens OIDC falsificados sin verificación de firma. Esta vulnerabilidad otorga acceso completo con privilegios de técnico y puede saltarse la autenticación de dos factores, comprometiendo totalmente la infraestructura de soporte remoto.

Relevant roles

BackendCyberSecurityWindowsLinuxCloud

Severity

Score: 10.0(CRITICAL)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
AV: NETWORK
AC: LOW
PR: NONE
UI: NONE
S: CHANGED
C: HIGH
I: HIGH
A: HIGH
Weakness (CWE): CWE-347

CISA KEV

Added to KEV: 2026-06-29
Federal patch deadline: 2026-07-02
Known ransomware use: Unknown
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.

EPSS

Probability of exploitation (next 30 days): 0.0116 (1.2%)
Percentile: 63.4%
EPSS: 2026-07-13

Affects

simple-help:simplehelp

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

Published: 6/12/2026, 6:16:35 PM
Last modified: 6/30/2026, 1:03:11 PM

References

HomeEventsBlogResourcesCoursesTeam