Export limit exceeded: 430143 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 430143 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430143 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-99777 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 4.4 Medium |
| In the Linux kernel, the following vulnerability has been resolved: net/9p/usbg: remove bogus context initialization in alloc_requests alloc_requests() initializes usb9pfs->in_req->context to point at the struct f_usb9pfs instance itself. usb9pfs_queue_tx() later overwrites this with the real struct p9_req_t pointer before every transmit, and usb9pfs_tx_complete() clears it back to NULL after each completion, so in_req->context only ever holds a valid p9_req_t once a request has actually been queued. usb9pfs_clear_tx(), however, can run at any time (mount close, gadget disable) independent of whether a request was ever queued. If it runs before the first usb9pfs_transmit(), it reads the leftover sentinel value, type-confuses the struct f_usb9pfs pointer as a struct p9_req_t, and both writes through it (req->t_err = -ECONNRESET) and hands it to p9_client_cb(), which manipulates req->wq and req->refcount at bogus offsets inside f_usb9pfs. This reliably corrupts memory or panics whenever the transport is torn down before any 9p request has been transmitted, e.g. mounting and immediately unmounting, or a cable disconnect racing the very first request. usb9pfs->out_req->context is set the same way but is never read by this transport (usb9pfs_rx_complete() identifies the instance via ep->driver_data instead), so it serves no purpose either. Both endpoints' ->driver_data are already set to usb9pfs in enable_endpoint(), which is what the completion handlers actually use to recover the f_usb9pfs instance. Just drop the leftover ->context assignments; usb_ep_alloc_request()/alloc_ep_req() already return zeroed requests, so in_req->context correctly starts out NULL. | ||||
| CVE-2026-131024 | 2 Apple, Google | 2 Iphone Os, Chrome | 2026-11-20 | 8.1 High |
| Incorrect authorization in iOSWeb in Google Chrome on on iOS prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-14915 | 2026-11-20 | 5.3 Medium | ||
| Exposure of sensitive system information to an unauthorized control sphere vulnerability in Tegsoft Yönetim ve Bilişim Hizmetleri Tic. Ltd. Şti. Tegsoft İletişim Merkezi allows Query System for Information. This issue affects Tegsoft İletişim Merkezi: before latest-202611161510. | ||||
| CVE-2026-133610 | 1 Antirez | 1 Gguf-tools | 2026-11-20 | 6.3 Medium |
| A vulnerability was found in antirez gguf-tools up to fdfafbed766db0a1e9019b07994cd88f133d1aab. The impacted element is the function gguf_get_tensor of the file gguflib.c of the component GGUF Parser. The manipulation of the argument offset/alignment results in out-of-bounds read. The attack can be launched remotely. The pull request to fix this issue awaits acceptance. | ||||
| CVE-2026-129074 | 2026-11-20 | 7.1 High | ||
| Missing Authorization vulnerability in miniOrange miniOrange's Google Authenticator miniorange-2-factor-authentication allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects miniOrange's Google Authenticator: from n/a through 6.6.0. | ||||
| CVE-2026-132937 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.5 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 arbitrary file write via read-write file channels in the Kotlin DSL sandbox was possible | ||||
| CVE-2026-132938 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.9 Medium |
| In JetBrains TeamCity before 2026.2 improper authorization allowed project-limited access tokens to act with full permissions via XML-RPC | ||||
| CVE-2026-132939 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.8 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS in the Maven settings health report was possible | ||||
| CVE-2026-132940 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.4 Medium |
| In JetBrains TeamCity before 2026.2 credential leakage via Mercurial subrepository URLs was possible | ||||
| CVE-2026-132941 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 4.3 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 missing authorization allowed users to remove all build configuration assignments from an agent | ||||
| CVE-2026-132942 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.3 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4 unauthenticated extraction of build parameter values via a timing attack on build status icons was possible | ||||
| CVE-2026-132943 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Log page was possible | ||||
| CVE-2026-132945 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the inspection profile selector popup was possible | ||||
| CVE-2026-132946 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.5 reflected XSS on the Test History page was possible | ||||
| CVE-2026-132947 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2 reflected XSS in Kubernetes cloud profile namespace and deployment choosers was possible | ||||
| CVE-2026-132948 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Build Chains tab was possible | ||||
| CVE-2026-132949 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS on the Clean-up Rules page was possible | ||||
| CVE-2026-132951 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 6.1 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 reflected XSS in the notification rule form was possible | ||||
| CVE-2026-132952 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.9 Medium |
| In JetBrains TeamCity before 2026.2 privilege escalation to system administrator was possible via project administrator roles in simple authorization mode | ||||
| CVE-2026-132954 | 1 Jetbrains | 1 Teamcity | 2026-11-20 | 5.4 Medium |
| In JetBrains TeamCity before 2026.2, 2026.1.4, 2025.11.8 stored XSS on the Triggers page was possible | ||||