Export limit exceeded: 430079 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430079 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-99712 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: KVM: x86: Conditionally resched when restarting REP string emulation When restarting emulation, e.g. of a REP-prefixed string instruction, conditionally reschedule as emulating guest writes can be deceptively slow and expensive, e.g. when shadow paging is in use and each write can trigger write tracking. In a perfect world, restarting emulation (or not) would be less arbitrary, e.g. would honor not only host events (NEED_RESCHED, signals, etc.) but also guest events (e.g. by checking kvm_vcpu_has_events()). Unfortunately, as pointed out by Sashiko, pio_in_emulated()'s read-ahead logic is baked into the restart logic, as KVM relies on restarting emulation to drain the cache and avoid duplicate reads from the I/O port. I.e. re-entering the guest on kvm_vcpu_has_events() or __xfer_to_guest_mode_work_pending() would introduce architecturally-incorrect, guest-visible changes. | ||||
| CVE-2026-99713 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 6.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: KVM: x86/mmu: Conditionally resched when retrying gPTE walk on A/D update failure Conditionally reschedule when retrying a guest PTE walk because the CMPXCHG to update A/D bits failed, e.g. because a different task/vCPU modified the relevant gPTEs. On kernels without involuntary preemption of some kind, a misbehaving guest can "capture" a pCPU effectively indefinitely and trigger soft lockups by continuously modifying its gPTEs such that the result of the walk is remains valid. | ||||
| CVE-2026-132231 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 9.9 Critical |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via best-fit character mapping in Perforce settings | ||||
| CVE-2026-132232 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 9.9 Critical |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Perforce settings | ||||
| CVE-2026-132233 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 9.9 Critical |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via build attribute injection | ||||
| CVE-2026-132234 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 9.9 Critical |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via argument injection in Mercurial VCS root settings | ||||
| CVE-2026-132235 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.2 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in project import archives | ||||
| CVE-2026-132237 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 8.8 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 remote code execution was possible via path traversal in the external artifact cache | ||||
| CVE-2026-132238 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.7 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.8 disclosure of password parameter values to project viewers was possible | ||||
| CVE-2026-132239 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.6 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 missing authorization in the Kubernetes integration allowed project viewers to use stored credentials | ||||
| CVE-2026-132240 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.7 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE via Maven settings file upload was possible | ||||
| CVE-2026-132241 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.3 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 XXE in the .NET build steps auto-discovery was possible | ||||
| CVE-2026-132242 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.6 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Promote build dialog was possible | ||||
| CVE-2026-132243 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 7.6 High |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS on the Docker Container Info tab was possible | ||||
| CVE-2026-132246 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.6 Medium |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 privilege escalation to system administrator was possible after disabling per-project permissions | ||||
| CVE-2026-132247 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.3 Medium |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 improper authorization allowed viewing build process details via agent stacktraces | ||||
| CVE-2026-132248 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.4 Medium |
| In JetBrains TeamCity before 2026.1.3 improper authorization allowed project viewers to change project IDs | ||||
| CVE-2026-132249 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.8 Medium |
| In JetBrains TeamCity before 2026.1.3, 2025.11.7 stored XSS in the Shared Resources build feature was possible | ||||
| CVE-2026-132250 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 3.1 Low |
| In JetBrains TeamCity before 2026.1.3 privilege escalation was possible via Basic authentication with a restricted access token | ||||
| CVE-2026-132930 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 reflected XSS in build problem details was possible | ||||