CVE-2025-24133VulnerabilityPublished 15 Sep 2025Updated 1 Oct 2025

CVE-2025-24133: Apple iOS and iPadOS

Affects Apple iOS and iPadOSSource CVE Database V5

Not known to be exploited · CVSS 4.0 Medium.

Data as of 8 Oct 2025, 23:21 UTC

CVSS 3.1 base score

4.0Medium

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

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 15 Sep 2025
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 2026-10-25.

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 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

AI-suggested

European organizations should implement strict physical security controls to prevent unauthorized local access to iOS and iPadOS devices, including enforcing device lock policies with strong passcodes and biometric protections. Mobile device management (MDM) solutions should be used to enforce security policies, restrict installation of untrusted applications, and enable remote wipe capabilities in case of device loss or theft. Regular monitoring and auditing of device access logs can help detect suspicious local access attempts. Organizations should stay alert for official Apple security updates addressing this vulnerability and apply patches promptly once available. Additionally, educating users about the risks of local device access and enforcing policies against leaving devices unattended in unsecured locations will reduce exploitation opportunities. For highly sensitive environments, consider limiting the use of iOS/iPadOS devices or segregating sensitive data away from mobile platforms until patches are applied.

Impact

For European organizations, this vulnerability poses a moderate risk primarily in environments where iOS and iPadOS devices are used in sensitive contexts and where local access to devices cannot be strictly controlled. The confidentiality impact, while limited, could lead to unauthorized disclosure of sensitive information stored on or accessible through the device. This could affect organizations handling personal data, intellectual property, or confidential communications on Apple mobile devices. The lack of impact on integrity and availability reduces the risk of operational disruption or data manipulation. However, sectors such as finance, healthcare, and government agencies in Europe, which often rely on mobile Apple devices for secure communications and data access, could be concerned about any confidentiality breach. The local attack vector means that remote exploitation is unlikely, but insider threats or physical device theft scenarios could be exploited. The absence of known exploits in the wild reduces immediate risk but does not eliminate the potential for future exploitation.

Summary

CVE-2025-24133 is a vulnerability identified in Apple's iOS and iPadOS platforms. Although specific technical details and affected versions are not provided, the CVSS vector string indicates that the vulnerability requires local access (AV:L), has low attack complexity (AC:L), does not require privileges (PR:N), and does not require user interaction (UI:N). The scope is unchanged (S:U), and the impact is limited to confidentiality (C:L) with no impact on integrity (I:N) or availability (A:N). This suggests that an attacker with local access to the device could exploit this vulnerability to gain limited unauthorized access to confidential information without affecting system integrity or availability. The absence of known exploits in the wild and lack of patch links indicate that this vulnerability might be newly disclosed or not yet actively exploited. The vulnerability was reserved in January 2025 and published in September 2025, indicating a recent discovery. Given the local attack vector and no required privileges or user interaction, exploitation might be feasible for an attacker with physical or local access to the device, such as through a malicious app or direct device access. However, the limited confidentiality impact suggests that the data exposure would be partial or limited in scope.

Community reviews

Loading reviews…

Exploitation evidence

What to do

AI analysisMachine-generated, updated 2 Oct 2025, 00:13 UTC

Impact

Summary

Technical details

Community reviews

Related threats