Process crash via libxslt memory mishandling
Published Jun 29, 2026 · Updated Jun 29, 2026
Denial of service in libxslt in Apple iOS, iPadOS, and macOS before 26.5.2 allows remote attackers to crash a process via web content. The component reads or writes outside intended memory bounds while processing the content, although Apple has not disclosed the precise operation. A user must cause an affected device to process the content; the documented consequence is a process crash rather than system-wide loss.
Summary
What happened
Denial of service in libxslt in Apple iOS, iPadOS, and macOS before 26.5.2 allows remote attackers to crash a process via web content. The component reads or writes outside intended memory bounds while processing the content, although Apple has not disclosed the precise operation. A user must cause an affected device to process the content; the documented consequence is a process crash rather than system-wide loss.
The record
- CVE
- CVE-2026-43703
- Published
- Jun 29, 2026
- Updated
- Jun 29, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-125, CWE-787, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 29, 2026CVE publishedPublication date reported by the CVE source.
- Jun 29, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <26.5.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo