Vulnerabilities
All
My stack
Known exploited
Public exploit
Critical (9+)
Likely exploited (EPSS ≥ 50%)
Changed, 24 h
New, 24 h
Sort:
risk
modified
published
CVSS
EPSS
| CVE | CVSS | EPSS | Vendor, product | Description | Modified |
|---|---|---|---|---|---|
| CVE-2016-3081KEVexploit ×2 | 8.1 high | 97.0% | huawei, apache, agile_controller-campus_firmware, anyoffice, logcenter | Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via method: prefix, related to chained expressions. | 9 Oct |
| CVE-2020-8840exploit ×6 | 9.8 critical | 27.0% | fasterxml, debian, jackson-databind, debian_linux, oncommand_api_services | FasterXML jackson-databind 2.0.0 through 2.9.10.2 lacks certain xbean-reflect/JNDI blocking, as demonstrated by org.apache.xbean.propertyeditor.JndiConverter. | 8 Oct |
| CVE-2026-34865 | 10.0 critical | 0.00% | huawei, harmonyos | Out-of-bounds write vulnerability in the WEB module.Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | Mon 26 Oct |
| CVE-2026-65198 | 8.6 high | 0.00% | no CPE yet | Huawei's openUBMC ships a default SNMPv3 USM key that uses one value for both authentication and privacy. An attacker who holds the key (recoverable from the open-source build) can authenticate SNMPv3 to, and decrypt SNMPv3 traffic from, any unit that still carries the shipped key. The build customization `manifest/build/customization/default_password.lua` sets `AuthenticationKey == EncryptionKey == 7df2f29369e3ac3245b2c9d46b67a0ecd055197e41808a34ef325db2f6422581` for the iBMC product build, and the community seed `account/manufacture/default_password.lua` sets both to `7a2f5b86f20233ec7b7bef49643fbf34d86d0cbf6f1f8f5c52d4f30d4536938b`. These are shipped constants, not per-unit values, and they are not rotated by the Administrator password reset, so they survive account provisioning. This is especially dangerous considering that SNMP access is mapped to full device administration privileges, including system reset and firmware upgrades. | 16 Oct |
| CVE-2022-50630 | 7.8 high | 0.00% | no CPE yet | In the Linux kernel, the following vulnerability has been resolved: mm: hugetlb: fix UAF in hugetlb_handle_userfault The vma_lock and hugetlb_fault_mutex are dropped before handling userfault and reacquire them again after handle_userfault(), but reacquire the vma_lock could lead to UAF[1,2] due to the following race, hugetlb_fault hugetlb_no_page /*unlock vma_lock */ hugetlb_handle_userfault handle_userfault /* unlock mm->mmap_lock*/ vm_mmap_pgoff do_mmap mmap_region munmap_vma_range /* clean old vma */ /* lock vma_lock again <--- UAF */ /* unlock vma_lock */ Since the vma_lock will unlock immediately after hugetlb_handle_userfault(), let's drop the unneeded lock and unlock in hugetlb_handle_userfault() to fix the issue. [1] https://lore.kernel.org/linux-mm/[email protected]/ [2] https://lore.kernel.org/linux-mm/[email protected]/ | 15 Oct |
| CVE-2026-28553 | 7.5 high | 0.00% | huawei, harmonyos, emui | Vulnerability of improper permission control in the theme setting module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | Mon 26 Oct |
| CVE-2026-34851 | 7.5 high | 0.00% | huawei, harmonyos | Race condition vulnerability in the event notification module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34856 | 7.5 high | 0.00% | huawei, harmonyos | UAF vulnerability in the communication module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34853 | 7.5 high | 0.00% | huawei, harmonyos, emui | Permission bypass vulnerability in the LBS module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2025-64312 | 7.5 high | 0.00% | huawei, harmonyos | Permission control vulnerability in the file management module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2026-34854 | 7.1 high | 0.00% | huawei, harmonyos, emui | UAF vulnerability in the kernel module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | Mon 26 Oct |
| CVE-2026-34859 | 7.1 high | 0.00% | huawei, harmonyos, emui | UAF vulnerability in the kernel module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | Mon 26 Oct |
| CVE-2025-58314 | 7.1 high | 0.00% | huawei, emui, harmonyos | Vulnerability of accessing invalid memory in the component driver module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | 18 Oct |
| CVE-2025-58311 | 7.1 high | 0.00% | huawei, emui, harmonyos | UAF vulnerability in the USB driver module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | 18 Oct |
| CVE-2026-110123 | 7.1 high | 0.00% | no CPE yet | Makunet maku-boot 4.3.0 through 5.0.0 contains a missing authorization vulnerability that allows authenticated users to read mail and SMS configurations by calling /sys/mail/config/list and /sys/sms/config/list without the required authority checks. Attackers can retrieve unmasked SMTP passwords and Aliyun, Tencent Cloud, Qiniu or Huawei Cloud access keys, and abuse /sys/mail/config/send to send mail to arbitrary recipients. | 16 Oct |
| CVE-2025-58309 | 7.1 high | 0.00% | huawei, harmonyos | Permission control vulnerability in the startup recovery module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | 8 Oct |
| CVE-2025-64315 | 7.1 high | 0.00% | huawei, harmonyos | Configuration defect vulnerability in the file management module. Impact: Successful exploitation of this vulnerability may affect app data confidentiality and integrity. | 8 Oct |
| CVE-2026-34860 | 6.5 medium | 0.00% | huawei, harmonyos | Access control vulnerability in the memo module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | Mon 26 Oct |
| CVE-2026-34852 | 6.5 medium | 0.00% | huawei, harmonyos | Stack overflow vulnerability in the media platform. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34850 | 5.9 medium | 0.00% | huawei, harmonyos | Race condition vulnerability in the notification service. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34855 | 5.7 medium | 0.00% | huawei, harmonyos, emui | Out-of-bounds write vulnerability in the kernel module. Impact: Successful exploitation of this vulnerability will affect availability and confidentiality. | Sun 25 Oct |
| CVE-2026-34867 | 5.6 medium | 0.00% | huawei, harmonyos | Double free vulnerability in the multi-mode input system. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34857 | 5.5 medium | 0.00% | huawei, harmonyos | UAF vulnerability in the communication module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34864 | 5.5 medium | 0.00% | huawei, harmonyos | Boundary-unlimited vulnerability in the application read module. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-34863 | 5.5 medium | 0.00% | huawei, harmonyos | Out-of-bounds write vulnerability in the file system. Impact: Successful exploitation of this vulnerability may affect availability. | Mon 26 Oct |
| CVE-2026-31767 | 5.5 medium | 0.00% | linux, linux_kernel | In the Linux kernel, the following vulnerability has been resolved: drm/i915/dsi: Don't do DSC horizontal timing adjustments in command mode Stop adjusting the horizontal timing values based on the compression ratio in command mode. Bspec seems to be telling us to do this only in video mode, and this is also how the Windows driver does things. This should also fix a div-by-zero on some machines because the adjusted htotal ends up being so small that we end up with line_time_us==0 when trying to determine the vtotal value in command mode. Note that this doesn't actually make the display on the Huawei Matebook E work, but at least the kernel no longer explodes when the driver loads. (cherry picked from commit 0b475e91ecc2313207196c6d7fd5c53e1a878525) | 21 Oct |
| CVE-2025-39782 | 5.5 medium | 0.00% | linux, debian, linux_kernel, debian_linux | In the Linux kernel, the following vulnerability has been resolved: jbd2: prevent softlockup in jbd2_log_do_checkpoint() Both jbd2_log_do_checkpoint() and jbd2_journal_shrink_checkpoint_list() periodically release j_list_lock after processing a batch of buffers to avoid long hold times on the j_list_lock. However, since both functions contend for j_list_lock, the combined time spent waiting and processing can be significant. jbd2_journal_shrink_checkpoint_list() explicitly calls cond_resched() when need_resched() is true to avoid softlockups during prolonged operations. But jbd2_log_do_checkpoint() only exits its loop when need_resched() is true, relying on potentially sleeping functions like __flush_batch() or wait_on_buffer() to trigger rescheduling. If those functions do not sleep, the kernel may hit a softlockup. watchdog: BUG: soft lockup - CPU#3 stuck for 156s! [kworker/u129:2:373] CPU: 3 PID: 373 Comm: kworker/u129:2 Kdump: loaded Not tainted 6.6.0+ #10 Hardware name: Huawei TaiShan 2280 /BC11SPCD, BIOS 1.27 06/13/2017 Workqueue: writeback wb_workfn (flush-7:2) pstate: 20000005 (nzCv daif -PAN -UAO -TCO -DIT -SSBS BTYPE=--) pc : native_queued_spin_lock_slowpath+0x358/0x418 lr : jbd2_log_do_checkpoint+0x31c/0x438 [jbd2] Call trace: native_queued_spin_lock_slowpath+0x358/0x418 jbd2_log_do_checkpoint+0x31c/0x438 [jbd2] __jbd2_log_wait_for_space+0xfc/0x2f8 [jbd2] add_transaction_credits+0x3bc/0x418 [jbd2] start_this_handle+0xf8/0x560 [jbd2] jbd2__journal_start+0x118/0x228 [jbd2] __ext4_journal_start_sb+0x110/0x188 [ext4] ext4_do_writepages+0x3dc/0x740 [ext4] ext4_writepages+0xa4/0x190 [ext4] do_writepages+0x94/0x228 __writeback_single_inode+0x48/0x318 writeback_sb_inodes+0x204/0x590 __writeback_inodes_wb+0x54/0xf8 wb_writeback+0x2cc/0x3d8 wb_do_writeback+0x2e0/0x2f8 wb_workfn+0x80/0x2a8 process_one_work+0x178/0x3e8 worker_thread+0x234/0x3b8 kthread+0xf0/0x108 ret_from_fork+0x10/0x20 So explicitly call cond_resched() in jbd2_log_do_checkpoint() to avoid softlockup. | 19 Oct |
| CVE-2025-39725 | 5.5 medium | 0.00% | linux, linux_kernel | In the Linux kernel, the following vulnerability has been resolved: mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list In shrink_folio_list(), the hwpoisoned folio may be large folio, which can't be handled by unmap_poisoned_folio(). For THP, try_to_unmap_one() must be passed with TTU_SPLIT_HUGE_PMD to split huge PMD first and then retry. Without TTU_SPLIT_HUGE_PMD, we will trigger null-ptr deref of pvmw.pte. Even we passed TTU_SPLIT_HUGE_PMD, we will trigger a WARN_ON_ONCE due to the page isn't in swapcache. Since UCE is rare in real world, and race with reclaimation is more rare, just skipping the hwpoisoned large folio is enough. memory_failure() will handle it if the UCE is triggered again. This happens when memory reclaim for large folio races with memory_failure(), and will lead to kernel panic. The race is as follows: cpu0 cpu1 shrink_folio_list memory_failure TestSetPageHWPoison unmap_poisoned_folio --> trigger BUG_ON due to unmap_poisoned_folio couldn't handle large folio [[email protected]: add comment to unmap_poisoned_folio()] | 19 Oct |
| CVE-2025-58276 | 5.5 medium | 0.00% | huawei, emui, harmonyos | Permission verification vulnerability in the home screen module Impact: Successful exploitation of this vulnerability may affect availability. | 18 Oct |
| CVE-2025-58303 | 5.5 medium | 0.00% | huawei, harmonyos | UAF vulnerability in the screen recording framework module. Impact: Successful exploitation of this vulnerability may affect availability. | 18 Oct |
| CVE-2025-64314 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the memory management module. Impact: Successful exploitation of this vulnerability may affect confidentiality. | 18 Oct |
| CVE-2025-58302 | 5.5 medium | 0.00% | huawei, emui, harmonyos | Permission control vulnerability in the Settings module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | 18 Oct |
| CVE-2024-57977 | 5.5 medium | 0.00% | linux, linux_kernel | In the Linux kernel, the following vulnerability has been resolved: memcg: fix soft lockup in the OOM process A soft lockup issue was found in the product with about 56,000 tasks were in the OOM cgroup, it was traversing them when the soft lockup was triggered. watchdog: BUG: soft lockup - CPU#2 stuck for 23s! [VM Thread:1503066] CPU: 2 PID: 1503066 Comm: VM Thread Kdump: loaded Tainted: G Hardware name: Huawei Cloud OpenStack Nova, BIOS RIP: 0010:console_unlock+0x343/0x540 RSP: 0000:ffffb751447db9a0 EFLAGS: 00000247 ORIG_RAX: ffffffffffffff13 RAX: 0000000000000001 RBX: 0000000000000000 RCX: 00000000ffffffff RDX: 0000000000000000 RSI: 0000000000000004 RDI: 0000000000000247 RBP: ffffffffafc71f90 R08: 0000000000000000 R09: 0000000000000040 R10: 0000000000000080 R11: 0000000000000000 R12: ffffffffafc74bd0 R13: ffffffffaf60a220 R14: 0000000000000247 R15: 0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f2fe6ad91f0 CR3: 00000004b2076003 CR4: 0000000000360ee0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: vprintk_emit+0x193/0x280 printk+0x52/0x6e dump_task+0x114/0x130 mem_cgroup_scan_tasks+0x76/0x100 dump_header+0x1fe/0x210 oom_kill_process+0xd1/0x100 out_of_memory+0x125/0x570 mem_cgroup_out_of_memory+0xb5/0xd0 try_charge+0x720/0x770 mem_cgroup_try_charge+0x86/0x180 mem_cgroup_try_charge_delay+0x1c/0x40 do_anonymous_page+0xb5/0x390 handle_mm_fault+0xc4/0x1f0 This is because thousands of processes are in the OOM cgroup, it takes a long time to traverse all of them. As a result, this lead to soft lockup in the OOM process. To fix this issue, call 'cond_resched' in the 'mem_cgroup_scan_tasks' function per 1000 iterations. For global OOM, call 'touch_softlockup_watchdog' per 1000 iterations to avoid this issue. | 15 Oct |
| CVE-2025-54654 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the Gallery module. Successful exploitation of this vulnerability may affect service confidentiality | 8 Oct |
| CVE-2025-58277 | 5.5 medium | 0.00% | huawei, harmonyos | Permission verification bypass vulnerability in the Camera app. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58278 | 5.5 medium | 0.00% | huawei, harmonyos | Identity authentication bypass vulnerability in the Gallery app. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58282 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the camera module. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58283 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the Wi-Fi module. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58284 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the network module. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58285 | 5.5 medium | 0.00% | huawei, harmonyos | Permission control vulnerability in the media module. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58286 | 5.5 medium | 0.00% | huawei, harmonyos | Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58287 | 5.5 medium | 0.00% | huawei, harmonyos | Use After Free (UAF) vulnerability in the office service. Successful exploitation of this vulnerability may affect service confidentiality. | 8 Oct |
| CVE-2025-58288 | 5.5 medium | 0.00% | huawei, harmonyos | Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58290 | 5.5 medium | 0.00% | huawei, harmonyos | Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58291 | 5.5 medium | 0.00% | huawei, harmonyos | Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58292 | 5.5 medium | 0.00% | huawei, harmonyos | Denial of service (DoS) vulnerability in the office service. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58295 | 5.5 medium | 0.00% | huawei, harmonyos | Buffer overflow vulnerability in the development framework module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58297 | 5.5 medium | 0.00% | huawei, harmonyos | Buffer overflow vulnerability in the sensor service. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58298 | 5.5 medium | 0.00% | huawei, harmonyos | Data processing error vulnerability in the package management module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
| CVE-2025-58299 | 5.5 medium | 0.00% | huawei, harmonyos | Use After Free (UAF) vulnerability in the storage management module. Successful exploitation of this vulnerability may affect availability. | 8 Oct |
50 of 73 · Next
Download these 73 as CSV · subscribe to this list.
EPSS scores: 2026-10-27. NVD cursor: 2026-10-28 19:18. The News page shows only notable CVEs (KEV, your stack, new criticals, EPSS over 50%, or active exploitation per SSVC); this table has all of them.