Privacy logging bypass via insufficient entitlement checks
Published May 11, 2026 · Updated May 11, 2026
Privacy authorization weakness in Apple iOS and iPadOS before 18.7.9 or 26.4 allows attackers to bypass App Privacy Report logging. The Privacy component applies insufficient entitlement checks when deciding whether app activity must be recorded, allowing that activity to escape the report. Execution of an app on an affected device is required; the consequence is incomplete privacy telemetry rather than access to underlying user data.
Summary
What happened
Privacy authorization weakness in Apple iOS and iPadOS before 18.7.9 or 26.4 allows attackers to bypass App Privacy Report logging. The Privacy component applies insufficient entitlement checks when deciding whether app activity must be recorded, allowing that activity to escape the report. Execution of an app on an affected device is required; the consequence is incomplete privacy telemetry rather than access to underlying user data.
The record
- CVE
- CVE-2026-28873
- Published
- May 11, 2026
- Updated
- May 11, 2026
- Vendor
- Apple
- Product
- iOS and iPadOS
- Classifications
- CWE-863, T1629
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- May 11, 2026CVE publishedPublication date reported by the CVE source.
- May 11, 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 <18.7.9
- Affected versionversion=0 <26.4
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