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.
Evidence dossier
CVE-2026-48558
SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification
gen-56ccdaf9Normalized restatement
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.
- State
- PUBLISHED
- Published
- Jun 12, 2026
- Updated
- Jul 14, 2026
- Evidence coverage
- 85%
2026-07-18 · v2026.06.15 · percentile 63.6%
Distinct CVSS assessments remain side by side; none are averaged.
Source comparison
Who said what
SimpleHelp Authentication Bypass via Missing OIDC JWT Signature Verification
SimpleHelp Authentication Bypass Vulnerability
Probability 0.011600000000; percentile 0.635750000000
Applicability
Cited product scope
[{"status": "affected", "version": "5.5.0", "lessThan": "5.5.16", "versionType": "semver"}, {"status": "affected", "version": "6.0", "lessThan": "6.0 RC2", "versionType": "custom"}]unknowncpe:2.3:a:simple-help:simplehelp:*:*:*:*:*:*:*:*; end excluding 5.5.16supportedcpe:2.3:a:simple-help:simplehelp:6.0:pre-release:*:*:*:*:*:*supportedAssessments
CVSS by origin
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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:HCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HLimitations and unknowns
- KEV membership is authoritative for the catalog, not proof of exposure in any environment.
- EPSS is a dated model probability and not an individual-environment prediction.
- Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
- NVD-carried upstream facts remain derivative and are not independent corroboration.
- Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
- NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
- Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
- Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.