🛡️ CVE-2026-27465 — fleet
Description
Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users
Summary
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.
Impact
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.
Patches
- v4.80.1
Workarounds
If an immediate upgrade is not possible, administrators should remove the Google Calendar integration from Fleet and rotate the affected Google service account credentials.
For more information
If there are any questions or comments about this advisory:
Email Fleet at [security@fleetdm.com](mailto:[email protected])
Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)
Credits
Fleet thanks @secfox-ai for responsibly reporting this issue.
How this vulnerability can be exploited
This issue can be reached over the network, attack complexity is low, an attacker needs low-level privileges on the target. No user interaction is required. The scope is unchanged, so the impact stays within the vulnerable component. Rated impact: confidentiality high, integrity none, availability none.
Affected software
CVE-2026-27465 is recorded against 2 packages.
- fleet (fixed in 4.80.1)
- github.com/fleetdm/fleet/v4
Timeline and source
Published on 26 February 2026 and last revised on 17 June 2026. No public exploit is currently recorded for this entry. Record sourced from NVD.
References
Details
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Affected Packages
| Software | From version | Fixed in |
|---|---|---|
| fleet | — | 4.80.1 |
| github.com/fleetdm/fleet/v4 | — | — |
References
Similar Threats
- High CVE-2026-23998
- Medium CVE-2026-24000
- High CVE-2026-24899
- High CVE-2026-26062
- Critical CVE-2026-26191
More CVE 2026 advisories
Browse all of CVE 2026 in the advisory index.
Site Security Check
Is fleet part of your stack?
CVE-2026-27465 is rated CVSS 8.0 High. BotEraser scans your installation against known CVE records and tells you whether this vulnerability applies to the versions you actually run.
Scan My Site Free →No credit card required · Results in minutes
ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.