Export limit exceeded: 30001 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429072 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429072 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-98075 | 1 Linux | 1 Linux Kernel | 2026-11-18 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: bpf: reject BPF_PSEUDO_FUNC reference to the main program fixups.c:jit_subprogs() rewrites BPF_PSEUDO_FUNC loads to contain real function addresses. This function is invoked from bpf_jit_subprogs() only when env->subprog_cnt > 1. Meaning that for any program like below: int main(void *ctx) { void *ptr = main; ... bpf_timer_set_callback(..., ptr); ... } The 'ptr' won't be ever converted to contain an address. In combination with e.g. bpf_timer_set_callback() this would lead to a function call at a bogus address. Instead of complicating the implementation, just assume that no useful program needs main to be a sync or async callback and reject BPF_PSEUDO_FUNC loads for the main subprogram. | ||||
| CVE-2026-98076 | 1 Linux | 1 Linux Kernel | 2026-11-18 | 7.8 High |
| In the Linux kernel, the following vulnerability has been resolved: tracing/probes: Fix use-after-free on field name/type of events with multiple probes The fields of a probe-based dynamic event (kprobe, uprobe, eprobe and fprobe events) are created in traceprobe_define_arg_fields() by handing the probe_arg name/type strings to trace_define_field(), which only stores the pointers without copying. Those strings are owned by the trace_probe and are freed when that probe is removed. An event can have several probes attached. The field list is defined only once, by the first probe that registers the event, but it is kept alive by any surviving sibling probe. Deleting just that first probe by symbol - # primary A: fields are defined from A's args echo 'p:kprobes/ev vfs_read a1=$arg1' > kprobe_events # append B: shares A's event call echo 'p:kprobes/ev vfs_write a1=$arg1' >> kprobe_events # delete only A (matched by symbol), B survives echo '-:kprobes/ev vfs_read' >> kprobe_events frees A's args (trace_probe_cleanup() -> traceprobe_free_probe_arg()), but trace_probe_unlink() keeps the trace_probe_event because the probe list is not empty. The event call stays registered via B while its fields now reference freed memory. Any field lookup then reads it, e.g. echo 'a1 == 1' > events/kprobes/ev/filter BUG: KASAN: slab-use-after-free in strcmp+0xa7/0xb0 Call Trace: strcmp trace_find_event_field parse_pred process_preds create_filter apply_event_filter event_filter_write field->name references parg->name (kstrdup'd, freed with the probe) and, for array arguments, field->type references parg->fmt (kmalloc'd, freed with the probe) - the scalar type otherwise points at the static fmttype rodata, which is safe. Have traceprobe_define_arg_fields() duplicate the name and type strings and anchor the copies on the trace_probe_event, which embeds the event call and outlives every individual probe; trace_probe_event_free() releases them. The reproducer above triggers reliably; the field lookup and the delete both run under event_mutex, so this is a dangling reference after removal rather than a race. The issue was found by the autokbug dynamic kernel fuzzer at Tencent Yunding Lab. | ||||
| CVE-2026-131031 | 1 Google | 1 Chrome | 2026-11-18 | 9.6 Critical |
| Out of bounds write in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical) | ||||
| CVE-2026-131057 | 1 Google | 1 Chrome | 2026-11-18 | 9.6 Critical |
| Out of bounds read in ANGLE in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131021 | 1 Google | 1 Chrome | 2026-11-18 | 8.8 High |
| Use after free in Accessibility in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131022 | 1 Google | 1 Chrome | 2026-11-18 | 8.8 High |
| Use after free in DOM in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131025 | 1 Google | 1 Chrome | 2026-11-18 | 9.6 Critical |
| Out of bounds read in ANGLE in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-61689 | 1 Xwiki | 1 Xwiki-platform | 2026-11-18 | N/A |
| XWiki Platform is a generic wiki platform. From 4.3-milestone-1 until 16.10.18, 17.10.5, and 18.2.0, the /rest/wikis/{wikiName}/query REST endpoint permits HQL query construction that can combine blind conditions with FROM-clause injection to join BaseObject and StringProperty, bypassing the SELECT-column whitelist. An unauthenticated attacker can recover database values from inaccessible pages, including salted SHA1 password hashes and passwords stored in configuration properties. It should be assumed that, with more complex techniques, this can work even when the attacker cannot read any wiki page. A typical password hash may require roughly 800 requests, and expensive injected queries can also degrade availability. The issue is remediated by disabling HQL and XWQL REST queries by default. This issue is fixed in versions 16.10.18, 17.10.5, and 18.2.0. | ||||
| CVE-2026-132124 | 1 Modified-shop | 1 Modified Ecommerce Shopsoftware | 2026-11-18 | 4.8 Medium |
| modified eCommerce Shopsoftware through 3.3.0 contains a stored cross-site scripting vulnerability that allows authenticated administrators to inject scripts via the orders_status_name parameter in admin/orders_status.php. Attackers with per-page order status access can store payloads that execute in other administrators' browsers when the unencoded status name is displayed. | ||||
| CVE-2026-132125 | 1 Weblate | 1 Weblate | 2026-11-18 | 3.3 Low |
| Weblate 5.0 through 2026.11.2 contains a privilege escalation vulnerability where deleting a component list leaves stale Group.projects rows, widening team scope to whole projects. A user with componentlist.edit who deletes a list grants 'From component list' team members their full role, including project.edit, across possibly private projects. | ||||
| CVE-2026-131039 | 1 Google | 1 Chrome | 2026-11-18 | 8.3 High |
| Use after free in Mojo in Google Chrome on on Windows prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131104 | 1 Google | 1 Chrome | 2026-11-18 | 4.7 Medium |
| Out of bounds read in Tint in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-131019 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Information leak in ANGLE in Google Chrome on on Windows prior to 158.0.8127.36 allowed a remote attacker to obtain cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-131026 | 1 Google | 1 Chrome | 2026-11-18 | 4.3 Medium |
| Information leak in Media in Google Chrome prior to 158.0.8127.36 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-131072 | 1 Google | 1 Chrome | 2026-11-18 | 6.5 Medium |
| Incorrect authorization in HID in Google Chrome prior to 158.0.8127.36 allowed a remote attacker leveraging social engineering to leak sensitive information via a crafted HTML page. (Chromium security severity: Low) | ||||
| CVE-2026-130749 | 1 Getgrav | 1 Grav | 2026-11-18 | 7.5 High |
| Grav from 2.0.0 before 2.2.18 contains a resource exhaustion vulnerability that allows unauthenticated attackers to fill the disk by varying the HTTP Host header. Attackers can send requests with distinct Host values to create per-host compiled configuration, blueprint, language and page index caches, causing session, upload and logging failures. | ||||
| CVE-2026-130746 | 1 Getgrav | 1 Grav | 2026-11-18 | 7.5 High |
| Grav before 1.7.53.7 and 2.x before 2.2.18 serves page media files, and rendered pages when lazy sessions are enabled, with the visitor's session cookie and a shared-cacheable Cache-Control header. When a shared cache such as Apache mod_cache stores Set-Cookie responses, an attacker can lure a user signed in through the front-end login to open a media URL with a unique query string, then request that URL to receive the cached session cookie and take over the session. | ||||
| CVE-2026-130745 | 1 Getgrav | 1 Grav | 2026-11-18 | 5.9 Medium |
| Grav from 2.0.0 before 2.2.18 contains an access control bypass vulnerability that allows anonymous visitors to read protected pages because admin and site scopes share a page cache key. Routine editor activity through the API plugin rebuilds the page index without frontmatter.yaml access rules, exposing members-only page content until the cache is rebuilt. | ||||
| CVE-2026-130742 | 1 Getgrav | 1 Grav | 2026-11-18 | 8.8 High |
| Grav 2.0.0 before 2.2.18 resolves Flex sort and filter field names by first calling them as public methods, so a field named delete invokes FlexObject::delete() without any permission check. Authenticated users with only list access can send GET /api/v1/flex-objects/user-accounts?sort=delete requests to delete every account, then use the reopened API first-run setup to create a super admin. | ||||
| CVE-2026-130741 | 1 Getgrav | 1 Grav | 2026-11-18 | 8.8 High |
| Grav from 2.0.0 before 2.2.18 contains a Twig sandbox bypass vulnerability that allows publishers to read any server file by abusing allowlisted array_key_value() and page accessor setters such as filePath(). Attackers can repoint page objects or overwrite the assets collections to render private keys and the API signing secret, then forge a super-admin API token. | ||||