CVE-2026-28935 json
The issue was addressed with improved memory handling.
published last mo. modified 14d ago also EUVD-2026-77992
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved memory handling. This issue is fixed in iOS 26.6.1 and iPadOS 26.6.1, macOS Sequoia 15.8, macOS Tahoe 26.6.2, tvOS 27, visionOS 27, watchOS 27. An app may be able to cause unexpected system termination or corrupt kernel memory.
Patch / fix
- Apple iOS and iPadOS 26.6.1
- Apple macOS 15.8, 26.6.2
- Apple tvOS 27
- Apple visionOS 27
- Apple watchOS 27
Is CVE-2026-28935 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- last mo.
Exploit prediction
0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
support.apple.com
/en-us/148281
release-notes, vendor-advisory
-
support.apple.com
/en-us/148282
release-notes, vendor-advisory
-
support.apple.com
/en-us/149036
release-notes, vendor-advisory
-
support.apple.com
/en-us/149037
release-notes, vendor-advisory
-
support.apple.com
/en-us/149038
release-notes, vendor-advisory
-
support.apple.com
/en-us/149043
release-notes, vendor-advisory
Sources
- CVE List CVE-2026-28935
- NVD CVE-2026-28935
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.