CVE-2026-48558: SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification
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.
Security readout for executives and security teams
Plain-English summary
SimpleHelp can accept forged login identity tokens when OIDC login is enabled. A remote attacker could become an authenticated technician without credentials or user interaction, and some setups may also bypass MFA. Because CISA lists this CVE in KEV, treat exposed OIDC-enabled SimpleHelp systems as urgent.
Executive priority
Immediate priority. This affects remote support infrastructure, can create fully authenticated technician access, and is listed in CISA KEV. Treat it as a same-day exposure review and remediation task for any OIDC-enabled SimpleHelp deployment.
Technical view
CVE-2026-48558 is a CWE-347 signature verification failure in SimpleHelp's OIDC flow. Versions 5.5.15 and prior plus 6.0 pre-release builds may accept identity tokens without validating the JWT cryptographic signature, allowing arbitrary identity claims and fully authenticated technician sessions. CVSS is 10.0 with network, unauthenticated, no-user-interaction exploitation characteristics.
Likely exposure
Exposure is limited by the sources to SimpleHelp deployments running affected versions with OIDC authentication configured. Internet-facing support portals and environments where technician access has broad administrative reach carry the highest business risk. Evidence is incomplete for non-OIDC configurations.
Exploitation context
Active exploitation is supported by CISA KEV inclusion. Horizon3 is cited for technical description and exploit-related indicators, and Blackpoint is cited as third-party intrusion-chain reporting. The provided bundle does not include full forensic detail, attacker prevalence, or exact fixed-version information.
Researcher notes
Do not assume all SimpleHelp instances are vulnerable; the described precondition is OIDC authentication. The bundle does not provide exact fixed builds or complete IOCs, so validate against the vendor advisory, release notes, CISA KEV entry, and Horizon3 details before closing exposure.
Mitigation direction
Follow SimpleHelp's May 2026 security update and release notes for the vendor-supported fix.
Prioritize affected OIDC-enabled SimpleHelp servers, especially internet-facing instances.
Restrict external access to SimpleHelp until vendor remediation is applied.
Review whether OIDC is required and align temporary changes with vendor guidance.
Hunt for suspicious technician logins and unexpected identity claims.
Validation and detection
Inventory SimpleHelp versions and identify any 5.5.15-and-prior or 6.0 pre-release systems.
Confirm whether OIDC authentication is configured on each SimpleHelp deployment.
Check whether the instance is internet-facing or reachable from untrusted networks.
Review authentication logs for unexpected technician sessions or identity-provider mismatches.
Confirm remediation status against SimpleHelp's security update and release notes.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-347: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
Exploitation: activeAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-347 · source CWE mapping
Improper Verification of Cryptographic Signature
Improper Verification of Cryptographic Signature represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.