Export limit exceeded: 430139 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430139 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430139 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430139 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430139 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430139 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-132903 | 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 any authenticated user to start and stop cloud agent instances | ||||
| CVE-2026-132905 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.6 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the AWS Credentials build feature was possible | ||||
| CVE-2026-132908 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.5 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via Mercurial VCS root settings | ||||
| CVE-2026-132912 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.2 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 remote code execution was possible via class injection in the Kotlin DSL sandbox | ||||
| CVE-2026-132913 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.4 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the P4 Code Review build tab was possible | ||||
| CVE-2026-132914 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Issue Log tab was possible | ||||
| CVE-2026-132916 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.1 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 arbitrary file deletion on the server was possible via the Kotlin DSL sandbox | ||||
| CVE-2026-132917 | 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 a file write bypass in the Kotlin DSL sandbox | ||||
| CVE-2026-132918 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.6 High |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on build and queue pages was possible | ||||
| CVE-2026-132923 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in SSH key management was possible | ||||
| CVE-2026-132926 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.2 Medium |
| In JetBrains TeamCity before 2026.2 poisoning of OAuth discovery metadata via the X-Forwarded-Host header was possible | ||||
| CVE-2026-132936 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.4 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the npm connection health report was possible | ||||
| CVE-2026-132963 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.4 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the checkout rules path preview was possible | ||||
| CVE-2026-132965 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the unknown VCS root page was possible | ||||
| CVE-2026-133023 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.2 High |
| In JetBrains TeamCity before 2026.2.1, 2026.1.5 remote code execution was possible via Kotlin DSL compiler arguments | ||||
| CVE-2026-116440 | 1 Dell | 15 Powerstore 1000t, Powerstore 1200t, Powerstore 1500 and 12 more | 2026-11-20 | 9.8 Critical |
| Dell PowerStore SDNAS contains a buffer overflow vulnerability that could allow an unauthenticated remote attacker to cause a denial of service or potential code execution on the NAS node. | ||||
| CVE-2026-116439 | 1 Dell | 15 Powerstore 1000t, Powerstore 1200t, Powerstore 1500 and 12 more | 2026-11-20 | 9.8 Critical |
| Dell PowerStore SDNAS contains a path traversal vulnerability that could allow an unauthenticated attacker to read, modify, or delete arbitrary files on the NAS node. | ||||
| CVE-2026-115342 | 1 Openvpn | 1 Openvpn | 2026-11-20 | N/A |
| Argument injection in OpenVPN version 2.4.0 through 2.6.23 and 2.7_alpha1 through 2.7.8 on Windows allows local authenticated users to bypass interactive service option validation and add arbitrary configuration options via a crafted command line. | ||||
| CVE-2026-99732 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: mm/filemap: read mapping->a_ops->free_folio under i_lock memory_failure() -> ... -> filemap_remove_folio() can read mapping->a_ops after the inode has been freed. Once the folio is deleted from the pagecache it no longer pins the mapping, so after i_lock is dropped e.g., a concurrent final iput() can evict and free the inode before filemap_free_folio() looks up mapping->a_ops->free_folio. Most callers hold a reference on the inode, but not all. Documentation/filesystems/vfs.rst explicitly states that ->free_folio() must not assume the original address_space mapping still exists. Fix it by loading ->free_folio while i_lock is still held, similar to what folio_unmap_invalidate() does. Inline filemap_free_folio() into its remaining caller such that delete_from_page_cache_batch() also just loads the callback before dropping the i_lock. The bug was found by code inspection and has not been reproduced. Fix generated by an LLM and sent by Josef Bacik in private. [ david: get rid of filemap_free_folio() entirely; improve patch description ] | ||||
| CVE-2026-99733 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 4.7 Medium |
| In the Linux kernel, the following vulnerability has been resolved: mm/truncate: look again if a folio left the mapping invalidate_inode_pages2_range() skips a folio which no longer belongs to the mapping by the time it has got the folio lock, on the assumption that somebody else has removed it from the page cache. But the folio may have been replaced, and then there is a new folio with the same data at that index. For most cases, like folio migration, that is impossible. However, collapse_file() only checks the refcount of the old folios, under the i_pages lock, and relies on their folio locks from there on. That works for users which repeat the lookup when they find folio->mapping changed. The following scenario is, however, possible: CPU0 pwrite(O_DIRECT) CPU1 collapse_file() kiocb_invalidate_pages() read the folio (old data), lock it refcount check the write completes copy to new_folio kiocb_invalidate_post_direct_write() find_get_entries() -> old folio xas_store(new_folio) folio->mapping = NULL folio_unlock(folio) folio_lock() folio->mapping != mapping -> continue In that scenario, the collapsed folio with the data from before the write stays in the page cache after the write has returned. This used to be impossible, as khugepaged only collapsed files that nobody had open for writing. Restart the lookup at that index, like shmem_undo_range() does. The same problem seems to exist in truncate_inode_pages_range() as well when truncate_inode_folio() fails, so handle it there as well, but slightly differently: simply check once more through find_get_entries(). | ||||