Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-27465: 0.27% estimated exploitation activity in the next 30 days; percentile 19.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

26 Feb 2026, 19:53 UTC

Last modified by the source

10 Mar 2026, 18:22 UTC

Source last checked

26 Oct 2026, 15:15 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-2v6m-6xw3-6467

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-27465

Advisory: Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users
IDs: CVE-2026-27465, GHSA-2v6m-6xw3-6467
Record: https://patchnext.com/advisories/cve-2026-27465 (revision 1, source checked 26 Oct 2026, 15:15 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/fleetdm/fleet/v4 4.80.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/fleetdm/fleet/v4: affected < 4.80.1; fixed in 4.80.1

## Suggested inspection (read-only)
- Go github.com/fleetdm/fleet/v4: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/fleetdm/fleet/v4.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-2v6m-6xw3-6467 (GitHub-reviewed advisory GHSA-2v6m-6xw3-6467 lists affected ranges: Go github.com/fleetdm/fleet/v4 >=0 <4.80.1)

Commands are suggestions: review each one before running it.