Export limit exceeded: 429927 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429929 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429942 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-76415 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the Yoda'a Crytper (yC) Portable Executable (PE) unpacker of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. . This vulnerability is due to lack of proper error checking for negative values when processing the PE file to be unpacked. An attacker could exploit this vulnerability by sending a PE file to be unpacked. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. | ||||
| CVE-2026-76416 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the InstallShield file parser of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to incomplete error checking when the InstallShield File Parser is performing a scan. An attacker could exploit this vulnerability by sending a crafted InstallShield file to be scanned. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate due to an infinite loop, resulting in a DoS condition on the affected software. | ||||
| CVE-2026-76421 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the LZX data algorithm for Microsoft Compiled HTML Help (CHM) file scanning in ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper boundary checks when applying the LZX data algorithm to CHM files during the decoder stage, which may result in buffer overflow. An attacker could exploit this vulnerability by sending a crafted CHM file for scanning. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. | ||||
| CVE-2026-76422 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the debug logging functionality of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper handling of logging values. An attacker could exploit this vulnerability by submitting a file to be scanned by the software that has debug logging enabled. A successful exploit could allow the attacker to cause the ClamAV scanning process to terminate, resulting in a DoS condition on the affected software. | ||||
| CVE-2026-76430 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the Ultimate Packer for eXecutables (UPX) unpacker of ClamAV could allow an unauthenticated, remote attacker to cause a DoS condition on an affected device. This vulnerability is due to improper length checks, when unpacking the UPX files, which may result in an out-of-bounds read of heap memory. An attacker could exploit this vulnerability by submitting a crafted UPX for decode. A successful exploit could allow the attacker to cause the ClamAV decode process to terminate, resulting in a DoS condition on the affected software. | ||||
| CVE-2026-76515 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the Object Linking and Embedding, 2nd Generation (OLE2) file parser for ClamAV could allow an unauthenticated, remote attacker to exceed the configured MaxScanTime and cause a DoS condition on an affected device. This vulnerability is due to inefficiencies when parsing specifically formatted files with the OLE2 file parser. An attacker could exploit this vulnerability by by sending a crafted Microsoft Compound File Binary (CFB) file to be scanned. A successful exploit could allow the attacker to effectively cause the ClamAV OLE2 parser to get into an infinite loop, resulting in a DoS condition on the affected software. | ||||
| CVE-2026-76516 | 1 Cisco | 1 Secure Endpoint | 2026-11-20 | 7.5 High |
| A vulnerability in the eXtensible ARchive (XAR) GZIP file parser for ClamAV could allow an unauthenticated, remote attacker to exceed the configured MaxFileSize and cause a DoS condition on an affected device. This vulnerability is due to inefficiencies when parsing specifically formatted files with the XAR GZIP file parser. An attacker could exploit this vulnerability by by sending a crafted XAR GZIP file to be scanned. A successful exploit could allow the attacker to effectively cause the ClamAV to exceed the MaxFileSize and potentially get caught in an infinite loop, causing a DoS condition. | ||||
| CVE-2026-116441 | 1 Dell | 12 Powerstore 1000t, Powerstore 1200t, Powerstore 3000t and 9 more | 2026-11-20 | 9.6 Critical |
| Dell PowerStore SDNAS contains an out-of-bounds write vulnerability in the storage-processor interconnect driver that could allow a malicious peer to execute code with system privileges. | ||||
| CVE-2026-132896 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.2 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4 remote code execution was possible via Kubernetes Executor settings | ||||
| CVE-2026-132901 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.7 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 improper authorization allowed publishing packages to NuGet feeds of other projects | ||||
| CVE-2026-132904 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.1 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 missing authorization allowed project viewers to remove VCS roots | ||||
| CVE-2026-132906 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.8 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via native code loading in the Kotlin DSL sandbox | ||||
| CVE-2026-132910 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.5 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 unauthenticated DoS via the agent protocol was possible | ||||
| CVE-2026-132920 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.3 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 an SSRF via connection tests was possible for users without project edit permissions | ||||
| CVE-2026-132921 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2 two-factor authentication bypass was possible via access token management | ||||
| CVE-2026-132922 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 stored XSS in the unified diff page syntax highlighting was possible | ||||
| CVE-2026-132924 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.4 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 improper authorization allowed users with the Run build permission to delete Perforce workspaces | ||||
| CVE-2026-99413 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 4.4 Medium |
| In the Linux kernel, the following vulnerability has been resolved: xfs: fix buffer overruns in xfs_ioc_attr_list When we converted the al_offset array in struct xfs_attrlist into a VLA, the size of the object shrank by 4 bytes. Unfortunately, the buffer size validation in the attrlist ioctl wasn't updated to notice this, so the al_offset[0] assignment blindly writes off the end of the buffer. LOLLM noticed the omitted check and complained. | ||||
| CVE-2026-99414 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 3.3 Low |
| In the Linux kernel, the following vulnerability has been resolved: ovl: skip copy up of empty security.capability ovl_copy_xattr() gives up if it can't read an attribute that listxattr() has named. An empty security.capability, which anybody has been able to store on any file for a long time, is such a case: it is listed, and getxattr() has nothing to return for it. A file in a lower layer that carries one can't be copied up: it can't be written to, renamed or have its mode changed. There is nothing to copy if there are no data. Go on with the next one. [amir: treat -EINVAL as no capability too, and do the same in ovl_copy_up_meta_inode_data()] | ||||
| CVE-2026-99415 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 2.5 Low |
| In the Linux kernel, the following vulnerability has been resolved: ovl: set the revalidate flags after d_instantiate() stat() of a file on an overlayfs mount triggers a kernel warning and fails with ECHILD if another task is creating that file at the same time. This happens on an overlay with a FUSE upper layer, which is the layer where overlayfs creates new files. Write access to a directory on such an overlay is all a user needs to run the two tasks. The revalidate flags are DCACHE_OP_REVALIDATE and DCACHE_OP_WEAK_REVALIDATE. They tell path walk to call ->d_revalidate() or ->d_weak_revalidate() on a dentry, so that the filesystem can check that the cached dentry is still valid. An overlay dentry only has one of these flags if a dentry in one of its layers has it. FUSE dentries have the first one. When a flag is set on an overlay dentry, path walk calls ovl_dentry_revalidate_common(). That function only expects a dentry without an inode in RCU walk, while the dentry is being destroyed. For such a dentry outside of RCU walk, it hits a WARN_ON() and returns -ECHILD. So a negative overlay dentry must never have the flags set. ovl_instantiate() breaks this rule. When a task creates a file, the overlay dentry for the new name is hashed but still negative. ovl_instantiate() then works in this order: - It copies the flags from the new upper dentry to the overlay dentry. - It calls ovl_get_inode(), which can sleep in a getxattr request to the FUSE server. - Only then does it call d_instantiate(). A second task that looks up the name between the first step and the last finds a negative dentry with the flags set and revalidates it. Reproduced with a FUSE server that delays its getxattr reply: stat() of a name that was being created hit the WARN_ON() and failed with ECHILD. Fix this by setting the flags after d_instantiate(). | ||||