MediumGHSA-q9c5-pp7m-fm2gCVE-2026-101047GO-2026-6268

Fleet: Unauthenticated download of in-house iOS app binaries via predictable URLs

Published 20 Aug 2026 · Updated 28 Sept 2026

Is your project on an affected github.com/fleetdm/fleet/v4?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

Affected
<4.87.0
Fixed in
4.87.0
Update to the fixed version for your release line, for example:go get github.com/fleetdm/fleet/v4@v4.87.0

Details

Summary

Two endpoints serving in-house iOS application packages and manifests in Fleet's enterprise tier are reachable without a hard-to-guess token in the URL, allowing an unauthenticated attacker who can reach the Fleet server to download an in-house IPA by guessing sequential title identifiers.

Impact

By design, Apple's InstallEnterpriseApplication MDM command requires that the manifest URL be reachable by the managed device without a Fleet session, so these endpoints cannot enforce session-based authentication. Fleet's legacy MDM installer path mitigates this by embedding a random, hard-to-guess token in the URL; the in-house iOS app endpoints (added later) were always intended to use the same time-limited-token pattern but the mitigation was not yet in place.

The result is read-only disclosure of in-house IPA binaries and their metadata (bundle identifier, version, name) that an operator has deployed through Fleet. This is enterprise-tier only — the free tier returns fleet.ErrMissingLicense. There is no privilege escalation, write access, or impact on hosts not managed by Fleet.

Workarounds

If an immediate upgrade is not possible:

  • Restrict network access to the Fleet server to trusted networks, as is typical for MDM deployments.
  • Remove in-house iOS apps that contain sensitive material from Fleet; in-house app IPAs are intentionally reachable by managed devices and should not be relied on as a confidential distribution channel.
  • Where available, configure CloudFront URL signing for software installers to limit the validity window of issued binary URLs.

For more information

If you have any questions or comments about this advisory:

Email us at [security@fleetdm.com](mailto:security@fleetdm.com) Join #fleet in osquery Slack

Credits

We thank @offset for responsibly reporting this issue.

Is GHSA-q9c5-pp7m-fm2g in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/fleetdm/fleet/v4, and gives you the command that fixes it.

More advisories for github.com/fleetdm/fleet/v4

  • LowCVE-2026-54245Fleet: SQL injection in Okta conditional access endpoint allows host-controlled compromise of the Fleet database in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints in github.com/fleetdm/fleet · 25 Aug 2026
  • LowCVE-2026-101046Fleet: ORDER BY column injection on activity list endpoints · 20 Aug 2026
  • LowCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint in github.com/fleetdm/fleet · 18 Aug 2026
  • MediumCVE-2026-48786Fleet: Observer-class users can view team enroll secrets and credential-bearing configuration via target search endpoint · 12 Aug 2026
  • LowCVE-2026-41262Fleet DM Vulnerable to Cross-Team Policy Data Exposure via Global Policy Read Endpoint in github.com/fleetdm/fleet · 7 Jul 2026
All 59 advisories for github.com/fleetdm/fleet/v4

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.