← back
CVE-2026-48558criticalobserved exploitationCWE-347

SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification

75Vexday Risk Score

Prioritize patching. It exploitation observed by VulnCheck and has a public proof of concept.

ssvc Actcvss 9.5epss 11%
from disclosure to weapon20 days
Published on NVDJun 12
1st PoC+20d
VulnCheck+17d
exploitation probability
11%top 4% of all CVEs
observed exploitation
yesVulnCheck
3 public exploit(s)
Action required by CISAfederal deadline: 2026-07-02

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.

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.
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Affected products
SimpleHelp · SimpleHelp
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.