IRONSMITHINTEL
MEDIUMCVSS6.3
|
Actively Exploited
|CISA KEV|CVE-2024-44309|Auth: none — unauthenticated|Reboot: required|Manual only

Apple Multiple Products Cross-Site Scripting (XSS) Vulnerability (CVE-2024-44309)

Apple iOS, macOS, and other Apple products contain an unspecified vulnerability when processing maliciously crafted web content that may lead to a cross-site scripting (XSS) attack.

Published Nov 20, 2024 · Updated May 17, 2026
Why patchRisk explained in plain English
Worst-case scenarioIf unpatched

A remote attacker, without authentication, can achieve partial data exposure, partial data tampering, partial service disruption. Federal agencies are required to remediate by 2024-12-12 under CISA BOD 22-01.

How the attack worksNo clicks needed

This is a Cross-Site Scripting (XSS) (CWE-79) vulnerability in Apple Multiple Products. A cookie management issue was addressed with improved state management. This issue is fixed in Safari 18.1.1, iOS 17.7.2 and iPadOS 17.7.2, iOS 18.1.1 and iPadOS 18.1.1, macOS Sequoia 15.1.1, visionOS 2.1.1. Processing maliciously crafted web content may lead to a cross site scripting attack. Apple is aware of a report that this issue may have been actively exploited on Intel-based Mac systems. Exploitation requires remote network access, low attack complexity, no authentication required, and user interaction required.

📧

Phishing link

→

🖼

Malicious file

🔓

Server compromised

Am I affected?Quick check

Probably yes if any of these apply:

●Apple Device Administrators
●Endpoint Security
●IT Security
●Running debian linux: 11.0; safari: v < 18.1.1; ipados: v < 17.7.2, 18.0 ≤ v < 18.1.1; iphone os: v < 17.7.2, 18.0 ≤ v < 18.1.1; macos: 15.0 ≤ v < 15.1.1; visionos: v < 2.1.1
Real-world incidentsWhat we've seen

CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2024-11-21 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2024-12-12.

How to patch

Manual remediation steps

1
Identify affected hosts: query inventory for general installs in scope.
2
Apply the vendor security update referenced in CVE-2024-44309's advisory. No specific KB/version is encoded yet — consult the linked MSRC/vendor URL.
3
Verify the fix per the vendor's published verification steps.
4
Document the remediation in your change ticket and re-scan with your vulnerability scanner to confirm closure.
PowerShell automationComing soon

No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.

References

↗ CVE-2024-44309↗ MSRC Advisory↗ NVD↗ Vendor Advisory