Export limit exceeded: 430235 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (430235 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-133171 | 2026-11-20 | 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-133167 | 1 Offis | 1 Dcmtk | 2026-11-20 | 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-133180 | 1 Jetbrains | 1 Resharper | 2026-11-20 | 3.7 Low |
| In JetBrains ReSharper before 2026.3 the What's New feature did not verify server certificates | ||||
| CVE-2026-133182 | 1 Jetbrains | 1 Intellij Idea | 2026-11-20 | 5.5 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 the GitHub plugin exposed GitHub access tokens via its public API | ||||
| CVE-2026-133184 | 1 Misp | 1 Misp | 2026-11-20 | N/A |
| MISP contains an authorization and input-validation flaw in its event push mechanism. When a user with push permissions initiates a push of events to a remote MISP instance, the system fails to enforce two critical checks: (1) it does not verify that an event is published before including it in the push, allowing unpublished (i.e., not yet publicly shared) events to be transmitted to the remote server; and (2) it does not verify that the pushing user has read access to the event, causing events the user cannot fetch to be sent as empty event shells, thereby disclosing the existence and metadata of events the user is not authorized to view. Additionally, the remote server's reply selecting which offered events to accept is used without validating that the selected identifiers actually correspond to events in the offered set, potentially allowing the remote to reference events outside the intended scope. The vulnerability requires an authenticated user with push permissions on the source MISP instance and a configured push target. The security impact is unauthorized disclosure of confidential threat-intelligence data (unpublished events and events restricted by user permissions) to a remote MISP instance that should not receive them. | ||||
| CVE-2026-133185 | 1 Goproxy Project | 1 Goproxy | 2026-11-20 | 7.4 High |
| Goproxy before 1.9.4 contains a weak key generation vulnerability in NewCounterEncryptorRandFromKey that derives RSA and Ed25519 leaf certificate private keys from public data due to misuse of hash.Sum. Attackers with the CA certificate and one observed leaf certificate can regenerate that host's leaf private key and impersonate the host to clients trusting the proxy CA. | ||||
| CVE-2026-133188 | 1 Misp | 1 Misp | 2026-11-20 | N/A |
| MISP contains a vulnerability in the cryptographic signature verification of protected events. When a MISP instance signs a protected event for synchronization, it strips all whitespace from the JSON body before computing the PGP signature (preg_replace("/\s+/", "", $data)). The receiving instance performs the same whitespace-stripping before verification. Because the signature covers only the whitespace-free representation, a network relay positioned between two MISP instances can insert whitespace characters into JSON object keys (effectively renaming fields) or into identifier values such as UUIDs, timestamps, and distribution fields without invalidating the signature. The receiving instance accepts the modified event as authentic. The vulnerability affects the protected event synchronization path: event creation (EventsController::add), event editing (EventsController::edit), event viewing (EventsController::view1), and server-to-server pull synchronization (ServerSyncTool, Server model). An attacker with a network position to intercept and modify traffic between MISP instances can alter the semantic content of protected events while the PGP signature still validates, undermining the integrity guarantees that protected events are designed to provide. The fix introduces two complementary mechanisms. First, a post-verification scan rejects any received body that contains whitespace in JSON keys (except under Galaxy cluster 'meta' keys) or in identifier-like values (uuid, id, timestamp, distribution, date). Second, a new exact-byte signature scheme (x-pgp-signature-v2) signs the body as transmitted, without whitespace normalization. MISP 3.0 and later peers exchange this exact-byte signature; older peers retain the legacy whitespace-stripped signature. A signature_version field is embedded in protected events so that a 3.0 receiver refuses a body carrying that marker if only the legacy signature is present. Both mechanisms together close the whitespace-injection vector while preserving backward compatibility with pre-3.0 instances. | ||||
| CVE-2026-133192 | 1 Jetbrains | 1 Junie Github Action | 2026-11-20 | 4.2 Medium |
| In JetBrains Junie GitHub Action before 1.10.0 untrusted fork code could be processed in privileged workflow runs | ||||
| CVE-2026-133193 | 1 Jetbrains | 1 Junie Github Action | 2026-11-20 | 5.6 Medium |
| In JetBrains Junie GitHub Action before 1.10.0 code execution was possible via path traversal in feedback session markers | ||||
| CVE-2026-133194 | 1 Jetbrains | 1 Junie Github Action | 2026-11-20 | 5.6 Medium |
| In JetBrains Junie GitHub Action before 1.10.0 command injection was possible via the action version input | ||||
| CVE-2026-133196 | 1 Jetbrains | 1 Junie Cli | 2026-11-20 | 5.3 Medium |
| In JetBrains Junie CLI before 26.11.1 files outside the project could be overwritten via shell output redirection | ||||
| CVE-2026-133197 | 1 Jetbrains | 1 Junie Cli | 2026-11-20 | 5 Medium |
| In JetBrains Junie CLI before 26.9.22 command injection was possible via file names in code review | ||||
| CVE-2026-133198 | 1 Jetbrains | 1 Junie | 2026-11-20 | 7.8 High |
| In JetBrains Junie before 252.819.35, 253.819.35 code execution was possible via terminal environment settings in project files | ||||
| CVE-2026-133061 | 1 Moodle | 1 Moodle | 2026-11-20 | 4.3 Medium |
| A flaw was found in Moodle. Due to a missing capability check in the grade items web service, an authenticated user with a student role can view the names of all grade items in a course, including those intended to be hidden. This flaw leads to unauthorized information disclosure of hidden course assessment details. | ||||
| CVE-2026-133239 | 2 Jhumanj, Opnform | 2 Opnform, Opnform | 2026-11-20 | 6.5 Medium |
| OpnForm before 2.8.2 contains an improper authorization vulnerability that allows unauthenticated attackers to move other forms' shared assets by supplying their URLs in file upload fields. Attackers can submit a public form with another form's cover or logo URL, causing Storage::move() to relocate it into submissions and break that asset. | ||||
| CVE-2026-99690 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 4.7 Medium |
| In the Linux kernel, the following vulnerability has been resolved: ocfs2: cache the mount context for dentry lock callbacks ocfs2_drop_dentry_lock() drops the inode reference before releasing the DENTRY lock. This lets inode eviction release the local inode and open locks before a remote unlink can proceed past the DENTRY lock. A DLM callback can still arrive before the DENTRY lock has been dropped. ocfs2_get_dentry_osb() obtains the mount context through dl_inode->i_sb, which can access a freed inode when the downconvert thread drops the last inode reference in its post-unlock callback: Downconvert thread DLM callback thread ------------------ ------------------- ocfs2_process_blocked_lock() ocfs2_dentry_post_unlock() ocfs2_dentry_lock_put() ocfs2_drop_dentry_lock() iput(dl->dl_inode) [inode reclaimed after RCU] ocfs2_blocking_ast() ocfs2_get_dentry_osb() dl->dl_inode->i_sb ocfs2_simple_drop_lockres() Store the mount context in the DENTRY lock resource's l_priv field and use the default mount-context lookup. Recover the containing dentry lock with container_of(), as already done for refcount locks, and remove ocfs2_get_dentry_osb(). ocfs2_dismount_volume() shuts down the DLM before freeing the mount context, so callbacks can use it without accessing the inode. Preserve the existing iput-before-unlock order to avoid delaying local inode and open lock release until after the DENTRY lock is released. | ||||
| CVE-2026-99743 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | 6.8 Medium |
| In the Linux kernel, the following vulnerability has been resolved: ksmbd: grant a POSIX ACL group entry only to the group's members When no ACE of the DACL matches the caller, Everyone or Authenticated Users, smb_check_perm_dacl() falls back to the file's POSIX ACL. It takes the first ACL_USER or ACL_GROUP entry whose id equals the caller's uid. For ACL_GROUP, this compares a gid with the caller's uid. A numerical match grants the group's permissions even when the caller is not a member. Match a group entry only when the caller is also in the group. | ||||
| CVE-2026-131071 | 1 Google | 2 Android, Chrome | 2026-11-20 | 8.1 High |
| Confused deputy in Mobile in Google Chrome on on Android prior to 158.0.8127.36 allowed a remote attacker to bypass web origin policy via a crafted HTML page. (Chromium security severity: Medium) | ||||
| CVE-2026-126054 | 2026-11-20 | N/A | ||
| A Path Traversal vulnerability in workspace directory handling and Git integration in Google Cloud Dataform, BigQuery Studio and Colab Enterprise on Google Cloud Platform allows an authenticated remote attacker to read private files and create arbitrary files across tenant repositories using crafted workspace operations and Git integration requests. This vulnerability was patched on 10 October 2026, and no customer action is needed. | ||||
| CVE-2026-95968 | 1 Microsoft | 23 Windows 10 1607, Windows 10 1809, Windows 10 21h2 and 20 more | 2026-11-20 | 7 High |
| Use after free in Windows Smart Card allows an authorized attacker to elevate privileges locally. | ||||