# CVE-2026-111923: Fleet before 4.89.0 Unauthenticated DoS via Apple MDM Enrollment Plist Parsing

> Unauthenticated attackers can crash the Fleet MDM server by sending crafted binary plist payloads to enrollment endpoints, causing resource exhaustion.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-jc4v-4w5q-xhc2, GHSA-x467-vgxf-2g6h

## What is CVE-2026-111923?

CVE-2026-111923 is a high-severity denial of service vulnerability in fleetdm fleet, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Fleet before 4.89.0 contains an unbounded recursion vulnerability in Apple MDM enrollment property list parsing that allows unauthenticated attackers to crash the server. Attackers can send a crafted binary plist payload of about 150 bytes to the enrollment endpoints, triggering exponential allocation or infinite recursion that exhausts CPU and memory.

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2026-111923?


## How do I fix CVE-2026-111923?

No fix has been published for CVE-2026-111923 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-111923 being exploited?

There is no known exploitation of CVE-2026-111923 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111923 and fix it if it is affected.

What it is: CVE-2026-111923 is a high-severity denial of service vulnerability in fleetdm fleet, published on 17 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111923 in the wild and no public exploit code.

Affected product: fleetdm fleet. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-111923/ (Markdown: https://insights.sbomify.com/CVE-2026-111923/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111923
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111923
- OSV: https://osv.dev/vulnerability/CVE-2026-111923

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111923/
Summaries are generated and may contain mistakes; the official description above is the record.