Fleet before 4.87.0 Authentication Bypass via Device Identifiers

Why this deserves its current priority

CVSS is 9.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Affected scope and exposure questions

The current feed maps fleetdm/fleet (generic). Check affected ranges and fixed versions before updating.

Recommended response

1. 1Check inventory. Check lockfiles and deployed manifests for fleetdm/fleet.
2. 2Review the reported fix. Update fleetdm/fleet to 4.87.0 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

1. Published upstream

   Oct 1, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

2. Source modified

   Oct 1, 2026

   Evidence: source:cvelist:source_dates:source-dates:record

3. First seen by HOL

   Oct 1, 2026

Sources and claim methodology

• GitHub security advisorygithub.com
• Source referencevulncheck.com

Related CVEs

• Fleet before 4.89.0 Information Disclosure via MDM Command ResultsSame fleetdm/fleet package
• Apache APISIX: Openid-connect introspection validation issueAlso CWE-287
• n8n before 1.123.80, 2.39.6, and 2.40.1 SQL Injection via Oracle Database Drop TableSame generic ecosystem
• n8n before 1.123.80, 2.39.6, and 2.40.1 Path Traversal via Resume URL GenerationSame generic ecosystem
• n8n before 1.123.80, 2.39.6, and 2.40.1 Path Traversal and Query Injection via SupabaseSame generic ecosystem
• n8n before 2.39.6 and 2.40.x before 2.40.1 Credentials Leak via preAuthentication HookSame generic ecosystem