Critical CVE-2026-48558 Vulnerability in SimpleHelp Allows Unauthorized Privileged Account Creation via OIDC Authentication Bypass

Critical CVE-2026-48558 Vulnerability in SimpleHelp Allows Unauthorized Privileged Account Creation via OIDC Authentication Bypass

Executive Summary

A critical vulnerability in SimpleHelp remote support software, tracked as CVE-2026-48558, has been identified, allowing unauthenticated attackers to create rogue privileged technician accounts on servers configured with OpenID Connect (OIDC) authentication. This flaw enables adversaries to bypass multi-factor authentication (MFA) and gain full administrative access to managed endpoints, presenting a severe risk of lateral movement, data exfiltration, and further compromise within enterprise environments. The vulnerability is trivial to exploit under certain configurations and is particularly attractive to threat actors targeting remote management and monitoring (RMM) tools. While there are currently no confirmed reports of exploitation in the wild, the exposure of thousands of SimpleHelp servers on the public internet and the history of RMM tools being targeted by ransomware and advanced persistent threat (APT) groups make this a high-priority issue for all organizations utilizing SimpleHelp.

Technical Information

CVE-2026-48558 is an authentication bypass and privilege escalation vulnerability affecting SimpleHelp versions up to and including 5.5.15, as well as all 6.0 pre-release versions. The vulnerability is rooted in improper validation of identity assertions from an OIDC identity provider (IdP). When OIDC authentication is enabled—either via generic OIDC or Azure AD OIDC—an unauthenticated attacker can craft a request to create and authenticate as a new "Technician" user. This account, by default, is granted privileged access, including the ability to remotely control endpoints and execute scripts.

The exploitation prerequisites are as follows: OIDC authentication must be enabled, at least one Technician Group must be associated with the OIDC provider, and the group must have "Allow group authenticated logins" enabled. Even if MFA is enforced, the attacker can bypass it by self-registering an MFA method on first login, effectively nullifying this security control.

The attack vector is remote and unauthenticated, meaning that any internet-exposed SimpleHelp server with the vulnerable configuration is at risk. The vulnerability allows for the creation of rogue privileged technician accounts, which can be used to gain full access to managed endpoints, perform remote control, execute arbitrary scripts, and potentially move laterally within the internal network. The impact is severe, as it undermines the core trust model of remote support infrastructure and can lead to complete compromise of enterprise assets.

Shodan scans have revealed approximately 14,000 SimpleHelp servers exposed to the public internet, with about 7.2% configured to use OIDC authentication. This broad exposure, combined with the trivial nature of the exploit, significantly elevates the risk profile for organizations using SimpleHelp.

Exploitation in the Wild

As of June 2026, there have been no confirmed reports of exploitation of CVE-2026-48558 in the wild, according to both SimpleHelp and security researchers at Horizon3.ai. However, the vulnerability is being actively discussed in the security community, and proof-of-concept details have been published that lower the barrier for exploitation. The history of RMM tools being targeted by ransomware operators and APT groups, combined with the ease of exploitation, suggests that widespread exploitation is likely if organizations do not apply the available patches.

Shodan data indicates that thousands of SimpleHelp servers are internet-facing, and a significant subset are configured with OIDC authentication, making them directly vulnerable. The attractiveness of RMM tools as a target for threat actors—due to their privileged access and central role in IT operations—means that this vulnerability is likely to be weaponized quickly.

APT Groups using this vulnerability

No specific APT group has been publicly linked to exploitation of CVE-2026-48558 as of June 2026. However, ransomware operators and financially motivated groups such as FIN6 and Wizard Spider/Conti have a documented history of targeting RMM software for initial access and lateral movement. The tactics, techniques, and procedures (TTPs) associated with this vulnerability map to several MITRE ATT&CK techniques, including Valid Accounts (T1078), Exploitation for Privilege Escalation (T1068), Remote Services (T1021), and Create Account (T1136). Given the high value of RMM tools in enterprise environments, it is highly probable that both opportunistic and targeted threat actors will seek to exploit this vulnerability.

Affected Product Versions

The following SimpleHelp product versions are affected by CVE-2026-48558: all versions up to and including 5.5.15, and all 6.0 pre-release versions. The vulnerability is remediated in versions 5.5.16 and 6.0RC2, both released on June 9, 2026. Organizations running any version prior to these releases are at risk and should prioritize upgrading immediately.

Other related vulnerabilities disclosed by Horizon3.ai include CVE-2024-57726 (privilege escalation from technician to admin), CVE-2024-57727 (path traversal and arbitrary file download), and CVE-2024-57728 (arbitrary file upload leading to remote code execution as admin). These vulnerabilities affect earlier versions and should be addressed as part of a comprehensive patching strategy.

Workaround and Mitigation

The primary mitigation for CVE-2026-48558 is to upgrade SimpleHelp to version 5.5.16 or 6.0RC2, which contain the necessary patches. If immediate upgrade is not possible, organizations should restrict technician login sources using IP-based allowlists via the Administration → Login Security settings. Additionally, all technician accounts and recent logins should be audited for unauthorized access, and server logs should be reviewed for suspicious registration or configuration activity.

Detection strategies include monitoring for the creation of new technician accounts, especially those with unfamiliar naming or email conventions, and reviewing logs for anomalous remote access from unexpected IP addresses. Example log entries indicating compromise may include messages such as "Registering technician login for rapidresponse-4b611bdd@horizon3.ai / (Technicians) Configuration save requested (Forged Attacker - rapidresponse-4b611bdd@horizon3.ai [(Technicians)] [New Anon])".

Organizations should also review and patch for the related vulnerabilities CVE-2024-57726, CVE-2024-57727, and CVE-2024-57728 to ensure comprehensive protection.

References

Rescana is here for you

At Rescana, we understand the critical importance of securing your third-party and remote management infrastructure. Our TPRM platform provides continuous monitoring, automated risk assessment, and actionable intelligence to help you identify and mitigate vulnerabilities across your digital supply chain. We are committed to supporting your organization in navigating the evolving threat landscape and ensuring the resilience of your operations. If you have any questions or require further assistance regarding this advisory or your broader cybersecurity posture, please contact us at ops@rescana.com.