VulnerabilityPublished 28 Oct 2024Updated 2 Apr 2026

CVE-2024-44263: Apple iOS and iPadOS · An app may be able to access user-sensitive data

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium · fixed in 18.1 : update Apple iOS and iPadOS when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

4.0Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 18.1

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector: Local
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: Low
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 28 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Apple iOS and iPadOS	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2024-44263, organizations and users should promptly update all affected Apple devices to iOS 18.1 or iPadOS 18.1 or later, where the vulnerability is fixed. Beyond patching, organizations should enforce strict app installation policies, restricting apps to those vetted through the Apple App Store and using Mobile Device Management (MDM) solutions to control app permissions and monitor unusual app behavior. Regular audits of installed applications and their data access permissions can help detect potentially malicious apps exploiting this vulnerability. Employing endpoint protection solutions that monitor for anomalous data access patterns on iOS/iPadOS devices can provide additional detection capabilities. User education about the risks of installing untrusted apps and the importance of timely updates is also critical. For high-security environments, consider additional data encryption and compartmentalization strategies to limit the impact of any data exposure. Finally, maintain an incident response plan that includes mobile device compromise scenarios.

Description

A logic issue was addressed with improved state management. This issue is fixed in iOS 18.1 and iPadOS 18.1. An app may be able to access user-sensitive data.

Impact

The primary impact of CVE-2024-44263 is the unauthorized disclosure of user-sensitive data on affected Apple devices. This can lead to privacy violations, leakage of personal or corporate confidential information, and potential secondary attacks if sensitive data such as credentials or tokens are exposed. Since the vulnerability can be exploited by any app without requiring user interaction or elevated privileges, it increases the risk surface significantly, especially in environments where users install apps from less trusted sources or where device management policies are lax. Organizations relying on iOS and iPadOS devices for sensitive communications, business operations, or handling regulated data could face compliance and reputational risks if this vulnerability is exploited. However, the lack of integrity or availability impact limits the scope to confidentiality concerns. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, as attackers may develop exploits post-disclosure. The local attack vector means physical or logical device access is necessary, somewhat limiting remote exploitation scenarios.

CWE-922Insecure Storage of Sensitive Information (opens in a new tab)
Class weaknessOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.1.6 (opens in a new tab)
V8.2.3 (opens in a new tab)
V8.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 3 Apr 2026, 00:05 UTC

WeaknessesCWE-922

Technical details

References

Community reviews

Related threats