# CVE-2026-48558: SimpleHelp Authentication Bypass

> Remote attackers can bypass authentication in SimpleHelp by submitting forged OIDC tokens when OIDC is configured, gaining technician access.

- **Severity:** Critical 9.5 (`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`)
- **Exploited in the wild:** Yes, since 29 Jun 2026 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Jun 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-m93h-gjv2-fmq2

## What is CVE-2026-48558?

CVE-2026-48558 is a critical authentication bypass vulnerability in SimpleHelp, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-48558?

It affects 1 product.


Products: Simple-Help Simplehelp.

## How do I fix CVE-2026-48558?

No fix has been published for CVE-2026-48558 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Jul 2026.

## Is CVE-2026-48558 being exploited?

Yes. Attackers have exploited CVE-2026-48558 in the wild since at least 29 Jun 2026.

Public exploit code:

- SimpleHelp OIDC Authentication Bypass PoC (github_poc): https://github.com/J4ck3LSyN-Gen2/CVE-2026-48558
- SimpleHelp OIDC Authentication Bypass Remote Code Execution (metasploit)
- SimpleHelp <=5.5.15 - OIDC JWT Authentication Bypass (nuclei): http/cves/2026/CVE-2026-48558.yaml

## Other vulnerabilities in SimpleHelp

- [CVE-2024-57726](https://insights.sbomify.com/CVE-2024-57726/): SimpleHelp Missing Authorization (critical 9.9, exploited in the wild)
- [CVE-2024-57727](https://insights.sbomify.com/CVE-2024-57727/): SimpleHelp Path Traversal (critical 9.1, exploited in the wild)
- [CVE-2024-57728](https://insights.sbomify.com/CVE-2024-57728/): SimpleHelp Path Traversal (high 7.2, exploited in the wild)
- [CVE-2025-36727](https://insights.sbomify.com/CVE-2025-36727/): SimpleHelp Inclusion of functionality from untrusted control sphere (high 8.3)
- [CVE-2025-36728](https://insights.sbomify.com/CVE-2025-36728/): SimpleHelp Cross Site Request Forgery (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-48558 and fix it if it is affected.

What it is: CVE-2026-48558 is a critical authentication bypass vulnerability in SimpleHelp, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2026-48558 in the wild since at least 29 Jun 2026.

Affected product: SimpleHelp. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-48558/ (Markdown: https://insights.sbomify.com/CVE-2026-48558/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-48558
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-48558
- OSV: https://osv.dev/vulnerability/CVE-2026-48558

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-48558/
Summaries are generated and may contain mistakes; the official description above is the record.