Skip to main content
Menu
CVEs

CVE

Fleet denial of service in Apple MDM PKCS#7 parsing

Only affects Fleet instances with Apple MDM enabled that run a version before 4.86.2. Fixed in Fleet 4.86.2.

CVE-2026-130760Published Updated Summary written by a model

8.7HighCNA
Exploited
No known exploitation
Fix
Fixed in 4.86.2
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 4.86.2.

Summary

Fleet, a product from fleetdm, contains a denial-of-service flaw in how it parses Apple MDM PKCS#7 data. An attacker can reach it remotely, without logging in, by sending deeply nested data to the Apple MDM check-in, enrollment, SCEP, or OTA endpoints, which can exhaust server memory and crash the entire Fleet instance.

Original description

Fleet before 4.86.2 contains a denial of service vulnerability that allows unauthenticated attackers to exhaust server memory via unbounded BER recursion in PKCS#7 parsing. Attackers can send deeply nested indefinite-length structures to Apple MDM check-in, enrollment, SCEP, or OTA endpoints to crash the entire Fleet instance.

Who should check

Teams running Fleet before 4.86.2 with Apple MDM enabled, including exposed Apple MDM check-in, enrollment, SCEP or OTA endpoints.

Not fixed by: Request size limits do not fully mitigate this issue.

“This issue only affects Fleet instances with Apple MDM enabled.”

github.com

cve.now Index

36Pcve.now Index 36 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach10/20Affects Go packages
  • Severity8.7/10CVSS 8.7
  • No patch0/5No signal

What would change the score

  • Would score about 81 if added to CISA KEV
  • Would score about 76 if CISA's SSVC rates exploitation active
  • Would score about 41 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 4.86.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-130760 (Fleet before 4.86.2 Unauthenticated DoS via Apple MDM PKCS#7 Parsing), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-130760 (entry last updated 2026-11-18):
Affected:
- Go package github.com/fleetdm/fleet: fixed in 4.86.2
Fixed versions: 4.86.2.
Conditions (all must be true for the bug to be hit):
- Fleet instance with Apple MDM enabled (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-3qx5-8m9j-pmrp)
- Fleet version before 4.86.2 (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-3qx5-8m9j-pmrp)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130760 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130760 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fleetdm/fleet/security/advisories/GHSA-3qx5-8m9j-pmrp
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-130760
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130760"}.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · fleetdm/fleet · Advisory GHSA-3qx5-8m9j-pmrp
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-130760
RecordNVD · CVE-2026-130760

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-130760

Is CVE-2026-130760 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An unauthenticated attacker can crash the Fleet server with a single request by exhausting its memory. This causes a denial of service for the whole instance and affects availability only.Source: github.com

Which versions are affected by CVE-2026-130760?

github.com/fleetdm/fleet (Go): before 4.86.2.Source: cve.now feed data

Am I affected, and how do I check?

Fleet versions before 4.86.2 are affected, but only instances with Apple MDM enabled. To check, look at your Fleet version and whether Apple MDM is enabled on the instance.Source: github.com

How do I fix CVE-2026-130760?

Upgrade Fleet to version 4.86.2 or later, which contains the fix.Source: github.com

More CVEs