# CVE-2026-130758: Fleet before 4.92.0 Authorization Bypass via Deprecated Apple MDM Enqueue Endpoint


- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-5vr5-74q2-mfg4, GHSA-6q65-q858-42p2

## What is CVE-2026-130758?

CVE-2026-130758 is a high-severity vulnerability in fleetdm fleet, published on 18 Nov 2026. 

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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

1 open source package ship an affected version, including github.com/fleetdm/fleet.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/fleetdm/fleet` | Go | `pkg:golang/github.com/fleetdm/fleet` | All versions | 4.92.0 |

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

Upgrade github.com/fleetdm/fleet to 4.92.0 or later.

## Is CVE-2026-130758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-130758 is a high-severity vulnerability in fleetdm fleet, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-130758 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/fleetdm/fleet (Go): affected all versions; fixed in 4.92.0

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

## Sources

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

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