Limited ability to spoof SAML authentication with missing audience verification
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA and GitHub. Impact type from CWE-287.
Summary
fleet is an open source device management, built on osquery. Versions prior to 4.9.1 expose a limited ability to spoof SAML authentication with missing audience verification. This impacts deployments using SAML SSO in two specific cases: 1. A malicious or compromised Service Provider (SP) could reuse the SAML response to log into Fleet as a user -- only if the user has an account with the same email in Fleet, _and_ the user signs into the malicious SP via SAML SSO from the same Identity Provider (IdP) configured with Fleet. 2. A user with an account in Fleet could reuse a SAML response intended for another SP to log into Fleet. This is only a concern if the user is blocked from Fleet in the IdP, but continues to have an account in Fleet. If the user is blocked from the IdP entirely, this cannot be exploited. Fleet 4.9.1 resolves this issue. Users unable to upgrade should: Reduce the length of sessions on your IdP to reduce the window for malicious re-use, Limit the amount of SAML Service Providers/Applications used by user accounts with access to Fleet, and When removing access to Fleet in the IdP, delete the Fleet user from Fleet as well.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| fleetdm | fleet | before 4.9.1 | 4.9.1 | Patch available | CNA |
| — | github.com/fleetdm/fleet/v4 (Go) | before 4.9.1 | 4.9.1 | Patch available | GHSA-ch68-7cf4-35vr |
- fleet Vendorfleetdm Affected before 4.9.1 Fixed in 4.9.1 Patch available CNA
- github.com/fleetdm/fleet/v4 (Go) Vendor— Affected before 4.9.1 Fixed in 4.9.1 Patch available GHSA-ch68-7cf4-35vr
Remediation
- Fix · CNA fleet (fleetdm) Fixed in 4.9.1
- Fix · GHSA-ch68-7cf4-35vr github.com/fleetdm/fleet/v4 (Go) Fixed in 4.9.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-23600
- 2026-10-03 Alias added: GHSA-ch68-7cf4-35vr
References
More fleetdm Fleet vulnerabilities
- TI-2026-65639 Fleet before 4.87.0 Authentication Bypass via Device Identifiers CVSS 4.0CRITICAL 9.3
- TI-2026-18942 Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment CVSS 4.0CRITICAL 9.3
- TI-2020-16097 SAML authentication vulnerability in Fleet CVSS 3.1CRITICAL 10.0
- TI-2026-21066 Fleet server may terminate unexpectedly when handling certain gRPC requests CVSS 4.0HIGH 8.7
- TI-2026-21065 Fleet's unbounded request body read allows remote Denial of Service CVSS 4.0HIGH 8.7
- TI-2026-20084 Fleet Windows MDM Azure AD JWT Authentication Bypass CVSS 4.0HIGH 8.2
Sources
- CVE-2022-23600 · CVE Program
- CVE-2022-23600 · NVD
- FIRST EPSS
- GHSA-ch68-7cf4-35vr · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences