Apple macOS kernel memory corruption from out-of-bounds write
- Exploited
- No known exploitation
- Fix
- Fixed in 27.2
- Who is exposed
- Not reported
Summary
An out-of-bounds write flaw in Apple's macOS lets an app cause unexpected system termination or corrupt kernel memory. The issue was fixed with improved bounds checking in macOS Golden Gate.
Written by a model
Original description
An out-of-bounds write issue was addressed with improved bounds checking. This issue is fixed in macOS Golden Gate 27.2. An app may be able to cause unexpected system termination or corrupt kernel memory.
What to do
Upgrade to a fixed version: 27.2.
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-132475 (An out-of-bounds write issue was addressed with improved bounds checking.), 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-132475 (entry last updated 2026-11-20):
Affected:
- Apple macOS: fixed in 27.2
Fixed versions: 27.2.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-132475 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132475 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://support.apple.com/en-us/149521
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-132475
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-132475"}.Affected versions
- Apple macOSfixed in 27.2
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure?/25Unknown. No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity?/10Unknown. No CVSS score or vendor rating
- No patch0/5No signal
What would change the score
- Would score about 55 if added to CISA KEV
- Would score about 50 if CISA's SSVC rates exploitation active
- Would score about 22 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
Evidence 3
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Link | support.apple.com · en-us/149521 |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132475 |
| Record | NVD · CVE-2026-132475 |
Questions about CVE-2026-132475
Is CVE-2026-132475 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
Which versions are affected by CVE-2026-132475?
macOS: before 27.2.
Source: cve.now feed data
How do I fix CVE-2026-132475?
Upgrade to a fixed version: 27.2.
Source: cve.now feed data
Related
- CVE-2026-113970A use-after-free issue was addressed with improved memory management.
- CVE-2026-65327A logic issue was addressed with improved checks.
- CVE-2026-84627A buffer overflow was addressed with improved bounds checking.
- CVE-2026-113969A logic issue was addressed with improved state management.
- CVE-2026-113961An authorization issue was addressed with improved validation.
- CVE-2026-112529An out-of-bounds read was addressed with improved bounds checking.
No corrections so far. Something wrong on this page? Report an error.