Search

Use the Query Builder to create your own search query, or check out the documentation to learn the search syntax.

Search Examples

CVEs in KEV CVEs with EPSS >= 80% Crit. Microsoft High Apache SQL Injection (CWE-89) Linux Kernel High (CVSS 3.1) Apache Struts RCE (Remote Code Execution) XSS (CWE-79) Critical (CVSS 4.0) CVEs to check

Search Results (337984 CVEs found)

Export CSV
CVE Vendors Products Updated CVSS v3.1
CVE-2021-40449 1 Microsoft 26 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 23 more 2025-10-30 7.8 High
Win32k Elevation of Privilege Vulnerability
CVE-2021-40450 1 Microsoft 14 Windows 10 1809, Windows 10 1909, Windows 10 2004 and 11 more 2025-10-30 7.8 High
Win32k Elevation of Privilege Vulnerability
CVE-2021-41357 1 Microsoft 12 Windows 10 1809, Windows 10 2004, Windows 10 20h2 and 9 more 2025-10-30 7.8 High
Win32k Elevation of Privilege Vulnerability
CVE-2021-41379 1 Microsoft 25 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 22 more 2025-10-30 5.5 Medium
Windows Installer Elevation of Privilege Vulnerability
CVE-2021-36948 1 Microsoft 11 Windows 10 1809, Windows 10 1909, Windows 10 2004 and 8 more 2025-10-30 7.8 High
Windows Update Medic Service Elevation of Privilege Vulnerability
CVE-2021-36955 1 Microsoft 23 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 20 more 2025-10-30 7.8 High
Windows Common Log File System Driver Elevation of Privilege Vulnerability
CVE-2025-21983 1 Linux 1 Linux Kernel 2025-10-30 7.8 High
In the Linux kernel, the following vulnerability has been resolved: mm/slab/kvfree_rcu: Switch to WQ_MEM_RECLAIM wq Currently kvfree_rcu() APIs use a system workqueue which is "system_unbound_wq" to driver RCU machinery to reclaim a memory. Recently, it has been noted that the following kernel warning can be observed: <snip> workqueue: WQ_MEM_RECLAIM nvme-wq:nvme_scan_work is flushing !WQ_MEM_RECLAIM events_unbound:kfree_rcu_work WARNING: CPU: 21 PID: 330 at kernel/workqueue.c:3719 check_flush_dependency+0x112/0x120 Modules linked in: intel_uncore_frequency(E) intel_uncore_frequency_common(E) skx_edac(E) ... CPU: 21 UID: 0 PID: 330 Comm: kworker/u144:6 Tainted: G E 6.13.2-0_g925d379822da #1 Hardware name: Wiwynn Twin Lakes MP/Twin Lakes Passive MP, BIOS YMM20 02/01/2023 Workqueue: nvme-wq nvme_scan_work RIP: 0010:check_flush_dependency+0x112/0x120 Code: 05 9a 40 14 02 01 48 81 c6 c0 00 00 00 48 8b 50 18 48 81 c7 c0 00 00 00 48 89 f9 48 ... RSP: 0018:ffffc90000df7bd8 EFLAGS: 00010082 RAX: 000000000000006a RBX: ffffffff81622390 RCX: 0000000000000027 RDX: 00000000fffeffff RSI: 000000000057ffa8 RDI: ffff88907f960c88 RBP: 0000000000000000 R08: ffffffff83068e50 R09: 000000000002fffd R10: 0000000000000004 R11: 0000000000000000 R12: ffff8881001a4400 R13: 0000000000000000 R14: ffff88907f420fb8 R15: 0000000000000000 FS: 0000000000000000(0000) GS:ffff88907f940000(0000) knlGS:0000000000000000 CR2: 00007f60c3001000 CR3: 000000107d010005 CR4: 00000000007726f0 PKRU: 55555554 Call Trace: <TASK> ? __warn+0xa4/0x140 ? check_flush_dependency+0x112/0x120 ? report_bug+0xe1/0x140 ? check_flush_dependency+0x112/0x120 ? handle_bug+0x5e/0x90 ? exc_invalid_op+0x16/0x40 ? asm_exc_invalid_op+0x16/0x20 ? timer_recalc_next_expiry+0x190/0x190 ? check_flush_dependency+0x112/0x120 ? check_flush_dependency+0x112/0x120 __flush_work.llvm.1643880146586177030+0x174/0x2c0 flush_rcu_work+0x28/0x30 kvfree_rcu_barrier+0x12f/0x160 kmem_cache_destroy+0x18/0x120 bioset_exit+0x10c/0x150 disk_release.llvm.6740012984264378178+0x61/0xd0 device_release+0x4f/0x90 kobject_put+0x95/0x180 nvme_put_ns+0x23/0xc0 nvme_remove_invalid_namespaces+0xb3/0xd0 nvme_scan_work+0x342/0x490 process_scheduled_works+0x1a2/0x370 worker_thread+0x2ff/0x390 ? pwq_release_workfn+0x1e0/0x1e0 kthread+0xb1/0xe0 ? __kthread_parkme+0x70/0x70 ret_from_fork+0x30/0x40 ? __kthread_parkme+0x70/0x70 ret_from_fork_asm+0x11/0x20 </TASK> ---[ end trace 0000000000000000 ]--- <snip> To address this switch to use of independent WQ_MEM_RECLAIM workqueue, so the rules are not violated from workqueue framework point of view. Apart of that, since kvfree_rcu() does reclaim memory it is worth to go with WQ_MEM_RECLAIM type of wq because it is designed for this purpose.
CVE-2021-38645 1 Microsoft 12 Azure Automation State Configuration, Azure Automation Update Management, Azure Diagnostics and 9 more 2025-10-30 7.8 High
Open Management Infrastructure Elevation of Privilege Vulnerability
CVE-2021-38646 1 Microsoft 2 365 Apps, Office 2025-10-30 7.8 High
Microsoft Office Access Connectivity Engine Remote Code Execution Vulnerability
CVE-2021-38647 1 Microsoft 12 Azure Automation State Configuration, Azure Automation Update Management, Azure Diagnostics and 9 more 2025-10-30 9.8 Critical
Open Management Infrastructure Remote Code Execution Vulnerability
CVE-2021-38648 1 Microsoft 12 Azure Automation State Configuration, Azure Automation Update Management, Azure Diagnostics and 9 more 2025-10-30 7.8 High
Open Management Infrastructure Elevation of Privilege Vulnerability
CVE-2021-34484 1 Microsoft 22 Windows 10 1507, Windows 10 1607, Windows 10 1809 and 19 more 2025-10-30 7.8 High
Windows User Profile Service Elevation of Privilege Vulnerability
CVE-2021-34486 1 Microsoft 11 Windows 10 1809, Windows 10 1909, Windows 10 2004 and 8 more 2025-10-30 7.8 High
Windows Event Tracing Elevation of Privilege Vulnerability
CVE-2021-34523 1 Microsoft 1 Exchange Server 2025-10-30 9 Critical
Microsoft Exchange Server Elevation of Privilege Vulnerability
CVE-2021-36942 1 Microsoft 10 Windows Server 2004, Windows Server 2008, Windows Server 2008 R2 and 7 more 2025-10-30 7.5 High
Windows LSA Spoofing Vulnerability
CVE-2023-21715 1 Microsoft 1 365 Apps 2025-10-30 7.3 High
Microsoft Publisher Security Feature Bypass Vulnerability
CVE-2023-21823 1 Microsoft 22 Office, Windows 10 1507, Windows 10 1607 and 19 more 2025-10-30 7.8 High
Windows Graphics Component Remote Code Execution Vulnerability
CVE-2025-2161 2 Pega, Pegasystems 2 Pega Platform, Pega Infinity 2025-10-30 7.1 High
Pega Platform versions 7.2.1 to Infinity 24.2.1 are affected by an XSS issue with Mashup
CVE-2024-30152 1 Hcltech 1 Hcl Sx 2025-10-30 6.5 Medium
HCL SX v21 is affected by usage of a weak cryptographic algorithm. An attacker could exploit this weakness to gain access to sensitive information, modify data, or other impacts.
CVE-2025-2160 2 Pega, Pegasystems 2 Pega Platform, Pega Infinity 2025-10-30 8.1 High
Pega Platform versions 8.4.3 to Infinity 24.2.1 are affected by an XSS issue with Mashup