CVE-2026-23518: Github.com/fleetdm/fleet Fleet Has A JWT Signature Vulnerability

CRITICAL
Advisory Identifier: GHSA-63m5-974w-448v
CWE-347
Published
Advisory Summary

CVE-2026-23518 is a CRITICAL fleet has a jwt signature vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Github.com/fleetdm/fleet libraries in the Go ecosystem. The issue involves fleet has a jwt signature bypass vulnerability in azure ad mdm enrollment. Remediation is available by upgrading affected packages to version 4.78.3, 4.77.1, 4.76.2, 4.75.2, 4.43.5-0.20260112202845-e225ef57912c.

CVE-2026-23518 at a Glance

CVE Identifier CVE-2026-23518
GHSA Identifier GHSA-63m5-974w-448v
Severity CRITICAL
CVSS v3.1 Base Score N/A
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Github.com/fleetdm/fleet
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-23518

To remediate this vulnerability, upgrade all affected Github.com/fleetdm/fleet dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/fleetdm/fleet fixed: 4.78.3
Upgrade github.com/fleetdm/fleet to 4.78.3
github.com/fleetdm/fleet fixed: 4.77.1
Upgrade github.com/fleetdm/fleet to 4.77.1
github.com/fleetdm/fleet fixed: 4.76.2
Upgrade github.com/fleetdm/fleet to 4.76.2
github.com/fleetdm/fleet fixed: 4.75.2
Upgrade github.com/fleetdm/fleet to 4.75.2
github.com/fleetdm/fleet fixed: 4.43.5-0.20260112202845-e225ef57912c
Upgrade github.com/fleetdm/fleet to 4.43.5-0.20260112202845-e225ef57912c
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/fleetdm/fleet

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-23518, inspect your project dependencies for Github.com/fleetdm/fleet:

inspect dependencies for github.com/fleetdm/fleet

Analyze the terminal output to locate any version of Github.com/fleetdm/fleet in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.78.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Github.com/fleetdm/fleet, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary A vulnerability in Fleet’s Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities. ### Impact If Windows MDM is enabled, an attacker can enroll rogue devices by submitting a forged JWT containing arbitrary identity claims. Due to missing JWT signature verification, Fleet accepts these claims without validating that the token was issued by Azure AD, allowing enrollment under any Azure AD user identity. ### Patches - 4.78.3 - 4.77.1 - 4.76.2 - 4.75.2 - 4.53.3 ### Workarounds If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM. ### For more information If you have any questions or comments about this advisory: Email us at [security@fleetdm.com](mailto:security@fleetdm.com) Join #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw) ### Credits We thank @secfox-ai for responsibly reporting this issue.

CVE-2026-23518 Affected Github.com/fleetdm/fleet Versions

5 component(s)
Fixed Versions:
4.78.34.77.14.76.24.75.24.43.5-0.20260112202845-e225ef57912c
Product / Package Ecosystem Affected Versions Fixed Version
github.com/fleetdm/fleet
Go
≥ 4.78.0
< 4.78.3
4.78.3
github.com/fleetdm/fleet
Go
≥ 4.77.0
< 4.77.1
4.77.1
github.com/fleetdm/fleet
Go
≥ 4.76.0
< 4.76.2
4.76.2
github.com/fleetdm/fleet
Go
≥ 4.75.0
< 4.75.2
4.75.2
github.com/fleetdm/fleet
Go
< 4.43.5-0.20260112202845-e225ef57912c
4.43.5-0.20260112202845-e225ef57912c

References

Frequently Asked Questions

What is CVE-2026-23518?
CVE-2026-23518 is a security vulnerability in Github.com/fleetdm/fleet involving Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment under CWE-347: Improper Verification of Cryptographic Signature.
Which Github.com/fleetdm/fleet versions are affected?
Affected versions include releases prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, 4.43.5-0.20260112202845-e225ef57912c across affected packages: github.com/fleetdm/fleet.
What version fixes CVE-2026-23518?
Upgrading to 4.78.3, 4.77.1, 4.76.2, 4.75.2, 4.43.5-0.20260112202845-e225ef57912c (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/fleetdm/fleet affected?
Yes, github.com/fleetdm/fleet is affected in releases prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, 4.43.5-0.20260112202845-e225ef57912c. Upgrade your dependency to 4.78.3, 4.77.1, 4.76.2, 4.75.2, 4.43.5-0.20260112202845-e225ef57912c or later.
What CWE is associated with CVE-2026-23518?
CVE-2026-23518 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check Go dependencies for CVE-2026-23518?
Run the dependency tree command: 'inspect dependencies for github.com/fleetdm/fleet'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-63m5-974w-448v",
  "modified" : "2026-02-27T22:02:58Z",
  "published" : "2026-01-20T20:55:17Z",
  "aliases" : [ "CVE-2026-23518" ],
  "summary" : "Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment ",
  "details" : "### Summary\n\nA vulnerability in Fleet’s Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities.\n\n### Impact\n\nIf Windows MDM is enabled, an attacker can enroll rogue devices by submitting a forged JWT containing arbitrary identity claims. Due to missing JWT signature verification, Fleet accepts these claims without validating that the token was issued by Azure AD, allowing enrollment under any Azure AD user identity.\n\n### Patches\n\n- 4.78.3\n- 4.77.1\n- 4.76.2\n- 4.75.2\n- 4.53.3\n\n### Workarounds\n\nIf an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.\n\n### For more information\n\nIf you have any questions or comments about this advisory:\n\nEmail us at [security@fleetdm.com](mailto:security@fleetdm.com)\nJoin #fleet in [osquery Slack](https://join.slack.com/t/osquery/shared_invite/zt-h29zm0gk-s2DBtGUTW4CFel0f0IjTEw)\n\n### Credits\n\nWe thank @secfox-ai for responsibly reporting this issue.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.78.0"
      }, {
        "fixed" : "4.78.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.77.0"
      }, {
        "fixed" : "4.77.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.76.0"
      }, {
        "fixed" : "4.76.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "4.75.0"
      }, {
        "fixed" : "4.75.2"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/fleetdm/fleet"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "4.43.5-0.20260112202845-e225ef57912c"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/fleetdm/fleet/security/advisories/GHSA-63m5-974w-448v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-23518"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/fleetdm/fleet/commit/e225ef57912c8f4ac8977e24b5ebe1d9fd875257"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/fleetdm/fleet"
  }, {
    "type" : "WEB",
    "url" : "https://pkg.go.dev/vuln/GO-2026-4335"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "CRITICAL",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-01-20T20:55:17Z",
    "nvd_published_at" : "2026-01-21T22:15:50Z"
  }
}