Latest Cybersecurity Vulnerabilities - Real-Time Updates

Latest 30 CVEs - Real-Time Cyber Threats

Cyber threats are constantly evolving, making real-time vulnerability tracking essential. Below are the 30 most recently disclosed Common Vulnerabilities and Exposures (CVEs), providing key details such as affected vendors, impact levels, and risk scores.

Each CVE entry includes a brief summary and a direct link to its full details, enabling cybersecurity professionals, system administrators, and developers to quickly assess and mitigate potential security risks.

CVE-2025-4444 Moderate Vulnerability Alert
A security flaw has been discovered in Tor up to 0.4.7.16/0.4.8.17. Impacted is an unknown function of the component Onion Service Descriptor Handler. Performing manipulation results in resource consumption. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitability is considered difficult. Upgrading to version 0.4.8.18 and 0.4.9.3-alpha is recommended to address this issue. It is recommended to upgrade the affected component.
Score: 3.7_/10 ⚠️ Moderate Risk
Published on 18 Sep 2025, 14:15 UTC (only 1 hour ago)
CVE-2025-10670 Exploitable Vulnerability Warning
A flaw has been found in itsourcecode E-Logbook with Health Monitoring System for COVID-19 1.0. This issue affects some unknown processing of the file /check_profile.php. Executing manipulation of the argument profile_id can lead to sql injection. It is possible to launch the attack remotely. The exploit has been published and may be used.
Score: 7.3_/10 🔥 Very High Risk
Published on 18 Sep 2025, 14:15 UTC (only 1 hour ago)
CVE-2025-10669 Critical Risk Assessment
A vulnerability was detected in Airsonic-Advanced up to 10.6.0. This vulnerability affects unknown code of the component Playlist Upload Handler. Performing manipulation results in unrestricted upload. It is possible to initiate the attack remotely. The exploit is now public and may be used.
Score: 6.3_/10 🔥 High Risk
Published on 18 Sep 2025, 14:15 UTC (only 1 hour ago)
CVE-2025-10668 Severe Cybersecurity Threat
A security vulnerability has been detected in itsourcecode Online Discussion Forum 1.0. This affects an unknown part of the file /members/compose_msg_admin.php. Such manipulation of the argument ID leads to sql injection. The attack may be performed from remote. The exploit has been disclosed publicly and may be used.
Score: 7.3_/10 🔥 Very High Risk
Published on 18 Sep 2025, 14:15 UTC (only 1 hour ago)
CVE-2023-53418 Security Notice
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: lpc32xx_udc: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53417 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: USB: sl811: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53416 Security Notice
In the Linux kernel, the following vulnerability has been resolved: USB: isp1362: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53415 Security Notice
In the Linux kernel, the following vulnerability has been resolved: USB: dwc3: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. Note, the root dentry for the debugfs directory for the device needs to be saved so we don't have to keep looking it up, which required a bit more refactoring to properly create and remove it when needed. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53414 Technical Report
In the Linux kernel, the following vulnerability has been resolved: scsi: snic: Fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53413 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: USB: isp116x: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53412 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: bcm63xx_udc: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53411 Security Notice
In the Linux kernel, the following vulnerability has been resolved: PM: EM: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53410 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: USB: ULPI: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53409 Security Notice
In the Linux kernel, the following vulnerability has been resolved: drivers: base: component: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53408 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: trace/blktrace: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53407 Technical Report
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: pxa27x_udc: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53406 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: pxa25x_udc: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53405 Vulnerability Insight
In the Linux kernel, the following vulnerability has been resolved: USB: gadget: gr_udc: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53404 Technical Report
In the Linux kernel, the following vulnerability has been resolved: USB: fotg210: fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)
CVE-2023-53403 Security Notice
In the Linux kernel, the following vulnerability has been resolved: time/debug: Fix memory leak with using debugfs_lookup() When calling debugfs_lookup() the result must have dput() called on it, otherwise the memory will leak over time. To make things simpler, just call debugfs_lookup_and_remove() instead which handles all of the logic at once. ⏳ Analysis in Progress 18 Sep 2025, 14:15 UTC (1 hour ago)