Kernel-memory disclosure via Audio out-of-bounds read
Published Nov 4, 2025 · Updated Nov 4, 2025
Out-of-bounds read in Apple Audio across affected operating-system releases allows local users to read kernel memory through a malicious app. Apple identifies the locus as Audio and says inadequate bounds checking permitted the read, but has not published the affected routine or input path. Local execution of a malicious app is required; the disclosed consequence is kernel-memory disclosure, with no vendor-reported write or code-execution impact.
Summary
What happened
Out-of-bounds read in Apple Audio across affected operating-system releases allows local users to read kernel memory through a malicious app. Apple identifies the locus as Audio and says inadequate bounds checking permitted the read, but has not published the affected routine or input path. Local execution of a malicious app is required; the disclosed consequence is kernel-memory disclosure, with no vendor-reported write or code-execution impact.
The record
- CVE
- CVE-2025-43361
- Published
- Nov 4, 2025
- Updated
- Nov 4, 2025
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-125, T1005
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2025CVE publishedPublication date reported by the CVE source.
- Nov 4, 2025Record 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=unspecified <26
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.
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