Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution

Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution  

MS-ISAC ADVISORY NUMBER:
2025-102

DATE(S) ISSUED:
11/7/2025

 

SUBJECT:
Multiple Vulnerabilities in Apple Products Could Allow for Arbitrary Code Execution  

OVERVIEW:
Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

 

THREAT INTELLEGENCE:

There are currently no reports of these vulnerabilities being exploited in the wild.

 

SYSTEMS AFFECTED:

  • Versions prior to Xcode 26.1
  • Versions prior to Safari 26.1
  • Versions prior to visionOS 26.1
  • Versions prior to watchOS 26.1
  • Versions prior to tvOS 26.1
  • Versions prior to macOS Sonoma 14.8.2
  • Versions prior to macOS Sequoia 15.7.2
  • Versions prior to macOS Tahoe 26.1
  • Versions prior to iOS 26.1 and iPadOS 26.1
  • Versions prior to iOS 18.7.2 and iPadOS 18.7.2

 

RISK:
Government:

  • Large and medium government entities: High
  • Small government entities: Medium

 

Businesses:

  • Large and medium business entities: High
  • Small business entities: Medium

 

Home users: Low

 

TECHNICAL SUMMARY:
Multiple vulnerabilities have been discovered in Apple products, the most severe of which could allow for arbitrary code execution. Details of the vulnerabilities are as follows:

 

Tactic: Execution (TA0002):

Technique: Exploitation for Client Execution (T1203):

  • In certain configurations, an attacker with host-limited sudo access may be able to elevate privileges. (CVE-2025-32462)
  • Processing maliciously crafted web content may lead to memory corruption. (CVE-2025-43433, CVE-2025-43431)
  • Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory. (CVE-2025-43445, CVE-2025-43386, CVE-2025-43385, CVE-2025-43384, CVE-2025-43383, CVE-2025-43372, CVE-2025-43338)
  • An app may be able to cause unexpected system termination or corrupt kernel memory. (CVE-2025-43447, CVE-2025-43462, CVE-2025-43373)

 

Additional lower severity vulnerabilities include:

  • Processing a maliciously crafted file may lead to heap corruption. (CVE-2025-43505)
  • A user in a privileged network position may be able to cause a denial-of-service. (CVE-2025-43504)
  • Visiting a malicious website may lead to address bar spoofing. (CVE-2025-43493)
  • Visiting a malicious website may lead to user interface spoofing. (CVE-2025-43503)
  • An app may be able to bypass certain Privacy preferences. (CVE-2025-43502)
  • A malicious website may exfiltrate data cross-origin. (CVE-2025-43480)
  • Processing maliciously crafted web content may lead to an unexpected process crash. (CVE-2025-43458, CVE-2025-43430, CVE-2025-43427, CVE-2025-43443, CVE-2025-43441, CVE-2025-43435, CVE-2025-43425, CVE-2025-43440, CVE-2025-43432, CVE-2025-43429, CVE-2025-43421)
  • Processing maliciously crafted web content may lead to an unexpected Safari crash. (CVE-2025-43438, CVE-2025-43457, CVE-2025-43434)
  • A website may exfiltrate image data cross-origin. (CVE-2025-43392)
  • A malicious app may be able to take a screenshot of sensitive information in embedded views. (CVE-2025-43455)
  • An app may be able to access protected user data. (CVE-2025-43379, CVE-2025-43394, CVE-2025-43395, CVE-2025-43399, CVE-2025-43461, CVE-2025-43351)
  • An app may be able to break out of its sandbox. (CVE-2025-43407, CVE-2025-43448, CVE-2025-43476, CVE-2025-43412, CVE-2025-43481, CVE-2025-43497, CVE-2025-43364, CVE-2025-43393)
  • An attacker with physical access to an unlocked device paired with a Mac may be able to view sensitive user information in system logging. (CVE-2025-43423)
  • An app may be able to enumerate a user's installed apps. (CVE-2025-43436)
  • Processing a maliciously crafted media file may lead to unexpected app termination or corrupt process memory. (CVE-2025-43445, CVE-2025-43386, CVE-2025-43385, CVE-2025-43384, CVE-2025-43383, CVE-2025-43372, CVE-2025-43338)
  • An app may be able to access sensitive user data. (CVE-2025-43498, CVE-2025-43389, CVE-2025-43500, CVE-2025-43294, CVE-2025-43468, CVE-2025-43469, CVE-2025-43479, CVE-2025-43382, CVE-2025-43420, CVE-2025-43391, CVE-2025-43499, CVE-2025-43477, CVE-2025-31199, CVE-2025-43337, CVE-2025-43378, CVE-2025-43292, CVE-2025-43409, CVE-2025-43471, CVE-2025-43388, CVE-2025-43466, CVE-2025-43465, CVE-2025-43426, CVE-2025-43406, CVE-2025-43404, CVE-2025-43473, CVE-2025-43463)
  • An app may be able to fingerprint the user. (CVE-2025-43507, CVE-2025-43444, CVE-2025-43439)
  • An app may be able to cause unexpected system termination. (CVE-2025-43398, CVE-2025-43478)
  • A sandboxed app may be able to observe system-wide network connections. (CVE-2025-43413)
  • Remote content may be loaded even when the 'Load Remote Images' setting is turned off. (CVE-2025-43496)
  • Processing a maliciously crafted font may lead to unexpected app termination or corrupt process memory. (CVE-2025-43400)
  • An attacker with physical access to a locked Apple Watch may be able to view Live Voicemail. (CVE-2025-43459)
  • An app may be able to access user-sensitive data. (CVE-2025-43322, CVE-2025-43411, CVE-2025-43405, CVE-2025-43335, CVE-2025-43334, CVE-2025-43390)
  • An app may be able to modify protected parts of the file system. (CVE-2025-43446)
  • A malicious app may be able to read kernel memory. (CVE-2025-43361)
  • An app may be able to gain root privileges. (CVE-2025-43472, CVE-2025-43467)
  • A remote attacker may be able to cause a denial-of-service. (CVE-2025-43401)
  • An app may bypass Gatekeeper checks. (CVE-2025-43348)
  • An app may be able to cause unexpected system termination or read kernel memory. (CVE-2025-43474)
  • A sandboxed app may be able to access sensitive user data. (CVE-2025-43396)
  • Multiple issues in ruby. (CVE-2024-43398, CVE-2024-49761, CVE-2025-6442)
  • An attacker with physical access may be able to access contacts from the lock screen. (CVE-2025-43408)
  • A shortcut may be able to access files that are normally inaccessible to the Shortcuts app. (CVE-2025-30465, CVE-2025-43414)
  • Parsing a file may lead to an unexpected app termination. (CVE-2025-43380)
  • An app with root privileges may be able to access private information. (CVE-2025-43336)
  • An app may be able to cause a denial-of-service. (CVE-2025-43397, CVE-2025-43377)
  • A malicious app may be able to gain root privileges. (CVE-2025-43387)
  • A malicious app may be able to delete protected user data. (CVE-2025-43381)
  • Visiting a website may lead to an app denial-of-service. (CVE-2025-43464)
  • A malicious HID device may cause an unexpected process crash. (CVE-2025-43424)
  • iCloud Private Relay may not activate when more than one user is logged in at the same time. (CVE-2025-43506)
  • A path handling issue was addressed with improved validation. (CVE-2025-53906)
  • An app may be able to cause unexpected system termination or corrupt process memory. (CVE-2025-43402)
  • An app may be able to identify what other apps a user has installed. (CVE-2025-43442)
  • A malicious app may be able to track users between installs. (CVE-2025-43449)
  • An app may be able to learn information about the current camera view before being granted camera access. (CVE-2025-43450)
  • An attacker may be able to view restricted content from the lock screen. (CVE-2025-43350)
  • A device may persistently fail to lock. (CVE-2025-43454)
  • An attacker with physical access to a locked device may be able to view sensitive user information. (CVE-2025-43460, CVE-2025-43418)
  • An attacker with physical access to a device may be able to disable Stolen Device Protection. (CVE-2025-43422)
  • Keyboard suggestions may display sensitive information on the lock screen. (CVE-2025-43452)
  • An app may be able to monitor keystrokes without user permission. (CVE-2025-43495)
  • An unprivileged process may be able to terminate a root processes. (CVE-2025-43365)
    ​​​​​

Successful exploitation of the most severe of these vulnerabilities could allow for arbitrary code execution in the context of the logged on user. Depending on the privileges associated with the user, an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Users whose accounts are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:
We recommend the following actions be taken:

  • Apply the stable channel update provided by Apple to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
    • Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
    • Safeguard 7.2 : Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
    • Safeguard 7.6 : Perform Automated Vulnerability Scans of Externally-Exposed Enterprise Assets: Perform automated vulnerability scans of externally-exposed enterprise assets using a SCAP-compliant vulnerability scanning tool. Perform scans on a monthly, or more frequent, basis.
    • Safeguard 7.7 : Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
    • Safeguard 16.13 Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
    • Safeguard 18.1 : Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
    • Safeguard 18.2 : Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
    • Safeguard 18.3 : Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
       
  • Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
    • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software: Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
    • Safeguard 5.4: Restrict Administrator Privileges to Dedicated Administrator Accounts: Restrict administrator privileges to dedicated administrator accounts on enterprise assets. Conduct general computing activities, such as internet browsing, email, and productivity suite use, from the user’s primary, non-privileged account.
       
  • Restrict use of certain websites, block downloads/attachments, block Javascript, restrict browser extensions, etc. (M1021: Restrict Web-Based Content)
    • Safeguard 2.3: Address Unauthorized Software: Ensure that unauthorized software is either removed from use on enterprise assets or receives a documented exception. Review monthly, or more frequently.
    • Safeguard 2.7: Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassessbi-annually, or more frequently.
    • Safeguard 9.3: Maintain and Enforce Network-Based URL Filters: Enforce and update network-based URL filters to limit an enterprise asset from connecting to potentially malicious or unapproved websites. Example implementations include category-based filtering, reputation-based filtering, or through the use of block lists. Enforce filters for all enterprise assets.
    • Safeguard 9.6: Block Unnecessary File Types: Block unnecessary file types attempting to enter the enterprise’s email gateway.
       
  • Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
    • Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.
       
  • Block execution of code on a system through application control, and/or script blocking. (M1038: Execution Prevention)
    • Safeguard 2.5 : Allowlist Authorized Software: Use technical controls, such as application allowlisting, to ensure that only authorized software can execute or be accessed. Reassess bi-annually, or more frequently.
    • Safeguard 2.6 : Allowlist Authorized Libraries: Use technical controls to ensure that only authorized software libraries, such as specific .dll, .ocx, .so, etc., files, are allowed to load into a system process. Block unauthorized libraries from loading into a system process. Reassess bi-annually, or more frequently.
    • Safeguard 2.7 : Allowlist Authorized Scripts: Use technical controls, such as digital signatures and version control, to ensure that only authorized scripts, such as specific .ps1, .py, etc., files, are allowed to execute. Block unauthorized scripts from executing. Reassess bi-annually, or more frequently.
       
  • Use capabilities to prevent suspicious behavior patterns from occurring on endpoint systems. This could include suspicious process, file, API call, etc. behavior. (M1040: Behavior Prevention on Endpoint)
    • Safeguard 13.2 : Deploy a Host-Based Intrusion Detection Solution: Deploy a host-based intrusion detection solution on enterprise assets, where appropriate and/or supported.
    • Safeguard 13.7 : Deploy a Host-Based Intrusion Prevention Solution: Deploy a host-based intrusion prevention solution on enterprise assets, where appropriate and/or supported. Example implementations include use of an Endpoint Detection and Response (EDR) client or host-based IPS agent.

 

REFERENCES:

Apple:

https://support.apple.com/en-us/100100 

https://support.apple.com/en-us/125633 

https://support.apple.com/en-us/125632 

https://support.apple.com/en-us/125634 

https://support.apple.com/en-us/125635 

https://support.apple.com/en-us/125636 

https://support.apple.com/en-us/125637 

https://support.apple.com/en-us/125639 

https://support.apple.com/en-us/125638 

https://support.apple.com/en-us/125640 

https://support.apple.com/en-us/125641 

 

CVE:

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-43398 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2024-49761   

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-6442 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-30465 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-31199 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-32462 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43292 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43294 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43322 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43334 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43335 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43336 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43337 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43338 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43348 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43350 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43351 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43361 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43364 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43365 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43372 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43373 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43377 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43378 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43379 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43380 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43381 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43382 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43383 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43384 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43385 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43386 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43387 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43388 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43389 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43390 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43391 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43392 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43393 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43394 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43395 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43396 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43397 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43398 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43399 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43400 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43401 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43402 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43404 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43405 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43406 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43407 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43408 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43409 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43411 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43412 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43413 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43414 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43418 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43420 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43421 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43422 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43423 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43424 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43425 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43426 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43427 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43429 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43430 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43431 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43432 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43433 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43434 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43435 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43436 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43438 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43439 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43440 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43441 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43442 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43443 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43444 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43445 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43446 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43447 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43448 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43449 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43450 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43452 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43454 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43455 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43457 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43458 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43459 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43460 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43461 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43462 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43463 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43464 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43465 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43466 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43467 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43468 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43469 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43471 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43472 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43473 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43474 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43476 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43477 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43478 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43479 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43480 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43481 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43493 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43495 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43496 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43497 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43498 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43499 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43500 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43502 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43503 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43504 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43505 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43506 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-43507 

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2025-53906