Safeguard
Vulnerability Analysis•

CVE-2023-32383: High Code Injection in Apple macOS and Xcode

CVE-2023-32383 is a high severity code injection flaw in macOS affecting Xcode binaries. Update to Ventura 13.4, Monterey 12.6.6 or Big Sur 11.7.7.

Safeguard Security Team
3 min read

CVE-2023-32383 is a high severity (CVSS 7.8) code injection flaw in Apple macOS. An app may be able to inject code into sensitive binaries bundled with Xcode. Apple fixed it by forcing the hardened runtime on those binaries in macOS Ventura 13.4, Monterey 12.6.6 and Big Sur 11.7.7. Update to those releases or later.

What's affected

The record lists Apple macOS and says the issue is fixed in macOS Monterey 12.6.6, macOS Big Sur 11.7.7 and macOS Ventura 13.4.

Apple's Ventura 13.4 bulletin, HT213758, places the entry under AppleMobileFileIntegrity and gives the fix as enforcing the hardened runtime on the affected binaries at the system level. The Ventura release date on that page is May 18, 2023. The bulletin credits an external researcher.

Developers are the most interesting group here. The affected binaries ship with Xcode, so machines that build and sign software carry more risk than a plain office laptop. The Monterey and Big Sur bulletins are referenced by the record but were not fetched for this review.

How to check if you're exposed

Open the Apple menu, choose About This Mac, and read the macOS version. From Terminal you can print it directly:

sw_vers -productVersion

Compare the result with the fixed versions above. Any Mac older than the fixed release for its major version is exposed to this flaw. Fleet owners can run the same command through their device management tool and report the output per machine.

Developer machines should also record the installed Xcode version, since the vulnerable binaries came bundled with it. Apple's note describes a system level fix, so the macOS update is what matters.

What to do now

  1. List developer and build Macs first, since Xcode binaries are the target.
  2. Update to Ventura 13.4, Monterey 12.6.6 or Big Sur 11.7.7 at minimum.
  3. Reboot and confirm with sw_vers -productVersion.
  4. Review who can install and run unsigned apps on build machines and reduce that list.
  5. Look at your signing and notarization process and confirm build keys stay on machines that are patched.

Why it matters

The weakness class is CWE-94, improper control of code generation, commonly called code injection. A process was able to load or run code inside another trusted process. The hardened runtime is the macOS feature that blocks that by default, and Apple's fix was to turn it on for the Xcode binaries rather than rely on each binary to opt in.

Injection into a trusted developer tool is a supply chain concern. Code that runs inside a build tool can see source, credentials and signing material that the tool can see. The record does not claim exploitation and the KEV flag is false, so this is a patch and hygiene item, not an emergency.

Your pipeline holds more than operating system risk. Run the free in-browser dependency scan on your repositories to see which libraries your own builds pull in, and treat the build machine as part of the supply chain.

Quick check

Who should care most about CVE-2023-32383?

Anyone who builds and signs software on macOS, because the affected binaries come with Xcode.

How did Apple fix it?

By forcing the hardened runtime on the affected binaries at the system level, per Apple security content HT213758.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.