Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub. Impact type from CWE-201.
Summary
Fleet is open source device management software. In versions prior to 4.80.1, a vulnerability in Fleet’s configuration API could expose Google Calendar service account credentials to authenticated users with low-privilege roles. This may allow unauthorized access to Google Calendar resources associated with the service account. Fleet returns configuration data through an API endpoint that is accessible to authenticated users, including those with the lowest-privilege “Observer” role. In affected versions, Google Calendar service account credentials were not properly obfuscated before being returned. As a result, a low-privilege user could retrieve the service account’s private key material. Depending on how the Google Calendar integration is configured, this could allow unauthorized access to calendar data or other Google Workspace resources associated with the service account. This issue does not allow escalation of privileges within Fleet or access to device management functionality. Version 4.80.1 patches the issue. If an immediate upgrade is not possible, administrators should remove the Google Calendar integration from Fleet and rotate the affected Google service account credentials.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- 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.80.1 | 4.80.1 | Patch available | CNA |
| — | github.com/fleetdm/fleet/v4 (Go) | before 4.80.1 | 4.80.1 | Patch available | GHSA-2v6m-6xw3-6467 |
- fleet Vendorfleetdm Affected before 4.80.1 Fixed in 4.80.1 Patch available CNA
- github.com/fleetdm/fleet/v4 (Go) Vendor— Affected before 4.80.1 Fixed in 4.80.1 Patch available GHSA-2v6m-6xw3-6467
Remediation
- Fix · CNA fleet (fleetdm) Fixed in 4.80.1
- Fix · GHSA-2v6m-6xw3-6467 github.com/fleetdm/fleet/v4 (Go) Fixed in 4.80.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2026-27465
- 2026-10-03 Alias added: GHSA-2v6m-6xw3-6467
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-2026-27465 · CVE Program
- CVE-2026-27465 · NVD
- FIRST EPSS
- GHSA-2v6m-6xw3-6467 · 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