CISA KEV Catalog Updated: Federal Agencies Must Patch Exploited Flaws in Apple, Laravel, Craft CMS

CISA Adds Actively Exploited Vulnerabilities in Apple visionOS, Laravel, and Craft CMS to KEV Catalog

HIGH
March 23, 2026
4m read
VulnerabilityPatch ManagementRegulatory

Related Entities

Organizations

Products & Tech

Laravel Framework Craft CMSApple visionOS

CVE Identifiers

Full Report

Executive Summary

On March 22, 2026, the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added three vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog, confirming they are under active exploitation by threat actors. The additions mandate that Federal Civilian Executive Branch (FCEB) agencies patch these flaws by April 12, 2026. The vulnerabilities affect a diverse range of popular products: Apple visionOS, the Laravel Framework, and Craft CMS. The flaws include an arbitrary code execution bug in Apple's new spatial computing platform, a remote code execution vulnerability in a widely-used PHP framework, and a privilege escalation flaw in a popular content management system. CISA's directive underscores the immediate risk these vulnerabilities pose, and all public and private sector organizations are strongly advised to prioritize applying the necessary security updates to mitigate active threats.


Vulnerability Details

The three vulnerabilities added to the KEV catalog represent distinct threats to different parts of the technology stack.

CVE-2026-28217: Apple visionOS Out-of-Bounds Write

  • Product: Apple visionOS
  • Description: An out-of-bounds write vulnerability that can be exploited by an attacker to cause unexpected application termination or, more critically, achieve arbitrary code execution on an Apple Vision Pro device.
  • Impact: Compromise of the device, potentially leading to data theft or unauthorized access.
  • KEV Status: True

CVE-2024-4671: Laravel Framework Remote Code Execution

  • Product: Laravel Framework
  • Description: This vulnerability is related to a previously disclosed flaw (CVE-2018-15133) and can lead to remote code execution. Exploitation is possible if the application's unique APP_KEY is exposed, a condition that can occur through misconfiguration or information disclosure vulnerabilities.
  • Impact: Full server compromise, allowing an attacker to execute arbitrary commands on the web server.
  • KEV Status: True

CVE-2026-25487: Craft CMS Cross-Site Scripting (XSS)

  • Product: Craft CMS
  • Description: A critical cross-site scripting (XSS) vulnerability. An unauthenticated attacker can craft a malicious link and, by tricking a logged-in administrator into clicking it, can create a new user account with full administrative privileges.
  • Impact: Complete takeover of the CMS, enabling the attacker to deface the website, steal data, or use the server for further attacks.
  • KEV Status: True

Exploitation Status

By definition, all three vulnerabilities are being actively exploited in the wild. CISA adds vulnerabilities to the KEV catalog only when there is reliable evidence of active exploitation. The specific threat actors or campaigns leveraging these flaws were not detailed in the CISA alert, but their inclusion serves as a definitive warning of their real-world risk.

Impact Assessment

The impact varies by vulnerability but is significant in each case:

  • CVE-2026-28217 (Apple): Compromise of a high-profile, emerging technology device used for both personal and professional applications. Could lead to theft of sensitive visual, audio, and personal data.
  • CVE-2024-4671 (Laravel): Affects countless web applications built on one of the most popular PHP frameworks. A successful exploit leads to server compromise, data breaches, and a platform for hosting malware or launching further attacks.
  • CVE-2026-25487 (Craft CMS): Gives attackers full administrative control over a website, leading to reputational damage, content manipulation, and potential compromise of user data collected by the site.

Detection Methods

  1. Asset Inventory and Version Scanning: The first step is to identify all assets running the affected software. Use software inventory tools, dependency scanners (for Laravel), and web scanners to find instances of Apple visionOS, Laravel applications, and Craft CMS, and check their version numbers against the patched versions.
  2. Web Server Log Analysis: For Laravel and Craft CMS, monitor web server access logs for suspicious requests. For CVE-2024-4671, look for requests that may indicate attempts to leak .env files or exploit deserialization. For CVE-2026-25487, look for unusual GET requests containing script tags or other XSS payloads, particularly those targeting administrative endpoints.
  3. Endpoint/Device Management: For CVE-2026-28217, use Mobile Device Management (MDM) solutions to query the OS version of all managed Apple Vision Pro devices to ensure they are updated.

Remediation Steps

Remediation for all three vulnerabilities involves applying the latest security updates provided by the respective vendors.

  1. Apply Patches Immediately (D3-SU): This is the most critical action. Organizations must follow the guidance from Apple, Laravel, and Craft CMS to update their systems. This is a direct application of D3FEND Software Update (D3-SU).
    • Apple visionOS: Update devices to the latest version via the system's software update mechanism.
    • Laravel Framework: Update to the patched version of the framework. Crucially, audit all applications to ensure the APP_KEY is not exposed and rotate the key if there is any suspicion of compromise.
    • Craft CMS: Update to the latest patched version of Craft CMS.
  2. Review for Compromise: Since these vulnerabilities are actively exploited, simply patching may not be enough. Organizations should review logs and system activity for signs of compromise that may have occurred before the patch was applied.
  3. Implement WAF Rules: For the web-based vulnerabilities (Laravel and Craft CMS), Web Application Firewalls (WAFs) can provide an additional layer of protection by blocking common XSS and RCE attack patterns. This aligns with D3FEND Inbound Traffic Filtering (D3-ITF).

Timeline of Events

1
March 22, 2026
CISA adds CVE-2026-28217, CVE-2024-4671, and CVE-2026-25487 to the KEV catalog.
2
March 23, 2026
This article was published
3
April 12, 2026
Deadline for U.S. Federal Civilian Executive Branch agencies to patch the newly added vulnerabilities.

MITRE ATT&CK Mitigations

Applying vendor patches is the primary mitigation for all three vulnerabilities.

Using a Web Application Firewall (WAF) can help block exploit attempts against the Laravel and Craft CMS vulnerabilities.

Audit

M1047enterprise

Regularly auditing and scanning for vulnerable software versions is crucial for timely detection and remediation.

D3FEND Defensive Countermeasures

The inclusion of these vulnerabilities in the CISA KEV catalog mandates immediate action. The most effective countermeasure is to apply the security updates provided by the vendors. For CVE-2026-28217, Apple Vision Pro devices must be updated to the latest visionOS. For CVE-2024-4671, Laravel applications must be updated, and critically, their configuration must be audited to ensure the APP_KEY is not exposed. For CVE-2026-25487, Craft CMS installations must be upgraded to a patched version. Organizations should use automated patch management and software composition analysis (SCA) tools to identify all affected instances and deploy updates systematically. Given these are actively exploited, patching should be treated as an emergency and completed well before the CISA deadline of April 12, 2026.

For the web-facing vulnerabilities (CVE-2024-4671 in Laravel and CVE-2026-25487 in Craft CMS), a Web Application Firewall (WAF) can serve as a vital defense-in-depth layer. Configure your WAF with rules to detect and block common attack patterns associated with these flaws. For the Craft CMS XSS flaw, this includes filtering for malicious JavaScript in URL parameters targeting admin pages. For the Laravel RCE, this includes blocking requests attempting to read .env files or carrying serialized PHP object payloads. While WAFs are not a substitute for patching, they can provide 'virtual patching' that protects systems while the official update is being tested and deployed, and can help defend against zero-day variants of these attacks.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

CISAKEVvulnerabilityAppleLaravelCraft CMSzero-daypatch management

📢 Share This Article

Help others stay informed about cybersecurity threats