Skip to main content
VulnerabilityPublished Updated

CVE-2026-28889: Apple Xcode · Improper Privilege Management

Affects Apple XcodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.2 Medium : upgrade to 26.4 when convenient.

Data as of 29 Oct 2026, 19:04 UTC

CVSS 3.1 base score
6.2Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 1% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 26.4
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade Apple Xcode to 26.4.

Affected software

ProductAffectedFixed in
AppleXcodeAffected
  • <26.4
Fixed in
  • 26.4

AI-suggested

  1. Immediately upgrade all Xcode installations to version 26.4 or later, where the vulnerability is fixed.
  2. Restrict installation of untrusted or unsigned applications on development machines to reduce risk of malicious apps exploiting this flaw.
  3. Implement strict access controls and sandboxing policies for apps running on macOS to limit their file system access.
  4. Regularly audit and monitor file access logs on development systems to detect unusual or unauthorized file reads.
  5. Use endpoint protection solutions capable of detecting privilege escalation attempts or anomalous app behavior.
  6. Educate developers and IT staff about the risks of running untrusted code and the importance of timely patching.
  7. Consider isolating sensitive development environments from general user systems to minimize exposure.
  8. Review and tighten macOS security settings, including System Integrity Protection (SIP) and user permissions, to reduce attack surface.
  9. Employ code signing and notarization enforcement to prevent execution of unauthorized apps.
  10. Maintain an inventory of all development tools and ensure they are kept up to date with security patches.

Description

A permissions issue was addressed with additional restrictions. This issue is fixed in Xcode 26.4. An app may be able to read arbitrary files as root.

References

Community reviews

Loading reviews…