CVE-2026-112673 json
A type confusion issue was addressed with improved state handling.
published 14d ago modified 5d ago also EUVD-2026-110114
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 48%
- public exploits
- 0
- none known
Summary
A type confusion issue was addressed with improved state handling. This issue is fixed in Safari 27.2, iOS 26.7.2 and iPadOS 26.7.2, iOS 27.2 and iPadOS 27.2, macOS Golden Gate 27.2, visionOS 27.2. Processing maliciously crafted web content may lead to an unexpected process termination.
Patch / fix
- Apple Safari 27.2
- Apple iOS and iPadOS 26.7.2, 27.2
- Apple macOS 27.2
- Apple visionOS 27.2
Is CVE-2026-112673 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
- 5d ago
Exploit prediction
0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-09).
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 |
| NVD | 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 visionOS
Classification
- Weakness
-
- CWE-843 Access of Resource Using Incompatible Type
References
-
support.apple.com
/en-us/149227
vendor-advisory
-
support.apple.com
/en-us/149230
vendor-advisory
-
support.apple.com
/en-us/149521
vendor-advisory
-
support.apple.com
/en-us/149526
vendor-advisory
-
support.apple.com
/en-us/149527
vendor-advisory
Sources
- CVE List CVE-2026-112673
- NVD CVE-2026-112673
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.