Export limit exceeded: 429947 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (429947 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-133629 | 1 Sunnet | 1 Ctms | 2026-11-20 | 6.3 Medium |
| A vulnerability was determined in Sunnet CTMS up to 10.11. Impacted is an unknown function of the file /cltcms/api/external-training/ext-course of the component External Training Application Form Feature. This manipulation of the argument memberids causes improper control of resource identifiers. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure but did not respond in any way. | ||||
| CVE-2026-107494 | 1 Openssl | 1 Openssl | 2026-11-20 | 9.1 Critical |
| Issue summary: The QUIC stack queues a RETIRE_CONNECTION_ID frame also for retransmitted NEW_CONNECTION_ID frames. This allows a remote malicious QUIC stack to queue an unlimited number of RETIRE_CONNECTION_ID frames. Impact summary: A malicious remote QUIC peer can trigger an out-of-memory condition causing a Denial of Service. CWE: CWE-770: Allocation of Resources Without Limits or Throttling Description: The earlier fix for CVE-2026-84784 was not complete. It failed to ignore retransmissions of the NEW_CONNECTION_ID frame. The QUIC implementation created and inserted a RETIRE_CONNECTION_ID frame for every retransmitted NEW_CONNECTION_ID frame it received and there was no limit on how many RETIRE_CONNECTION_ID frames were queued. This allows a malicious remote QUIC stack to trigger an out-of-memory (OOM) condition. FIPS impact: no The FIPS module is not affected as the QUIC implementation is outside the OpenSSL FIPS module boundary. | ||||
| CVE-2026-121481 | 1 Openssl | 1 Openssl | 2026-11-20 | 9.8 Critical |
| Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer. Impact summary: No path by which an attacker can trigger this has been identified. An application that passes an input length near INT_MAX to EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting its own memory, but it must itself supply such a length. CWE: CWE-190: Integer Overflow or Wraparound Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied length into an output buffer that the caller allocates. The caller is expected to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the arithmetic that computes the encoded length overflows a signed integer, so the function writes more data than the documented output size. The result is a heap buffer overflow in the calling process. Reaching this requires an application to pass an input length near INT_MAX to EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode buffers of that size, and the command line tools cannot practically be made to do so: the limits on reading a proxy password from a file and on bignum sizes prevent it. An application that accepts an attacker-controlled length and forwards it to EVP_EncodeBlock() without its own bound check is exposed. The severity is Low because no attacker-controlled path to the overflow is known. The caller must already hold a buffer of about two gigabytes before the defect can be reached. FIPS impact: no The affected code is outside the FIPS module boundary. | ||||
| CVE-2026-121482 | 1 Openssl | 1 Openssl | 2026-11-20 | 7.5 High |
| Verifying a maliciously crafted CMS or PKCS#7 SignedData message with CRL checking enabled may consume excessive CPU time, growing with the square of the message size. | ||||
| CVE-2026-111508 | 1 Dell | 12 Powerstore 1000t, Powerstore 1200t, Powerstore 3000t and 9 more | 2026-11-20 | 9.1 Critical |
| Dell PowerStore contains an OS Command Injection vulnerability. Exploitation could lead to arbitrary command execution with root privileges on the appliance. | ||||
| CVE-2026-107518 | 1 Dell | 12 Powerstore 1000t, Powerstore 1200t, Powerstore 3000t and 9 more | 2026-11-20 | 8.7 High |
| Dell PowerStore contains a Server-Side Request Forgery (SSRF) vulnerability. An authenticated user with limited privileges could potentially exploit this vulnerability to make the appliance connect to attacker-chosen internal systems. | ||||
| 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-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-99690 | 1 Linux | 2 Linux, Linux Kernel | 2026-11-20 | N/A |
| 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 | N/A |
| 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-132668 | 2026-11-20 | N/A | ||
| In Postgres Enterprise Manager (PEM), any PEM user can run the pem.send_webhook() function, which runs with elevated privileges and queues a payload for any configured webhook. The PEM agent then delivers it with that webhook's stored headers, OAuth token or client certificate, so a user can send forged notifications to endpoints they could not otherwise authenticate to. From PEM 10.6.1, no PEM login role can call this function directly. PEM still sends webhook notifications through its own internal paths. | ||||
| CVE-2026-132665 | 2026-11-20 | N/A | ||
| In Postgres Enterprise Manager (PEM), the pem.deploy_job_template() function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role (pem_manage_schedule_task) can deploy and schedule SQL or shell job steps on agents that belong to other teams. From PEM 10.6.1, PEM checks team access for every server, group and agent a template is deployed to. | ||||
| CVE-2026-132664 | 2026-11-20 | N/A | ||
| In Postgres Enterprise Manager (PEM), any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted with a key that is the same in every PEM installation, so they can be decrypted. From PEM 10.6.1, PEM users can no longer read these passwords. | ||||