Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 429303 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429303 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-99335 | 1 Linux | 1 Linux Kernel | 2026-11-19 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: KVM: guest_memfd: Establish memslot<=>guest_memfd bindings *after* memslot is ready Wait to bind a memslot to a guest_memfd instance until *after* the memslot is fully prepared, as creating the binding in guest_memfd will effectively expose the memslot to readers. As pointed out by Sashiko, binding the memslot before it's ready to be exposed to the rest of the world can break various memslot assumption and rules. E.g. x86 could observe a NULL rmap pointer if a PUNCH_HOLE hit the guest_memfd after the binding was created, but before KVM made it through kvm_prepare_memory_region(). | ||||
| CVE-2026-99334 | 1 Linux | 1 Linux Kernel | 2026-11-19 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: KVM: PPC: Book3S HV: Add preempt_disable() around virtual-mode HPTE bit-lock users kvmppc_hv_find_lock_hpte() requires virtual-mode callers to run with preemption disabled, because it can return with HPTE_V_HVLOCK still held until the caller later unlocks the HPTE. Existing virtual-mode callers in book3s_64_mmu_hv.c already follow that rule. Two virtual-mode call paths do not: 1. kvmppc_handle_exit_hv() calls kvmppc_hpte_hv_fault() for hash-mode data-side and instruction-side faults after guest exit, with preemption already enabled. kvmppc_hpte_hv_fault() calls kvmppc_hv_find_lock_hpte() directly. 2. kvmppc_pseries_do_hcall() executes virtual-mode handlers for HPT hcalls via kvmppc_pseries_do_hpt_hcall() with preemption enabled. The handlers for H_ENTER, H_REMOVE, H_READ, H_CLEAR_MOD, H_CLEAR_REF, H_PROTECT, and H_BULK_REMOVE spin on try_lock_hpte() or lock_rmap(), and H_ENTER also reaches kvmppc_do_h_enter(), which uses arch_spin_lock() on kvm->mmu_lock. That raw lock choice is intentional because kvmppc_do_h_enter() is also used by real-mode callers, so the correct fix is to establish the proper preemption context at the virtual-mode caller boundary. If a vCPU thread is preempted while holding HPTE_V_HVLOCK, any other thread on the same CPU trying to acquire the same bit-lock can spin indefinitely. The same applies to lock_rmap() users and to the H_ENTER path while holding the raw mmu_lock. Fix this by adding preempt_disable()/preempt_enable() pairs around the two kvmppc_hpte_hv_fault() call sites in kvmppc_handle_exit_hv(), and around the kvmppc_pseries_do_hpt_hcall() invocation in kvmppc_pseries_do_hcall(). Targeting only the HPT hcall helper avoids wrapping non-HPT hcalls (such as H_RTAS, H_CONFER, H_REGISTER_VPA) that perform page faults, blocking memory allocations, or context switches. | ||||
| CVE-2026-99333 | 1 Linux | 1 Linux Kernel | 2026-11-19 | N/A |
| In the Linux kernel, the following vulnerability has been resolved: HID: amd_sfh: Use report type from request node Use report type from request node while sending feature and input reports to HID core. The cli_data report type array is never assigned and feature reports are sent as input reports. | ||||
| CVE-2026-133086 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 8.8 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via a URL stream handler in the Kotlin DSL sandbox | ||||
| CVE-2026-99285 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-19 | 5.5 Medium |
| In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_byteorder: remove multi-register support 64bit byteorder conversion is broken when several registers need to be converted because the source register array advances in steps for 4 bytes instead of 8: for (i = ... src64 = nft_reg_load64(&src[i]); ~~~~~ u32 *src nft_reg_store64(&dst64[i], Remove the multi-register support, it has other issues as well: Pablo points out that commit caf3ef7468f7 ("netfilter: nf_tables: prevent OOB access in nft_byteorder_eval") alters semantics: before the loop operated on registers, i.e. for ( ... ) dst32[i] = htons((u16)src32[i]) .. but after the patch it will operate on bytes, which makes this useless to convert e.g. concatenations, which store each compound in its own register. Multi-convert of u32 has one theoretical application: ct mark . meta mark . tcp dport @intervalset Because ct mark and meta mark are host byte order, use with intervals has to convert the byteorder for ct/meta mark value to network byte order (bigendian). nftables emits this: [ meta load mark => reg 1 ] [ byteorder reg 1 = hton(reg 1, 4, 4) ] [ ct load mark => reg 9 ] [ byteorder reg 9 = hton(reg 9, 4, 4) ] ... I.e. two separate calls. Theoretically it could be changed to do: [ meta load mark => reg 1 ] [ ct load mark => reg 9 ] [ byteorder reg 1 = htonl(reg 1, 4, 8) ] ... But then all it would take to change the set to meta mark . tcp dport . ct mark ... and we'd be back to two "byteorder" calls. IOW, support to convert a range of registers is both dysfunctional and dubious. Simplify this: remove the feature. Pablo Neira Ayuso points out that nftables before 1.1.0 can generate incorrect byteorder conversions, see 9fe58952c45a, "evaluate: skip byteorder conversion for selector smaller than 2 bytes" in nftables.git). Affected rulesets fail to load with this change and old userspace due to 'len != size' check. | ||||
| CVE-2026-133161 | 2026-11-19 | 7.5 High | ||
| ### Summary ui With `strip_ansi=True`, Pydantic AI Harness's `ToolOutputLimits` capability removes ANSI escape sequences from tool output with a pattern that takes time quadratic in the length of a line. A tool result of a few hundred kilobytes, crafted with many unterminated escape sequences, can occupy the event loop for tens of seconds to minutes, delaying every other request and agent run in the process. ### Details This affects applications that set `strip_ansi=True` on `ToolOutputLimits` (named `OverflowingToolOutput` before 0.13.0) and run tools whose output an attacker can influence, such as shell commands, file reads, fetched pages or MCP servers. Stripping runs on the event loop before the capability reduces the output, so its own size limits do not bound it. The assumed attacker can place text in content a tool returns. ### Mitigation Upgrade `pydantic-ai-harness` to 0.70.0 or later. Until then, leave `strip_ansi` at its default, `False`. On Pydantic AI v1, the harness cannot be upgraded past 0.4.0. Upgrade to Pydantic AI v2 and `pydantic-ai-harness` 0.70.0, or leave `strip_ansi` off. | ||||
| CVE-2026-133182 | 2026-11-19 | 5.5 Medium | ||
| In JetBrains IntelliJ IDEA before 2026.3 the GitHub plugin exposed GitHub access tokens via its public API | ||||
| CVE-2026-133180 | 2026-11-19 | 3.7 Low | ||
| In JetBrains ReSharper before 2026.3 the What's New feature did not verify server certificates | ||||
| CVE-2026-133179 | 2026-11-19 | 3.6 Low | ||
| In JetBrains Rider before 2026.3 code execution was possible via MSBuild configuration files in parent directories | ||||
| CVE-2026-133183 | 1 Misp | 1 Misp | 2026-11-19 | N/A |
| MISP contains an authorization flaw in the handling of remote pull and feed operations. When a non-internal pull or a feed processes incoming data and encounters an existing sharing group, the application did not verify that the remote server's organization was actually a member of that sharing group before allowing the group's metadata to be updated. The captureRemote mechanism previously stored only a boolean flag indicating whether the link was internal, and the authorization check in captureSGExisting relied solely on that flag. For non-internal pulls and feeds, the check was insufficient: a remote server whose organization was not a member of the target sharing group could still cause the group record to be modified (for example, altering the local flag, the modified timestamp, or other group properties). A feed, which has no associated server organization at all, could likewise trigger an update to an existing sharing group's metadata. The security impact is an integrity violation: an authenticated remote entity with sync or feed privileges can alter sharing group attributes that govern how data is distributed among organizations, potentially changing the local flag or other access-relevant properties of groups it does not belong to. The vulnerability requires an authenticated user with the ability to initiate a pull or feed (a sync user or feed administrator) and a target sharing group that exists on the local instance. No unauthenticated access or user interaction is required. | ||||
| CVE-2026-128666 | 1 Phpgurukul | 1 News Portal Project | 2026-11-19 | 6.1 Medium |
| A Reflected Cross-Site Scripting (XSS) vulnerability exists in PHPGurukul News Portal Project V4.1. The $currenturl variable in news-details.php is constructed using unencoded REQUEST_URI and HTTP_HOST server variables and echoed directly into the href attributes of social share links. An unauthenticated remote attacker can exploit this by crafting a URL containing HTML metacharacters to break out of the href attribute and execute arbitrary HTML or JavaScript in the context of the victim's browser. | ||||
| CVE-2026-128660 | 1 Phpgurukul | 1 Beauty Parlour Management System | 2026-11-19 | 4.8 Medium |
| PHPGurukul Beauty Parlour Management System V 1.1 is vulnerable to Cross Site Scripting (XSS) in admin/search-invoices.php via the searchdata parameter. | ||||
| CVE-2026-133167 | 1 Offis | 1 Dcmtk | 2026-11-19 | 5.5 Medium |
| OFFIS DCMTK 3.5.4 through 3.7.1 contains an integer overflow in DJCodecEncoder::encodeTrueLossless size checks that allows attackers to trigger a heap out-of-bounds read. Attackers can supply a crafted DICOM file with large Columns, Rows and SamplesPerPixel values that, when compressed with true-lossless JPEG, crashes the application. | ||||
| CVE-2026-133168 | 1 Offis | 1 Dcmtk | 2026-11-19 | 7.8 High |
| OFFIS DCMTK 3.7.1 contains a heap buffer overflow vulnerability in togglePlanarConfiguration8 and togglePlanarConfiguration16 in djcodece.cc, which compute row offsets using rows instead of columns. Attackers can supply a crafted color-by-plane DICOM image with more rows than columns that is compressed with the true-lossless JPEG codec to corrupt heap memory, causing crashes and potentially code execution. | ||||
| CVE-2026-133169 | 1 Modified-shop | 1 Modified Ecommerce Shopsoftware | 2026-11-19 | 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 unsanitized products_model field. Attackers with product editing permission can store JavaScript that executes in browsers of other administrators, storefront visitors, and customers viewing carts and order history. | ||||
| CVE-2026-133170 | 2026-11-19 | 4.7 Medium | ||
| Tiptap @tiptap/core 2.0.0-alpha.0 before 3.30.4 contains a cross-site scripting vulnerability that allows attackers to inject DOM attributes via a __proto__ key passed to mergeAttributes(). Attackers can supply untrusted JSON attribute data whose __proto__ replaces the merged object's prototype, causing DOMSerializer.renderSpec to render injected event handlers that execute JavaScript. | ||||
| CVE-2026-133171 | 2026-11-19 | 5.3 Medium | ||
| Tiptap @tiptap/core 3.7.0 before 3.30.5 contains a regular expression denial of service vulnerability in parseAttributes and parseShortcodeAttributes that allows attackers to exhaust CPU through quadratic backtracking. Attackers can supply Markdown with long crafted attribute strings parsed by createBlockMarkdownSpec, createAtomBlockMarkdownSpec or createInlineMarkdownSpec to stall browser pages or server processes. | ||||
| CVE-2026-133172 | 2026-11-19 | 8.8 High | ||
| Cozy Cloud cozy-stack 1.6.62 before 1.6.69 contains an authorization bypass vulnerability in the shared-drive move handler that allows authenticated users to access other instances' files. Attackers owning a shared drive can name another instance's domain and any directory ID as the move source to copy and delete the victim's file tree. | ||||
| CVE-2026-133174 | 2026-11-19 | 4.3 Medium | ||
| HotGo 2.18.6 through 2.19.0 contains an information disclosure vulnerability that allows authenticated backend users to read other administrators' private letters because the messageIds helper omits the receiver filter. Low-privilege users can call GET /admin/notice/pullMessages, which is exempt from role permission checks via exceptAuth, to retrieve titles, contents and senders of private letters. | ||||
| CVE-2026-133092 | 1 Jetbrains | 1 Teamcity | 2026-11-19 | 8.8 High |
| In JetBrains TeamCity before 2026.2.2, 2026.1.6 remote code execution was possible via Git submodule URLs | ||||