CVE-2026-28917 json
The issue was addressed with improved input validation.
published 2026-05-11 5 mo ago modified 2026-10-25 14 d ago also EUVD-2026-29238
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 22%
- public exploits
- 0
- none known
Summary
The issue was addressed with improved input validation. This issue is fixed in Safari 26.5, iOS 18.7.9 and iPadOS 18.7.9, iOS 26.5 and iPadOS 26.5, macOS Tahoe 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5. Processing maliciously crafted web content may lead to an unexpected process crash.
Patch / fix
- Apple Safari 26.5
- Apple iOS and iPadOS 18.7.9, 26.5
- Apple macOS 26.5
- Apple tvOS 26.5
- Apple visionOS 26.5
- Apple watchOS 26.5
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.30% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L |
Affected products
- Apple Safari
- 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/127110
release-notes, vendor-advisory
-
support.apple.com
/en-us/127111
release-notes, vendor-advisory
-
support.apple.com
/en-us/127115
release-notes, vendor-advisory
-
support.apple.com
/en-us/127118
release-notes, vendor-advisory
-
support.apple.com
/en-us/127119
release-notes, vendor-advisory
-
support.apple.com
/en-us/127120
release-notes, vendor-advisory
- support.apple.com /en-us/127121
Sources
- CVE List CVE-2026-28917
- NVD CVE-2026-28917
Fencer Vulns 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.