Skip to content
Server Security Center
KEVcritical10.0

CVE-2026-48558: SimpleHelp Authentication Bypass

SimpleHelp · listed in the CISA catalog of actively exploited vulnerabilities since 2026-06-29.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
80%
higher than 99.6% of all CVEs
Added to CISA KEV
2026-06-29
US federal due date 2026-07-02
Automatable (CISA SSVC)
yes
technical impact: total

CVE-2026-48558 explained

CVE-2026-48558 is a critical authentication bypass in SimpleHelp server software. When OIDC authentication is configured, identity tokens submitted at login are accepted without checking their cryptographic signature. A remote attacker can forge a token and get a fully authenticated technician session. CISA lists the flaw as known to be exploited.

Impact

A remote, unauthenticated attacker can submit a forged identity token and obtain a fully authenticated technician session. In some configurations this may also bypass multi-factor authentication. No user interaction is required. Only systems with OIDC authentication configured are vulnerable. CISA rates the flaw as automatable, with total technical impact, so attackers can exploit it at scale and gain full control of the affected component. Attackers are known to use this vulnerability.

Who is affected

The CVE record lists SimpleHelp versions ≥ 5.5.0, < 5.5.16 and ≥ 6.0, < 6.0 RC2 as affected. The description also names version 5.5.15 and prior and 6.0 pre-release versions. The CVE record names no fixed version in its fixed-version data. Check the vendor advisory to confirm which release contains the fix for your branch.

Written with AI from the data on this page and checked against it automatically.

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

CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. 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.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • SimpleHelp
    Affected
    • ≥ 5.5.0, < 5.5.16
    • ≥ 6.0, < 6.0 RC2
    Fixed in
    not stated

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: simple-help.com/security/simplehelp-security-update-2026-05
  • CISA's deadline for US federal agencies: 2026-07-02 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Identify all SimpleHelp servers and check whether OIDC authentication is configured.
  2. Follow the SimpleHelp vendor advisory and update to the release it names as fixed for your branch.
  3. Apply the vendor's mitigations, as CISA requires, if you cannot update right away.
  4. Restrict network access to SimpleHelp servers and avoid exposing them directly to the internet where possible.
  5. Review technician sessions and logins for signs of compromise, following CISA's forensics triage requirements.
  6. Discontinue use of the product if mitigations are unavailable, as CISA's required action states.

The CVE record names no fixed version. Follow the SimpleHelp vendor advisory for the fixed release and any mitigations. CISA requires applying mitigations per vendor instructions and following BOD 26-04 guidance, or discontinuing use if mitigations are unavailable. Until then, limit network exposure of SimpleHelp servers and check for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-347 Improper Verification of Cryptographic Signature

Questions about CVE-2026-48558

Are all SimpleHelp servers vulnerable?
Only servers in an affected version range with OIDC authentication configured are vulnerable, according to the description. Affected ranges are ≥ 5.5.0, < 5.5.16 and ≥ 6.0, < 6.0 RC2.
Is this vulnerability being exploited?
Yes. CISA added CVE-2026-48558 to its Known Exploited Vulnerabilities catalog on 2026-06-29, with a US federal due date of 2026-07-02. Whether it is used in ransomware campaigns is unknown.
Can multi-factor authentication protect us?
Not reliably. The description states that in some configurations the flaw may also allow bypass of multi-factor authentication.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.