dbcve.org
FleetApplication · Fleetdm

CVE-2026-27465

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-26
Fix available
A fix is available. Upgrade to 4.80.1 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Fleet's configuration API endpoint returns Google Calendar service account credentials without proper obfuscation. Any authenticated user, including those with the lowest 'Observer' role, can access the API and retrieve the service account's private key material through the configuration response.

MitigationUpgrade to Fleet 4.80.1 or higher. If immediate upgrade is not possible, remove the Google Calendar integration from Fleet and rotate the exposed service account credentials.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FleetApplication
Affected:< 4.80.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Fleet version
    Retrieve the installed Fleet version via the UI, command line (fleetctl version), or API call and compare it to 4.80.1. Any version below 4.80.1 is affected.
    Affected if Installed version is lower than 4.80.1
  2. Verify Google Calendar integration status
    Access Fleet's settings or integrations configuration panel and check whether a Google Calendar integration is configured or enabled.
    Affected if Google Calendar integration is configured in Fleet
  3. Test low-privilege API access
    Using an account with the Observer role (the lowest privilege role), make a request to the configuration API endpoint and examine the response payload for unredacted credential fields.
    Affected if An Observer-role user can retrieve the configuration API response and it contains unmasked Google Calendar service account private key material

Environment is affected if running Fleet version below 4.80.1 with Google Calendar integration enabled, and low-privilege users can view unmasked service account credentials in the configuration API response.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 4.80.1 or later
Fixed in 4.80.1
Interim mitigation

Upgrade to Fleet 4.80.1 or higher. If immediate upgrade is not possible, remove the Google Calendar integration from Fleet and rotate the exposed service account credentials.

Recommended fix High confidence

Fleet 4.80.1

  1. Upgrade Fleet to version 4.80.1 or later to patch the credential exposure vulnerability
  2. After upgrading, verify through API testing that Google Calendar service account credentials are properly obfuscated and no longer returned in plaintext to low-privilege users
  3. If immediate upgrade is not possible, navigate to Fleet's integration settings and remove the Google Calendar integration
  4. Rotate the affected Google service account credentials by generating a new service account key in Google Cloud Console and updating the integration

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fleet Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27465 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-27465 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data