CVE
Fleet authorization bypass in deprecated Apple MDM endpoint
Fleet before 4.92.0 lets a team-scoped admin, maintainer, or GitOps user reach Apple MDM enrollments outside their teams through the deprecated enqueue endpoint. Fixed in 4.92.0.
- Exploited
- No known exploitation
- Fix
- Fixed in 4.92.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Fleet before 4.92.0 is affected. The deprecated Apple MDM enqueue endpoint is used (POST /api/latest/fleet/mdm/apple/enqueue). Attacker holds a team-scoped admin, maintainer, or GitOps role. Attacker includes one UUID of a host on their own team alongside the target enrollment IDs.
Summary
Fleet contains an authorization bypass in its deprecated Apple MDM enqueue endpoint that lets team-scoped users send Apple MDM commands outside their own teams. Remotely over the network, an attacker who already holds a team admin, maintainer, or GitOps role can send commands such as InstallProfile to deleted or user-channel enrollments without the activity being logged.
Original description
Fleet before 4.92.0 contains an authorization bypass vulnerability in the deprecated POST /api/latest/fleet/mdm/apple/enqueue endpoint that allows team-scoped users to enqueue Apple MDM commands outside their teams. Attackers with team admin, maintainer, or GitOps roles can include one own-team host UUID alongside unresolved enrollment IDs to send commands like InstallProfile to deleted or user-channel enrollments without activity logging.
Who should check
Teams running Fleet before 4.92.0 that manage Apple MDM devices and grant team-scoped admin, maintainer, or GitOps roles.
“Team-scoped users could enqueue Apple MDM commands to enrollments outside their teams”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Affects Go packages
- Severity8.6/10CVSS 8.6
- No patch0/5No signal
What would change the score
- Would score about 77 if added to CISA KEV
- Would score about 72 if CISA's SSVC rates exploitation active
- Would score about 34 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Fleet before 4.92.0 is affected. The deprecated Apple MDM enqueue endpoint is used (POST /api/latest/fleet/mdm/apple/enqueue). Attacker holds a team-scoped admin, maintainer, or GitOps role. Attacker includes one UUID of a host on their own team alongside the target enrollment IDs.Upgrade to a fixed version: 4.92.0.
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-130758 (Fleet before 4.92.0 Authorization Bypass via Deprecated Apple MDM Enqueue Endpoint), 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-130758 (entry last updated 2026-11-18):
Affected:
- Go package github.com/fleetdm/fleet: fixed in 4.92.0
Fixed versions: 4.92.0.
Conditions (all must be true for the bug to be hit):
- Fleet before 4.92.0 is affected. (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-5vr5-74q2-mfg4)
- The deprecated Apple MDM enqueue endpoint is used (POST /api/latest/fleet/mdm/apple/enqueue). (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-5vr5-74q2-mfg4)
- Attacker holds a team-scoped admin, maintainer, or GitOps role. (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-5vr5-74q2-mfg4)
- Attacker includes one UUID of a host on their own team alongside the target enrollment IDs. (source: https://github.com/fleetdm/fleet/security/advisories/GHSA-5vr5-74q2-mfg4)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, high-privilege login, no user action.
CISA KEV: CVE-2026-130758 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130758 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-5vr5-74q2-mfg4
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-130758
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-130758"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
fixed in 4.92.0
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · fleetdm/fleet · Advisory GHSA-5vr5-74q2-mfg4 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-130758 |
| Record | NVD · CVE-2026-130758 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130758
Is CVE-2026-130758 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?
The deprecated Apple MDM enqueue endpoint (POST /api/latest/fleet/mdm/apple/enqueue) can be used to queue arbitrary Apple MDM commands, such as InstallProfile, against enrollments outside the user's authorized teams. The user includes one UUID of a host on their own team alongside the target enrollment IDs, and the action is not recorded in the activity log.Source: github.com
Which versions are affected by CVE-2026-130758?
github.com/fleetdm/fleet (Go): before 4.92.0.Source: cve.now feed data
Am I affected, and how do I check?
Fleet versions before 4.92.0 are affected, and the issue requires a team-scoped admin, maintainer, or GitOps role plus calls to the deprecated Apple MDM enqueue endpoint. To check, look at the Fleet server version and whether any automation or tooling sends requests to POST /api/latest/fleet/mdm/apple/enqueue.Source: github.com
How do I fix CVE-2026-130758?
Upgrade Fleet to 4.92.0 or later, which is the fixed version named in the advisory.Source: github.com