CVE-2026-28852 json
A stack overflow was addressed with improved input validation.
published 7mo ago modified 14d ago also EUVD-2026-15123
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
A stack overflow was addressed with improved input validation. This issue is fixed in iOS 18.7.7 and iPadOS 18.7.7, iOS 26.4 and iPadOS 26.4, macOS Sequoia 15.7.5, macOS Tahoe 26.4, tvOS 26.4, visionOS 26.4, watchOS 26.4. An app may be able to cause a denial-of-service.
Patch / fix
- Apple iOS and iPadOS 18.7.7, 26.4
- Apple macOS 15.7.5, 26.4
- Apple tvOS 26.4
- Apple visionOS 26.4
- Apple watchOS 26.4
Is CVE-2026-28852 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
- no
- Technical impact
- partial
- Assessed
- 7mo ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H |
Affected products
- Apple iOS and iPadOS
- Apple macOS
- Apple tvOS
- Apple visionOS
- Apple watchOS
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
support.apple.com
/en-us/126792
release-notes, vendor-advisory
-
support.apple.com
/en-us/126793
release-notes, vendor-advisory
-
support.apple.com
/en-us/126794
release-notes, vendor-advisory
-
support.apple.com
/en-us/126795
release-notes, vendor-advisory
-
support.apple.com
/en-us/126797
release-notes, vendor-advisory
-
support.apple.com
/en-us/126798
release-notes, vendor-advisory
-
support.apple.com
/en-us/126799
release-notes, vendor-advisory
Sources
- CVE List CVE-2026-28852
- NVD CVE-2026-28852
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.