[CVE-2026-48558] SimpleHelp SimpleHelp — SimpleHelp Authentication Bypass Vulnerability

What happened?

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

Key details

• Linux kernel ebtables SNAT target has an out-of-bounds write flaw.
• ARP sender hardware address rewrite can write into a nonlinear socket-buffer fragment.
• The affected buffer fragment is backed by a splice-imported file page.
• The impacted product may be end-of-life or end-of-service.
• Users should discontinue use or move to a supported version.
• Forensic triage is required under CISA BOD 26-04.

Summarised by SecOraLens from CISA KEV. Always read the original source before acting. How SecOraLens verifies advisories.

What should I do about it?

1. 1Apply the latest security updates and patches to SimpleHelp according to the vendor's instructions
2. 2Ensure compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance
3. 3Follow CISA’s Forensics Triage Requirements for incident response
4. 4Evaluate each asset's internet exposure and adhere to BOD 26-04 patching guidelines
5. 5Consider discontinuing use of the product if mitigations are unavailable
6. 6Monitor authentication logs and network traffic for suspicious activity
7. 7Implement additional security controls, such as multi-factor authentication and identity token validation