Fallos del tipo CWE-787
4554 resultadosCVE-2026-6039MEDIUMHeap buffer overflow in DXF polyline importEPSS 0.2%CVE-2025-33189HIGHNVIDIA DGX Spark GB10 contains a vulnerability in SROOT firmware, where an attacker could cause an out-of-bound write. A successful exploit EPSS 0.2%CVE-2026-22716MEDIUMVMware Workstation out-of-bounds write vulnerabilityEPSS 0.2%CVE-2019-25691HIGHFaleemi Desktop Software 1.8 Local Buffer Overflow SEH DEP BypassEPSS 0.2%CVE-2023-53372HIGHsctp: fix a potential overflow in sctp_ifwdtsn_skipEPSS 0.2%CVE-2025-59732HIGHHeap-buffer-overflow write in FFmpeg EXR dwa_uncompressEPSS 0.2%CVE-2025-59298MEDIUMFile Parsing Out-Of-Bounds Write Vulnerability in DIAScreenEPSS 0.2%CVE-2025-3154LOWOut-of-bounds array write due to invalid VerticesPerRow in Xpdf 4.05EPSS 0.2%CVE-2021-1050HIGHIn MMU_UnmapPages of the PowerVR kernel driver, there is a possible out of bounds write due to a missing bounds check. This could lead to loEPSS 0.2%CVE-2025-59297MEDIUMFile Parsing Out-Of-Bounds Write Vulnerability in DIAScreenEPSS 0.2%CVE-2025-49848HIGHOut-of-bounds Write in LS Electric GMWin 4EPSS 0.2%CVE-2021-26383HIGHInsufficient bounds checking in AMD TEE (Trusted Execution Environment) could allow an attacker with a compromised userspace to invoke a comEPSS 0.2%CVE-2025-9340NONEnative encrypt/decrypt operations in JCE may corrupt data if same byte array used for input and output.EPSS 0.2%CVE-2025-14409HIGHSoda PDF Desktop PDF File Parsing Out-Of-Bounds Write Remote Code Execution VulnerabilityEPSS 0.2%CVE-2026-27295HIGHAdobe Framemaker | Out-of-bounds Write (CWE-787)EPSS 0.2%CVE-2025-52939CRITICALPotential heap-buffer overflow vulnerability in NotepadNextEPSS 0.2%CVE-2024-36355HIGHImproper input validation in the SMM handler could allow an attacker with Ring0 access to write to SMRAM and modify execution flow for S3 (sEPSS 0.2%CVE-2025-68160MEDIUMHeap out-of-bounds write in BIO_f_linebuffer on short writesEPSS 0.2%CVE-2024-58099MEDIUMvmxnet3: Fix packet corruption in vmxnet3_xdp_xmit_frameEPSS 0.2%CVE-2026-0030HIGHIn __host_check_page_state_range of mem_protect.c, there is a possible out of bounds write due to an incorrect bounds check. This could leadEPSS 0.2%