VulnerabilityPublished 27 Jan 2025Updated 2 Apr 2026

CVE-2025-24169: Apple Safari · Sensitive Data in Logs

Affects Apple SafariSource CVE Database V5

Not known to be exploited · CVSS 7.5 High · fixed in 18.3 : patch Apple Safari soon.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

7.5High

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

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

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

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

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

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
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: None: There is no loss of confidentiality within the impacted component.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to 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 27 Jan 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 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 Safari	Affected =0	Fixed in–

AI-suggested

To mitigate CVE-2025-24169, organizations and users should promptly update Safari to version 18.3 or later and macOS to Sequoia 15.3 or later, where the vulnerability has been addressed. Beyond patching, administrators should audit and limit the use of browser extensions to only those that are essential and from trusted sources, reducing the attack surface. Implementing application whitelisting and restricting installation of unauthorized apps can prevent malicious apps from being present to exploit this flaw. Monitoring logs for unusual extension activity or authentication anomalies can help detect exploitation attempts. Security teams should review logging configurations to ensure sensitive data is properly redacted and not exposed in logs. For enterprise environments, consider deploying endpoint detection and response (EDR) solutions that can identify suspicious behaviors related to extension manipulation. Finally, educating users about the risks of installing unverified applications and extensions can reduce the likelihood of successful exploitation.

Description

A logging issue was addressed with improved data redaction. This issue is fixed in Safari 18.3, macOS Sequoia 15.3. A malicious app may be able to bypass browser extension authentication.

Impact

The primary impact of CVE-2025-24169 is on the integrity of browser extensions within Safari. A successful exploit allows a malicious app to bypass authentication, potentially enabling unauthorized actions such as data manipulation, interception of user inputs, or execution of malicious code within the extension context. This can lead to compromised user privacy, theft of sensitive information, or disruption of enterprise workflows relying on trusted extensions. Since the attack requires no privileges or user interaction, it can be exploited remotely, increasing the risk of widespread attacks. Organizations using Safari extensions for security enforcement, data protection, or productivity enhancements may face significant operational and reputational damage if this vulnerability is exploited. The absence of confidentiality and availability impacts reduces the risk of data leakage or denial of service, but the integrity compromise alone is critical enough to warrant immediate attention. The vulnerability also raises concerns about the security of logging mechanisms and the potential for similar issues in other Apple software components.

CWE-532Insertion of Sensitive Information into Log File (opens in a new tab)
Base weaknessLikelihood of exploit: MediumOWASP Top 10 A09:2025: Security Logging & Alerting Failures (opens in a new tab)
The product writes sensitive information to a log file.
Architecture and Design · Implementation
Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
Distribution
Remove debug log files before deploying the application into production.
Operation
Protect log files against unauthorized read/write.
OWASP Cheat Sheets
Application Logging Vocabulary (opens in a new tab)
Logging (opens in a new tab)
OWASP ASVS 4.0.3
V7.1.1 (opens in a new tab)
V7.1.2 (opens in a new tab)
V8.3.5 (opens in a new tab)
Attack patterns
Fuzzing for application mapping (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:41 UTC

WeaknessesCWE-532

Technical details

References

Community reviews

Related threats