# CVE-2026-27465: Fleet: Sensitive Google Calendar credentials disclosed to low-privileged users > Low-privileged users can retrieve Google Calendar service account credentials via the configuration API, potentially accessing external calendar data. - **Severity:** Low 1.3 (`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`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Feb 2026 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-2v6m-6xw3-6467, GO-2026-4560 ## What is CVE-2026-27465? CVE-2026-27465 is a low-severity vulnerability in fleetdm fleet, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data) ## Which versions are affected by CVE-2026-27465? 3 open source packages ship an affected version, including github.com/fleetdm/fleet/v4. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/fleetdm/fleet/v4` | Go | All versions | 4.80.1 | | `github.com/fleetdm/fleet/v4` | Go | All versions | 4.80.1 | | `github.com/fleetdm/fleet/v4` | Go | All versions | 4.80.1 | Products: Fleetdm Fleet. ## How do I fix CVE-2026-27465? Upgrade github.com/fleetdm/fleet/v4 to 4.80.1 or later. ## Is CVE-2026-27465 being exploited? There is no known exploitation of CVE-2026-27465 in the wild and no public exploit code. ## Other vulnerabilities in fleetdm fleet - [CVE-2020-26276](https://insights.sbomify.com/CVE-2020-26276/): SAML authentication vulnerability in Fleet (critical 10.0) - [CVE-2026-103264](https://insights.sbomify.com/CVE-2026-103264/): Fleet before 4.87.0 Authentication Bypass via Device Identifiers (critical 9.3) - [CVE-2026-23518](https://insights.sbomify.com/CVE-2026-23518/): Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment (critical 9.3) - [CVE-2026-26062](https://insights.sbomify.com/CVE-2026-26062/): Fleet server may terminate unexpectedly when handling certain gRPC requests (high 8.7) - [CVE-2026-26061](https://insights.sbomify.com/CVE-2026-26061/): Fleet's unbounded request body read allows remote Denial of Service (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27465 and fix it if it is affected. What it is: CVE-2026-27465 is a low-severity vulnerability in fleetdm fleet, published on 26 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-27465 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.80.1 - github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.80.1 - github.com/fleetdm/fleet/v4 (Go): affected all versions; fixed in 4.80.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-27465/ (Markdown: https://insights.sbomify.com/CVE-2026-27465/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27465 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27465 - OSV: https://osv.dev/vulnerability/CVE-2026-27465 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27465/ Summaries are generated and may contain mistakes; the official description above is the record.