Export limit exceeded: 420129 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 420129 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 420129 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Export limit exceeded: 420129 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.

Search

Search Results (420129 CVEs found)

CVE Vendors Products Updated CVSS v3.1
CVE-2026-83525 1 Apache 1 Kafka 2026-11-05 6.5 Medium
Incorrect operator (CWE-480) in the FetchSnapshot RPC handler in Apache Kafka from 2.8.0 before 4.2.2, and from 4.3.0 before 4.3.2 on all platforms allows an authenticated attacker with CLUSTER_ACTION privilege to cause a denial of service (controller process termination) via a crafted FetchSnapshotRequest with an empty topics array or a topic with no partitions. Users are recommended to upgrade to version 4.2.2, 4.3.2, or 4.4.0, which fix this issue. Users on unsupported branches (4.1.x and earlier) should upgrade to 4.2.2 or later.
CVE-2026-114349 1 Apache 1 Kafka 2026-11-05 6.5 Medium
When a broker decodes a compressed record batch, the per-record decoder reads a declared body size from the decompressed stream and allocates a buffer of that size before validating it against the bytes available or any configured limit. The size is attacker-controlled, and the batch CRC does not constrain it, so a small (around 90-byte), CRC-valid compressed produce request can declare a body size of up to about 2 GiB and force the broker to attempt that allocation, raising OutOfMemoryError. The record size limit (max.message.bytes), the request size limit, and client/broker quotas bound only the compressed wire size, not the declared decompressed size. Impact: An authenticated principal with Write on a topic can crash broker request-handler threads (reached when a batch's codec differs from the topic's compression.type and records are re-encoded) and any consumer that fetches the record, denying service. On brokers started with -XX:+ExitOnOutOfMemoryError, a common hardening, a single crafted request terminates the broker JVM. More seriously, a crafted record  is accepted at ingest and written to disk; when the log-cleaner later reads it on a compacted topic, the OutOfMemoryError (an Error, not an Exception) terminates the cleaner thread, which is not restarted. With the default of a single cleaner thread, log compaction then stops for the entire broker, including the internal __consumer_offsets and __transaction_state topics, and the condition persists across restarts until the offending record is removed. The impact is availability only; no data is disclosed or altered. Mitigation: Upgrade to Apache Kafka 4.2.2, 4.3.2, or 4.4.0, and set max.decompressed.message.bytes (at the broker and/or topic level) to a bounded value appropriate for your workload. Upgrading alone is not sufficient: for backward compatibility this configuration defaults to an effectively unlimited value (about 2 GiB), so a broker remains exposed until the limit is set. Choose a value at or slightly above the largest legitimate decompressed record your applications produce, and comfortably below the broker heap divided by the number of request-handler and cleaner threads. Until you can upgrade and configure the limit, restrict Write access to trusted producers; quotas and max.message.bytes do not mitigate this issue. Resolution: From Apache Kafka 4.2.2, 4.3.2, and 4.4.0: the broker validates a record's declared decompressed body size against max.decompressed.message.bytes before allocating, on the produce-validation, log-compaction, and timestamp-lookup paths, and rejects oversized or negative sizes with InvalidRecordException. Operators must set this configuration to a bounded value to be protected, as its default is effectively unlimited.
CVE-2026-59048 1 Google 1 Android 2026-11-05 5.5 Medium
In rb_cpu_init of trace.c, there is a possible out-of-bounds read due to an incorrect bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.
CVE-2026-93998 1 Redhat 7 Amq Broker, Build Keycloak, Jboss Enterprise Application Platform and 4 more 2026-11-05 7.4 High
A flaw was found in the SAML adapter component of Keycloak, which is used to secure applications with SAML-based authentication. The adapter fails to verify that the issuer of a signed SAML assertion matches the expected identity provider configured for the application. If multiple identity providers share the same trusted signing key, an attacker who controls one of those providers can create a validly signed assertion to log into the application as any user, potentially gaining full administrative control.
CVE-2026-107903 1 Balbooa.com 1 Gridbox Extension For Joomla 2026-11-05 8.3 High
Joomla Extension - balbooa.com - Stored XSS in reviews via inconsistent sanitization in Gridbox < 2.20.5.0
CVE-2026-61649 1 Suitecrm 1 Suitecrm 2026-11-05 7.7 High
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the SSRF protection added in 7.15.1 uses a substring comparison in isSelfRequest() rather than hostname equality. The affected flow begins at validate_external_host() and uses isSelfRequest(), and stripos() to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated attacker can place the server hostname in a URL path to bypass IP validation and direct server-side requests to internal services. This issue is fixed in versions 7.15.2 and 8.10.2.
CVE-2026-69137 1 Suitecrm 1 Suitecrm 2026-11-05 7.7 High
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the CalendarAccount testConnection action passes an authenticated caller's server_url directly to curl without host, address, or scheme validation. The affected flow begins at CalendarAccount::action_testConnection and uses server_url, CalDAVProvider::makeCalDAVRequest(), and PROPFIND to carry attacker-controlled data or authorization state into the security-sensitive operation. The server sends a PROPFIND request from its network context and returns non-success response bodies, enabling internal-service access, partial response disclosure, service enumeration, and possible cloud metadata access. This issue is fixed in versions 7.15.2 and 8.10.2.
CVE-2026-100364 1 Suitecrm 1 Suitecrm 2026-11-05 7.1 High
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to 7.15.2 and 8.10.2, the V8 JSON:API update path fails to remove the id attribute before assigning user-supplied attributes to a SugarBean. The affected flow begins at updateRecord() and uses processAttributes(), id, and ACL_ALLOW_OWNER to carry attacker-controlled data or authorization state into the security-sensitive operation. An authenticated user can substitute a victim record identifier, bypass owner-only authorization, overwrite another record, and hijack record ownership. This issue is fixed in versions 7.15.2 and 8.10.2.
CVE-2026-112441 1 Apple 1 Macos 2026-11-05 3.3 Low
This issue was addressed by removing the vulnerable code. This issue is fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2. An app may be able to access sensitive user data.
CVE-2026-112442 1 Apple 1 Macos 2026-11-05 4.7 Medium
A race condition was addressed with additional validation. This issue is fixed in macOS Golden Gate 27.2, macOS Sequoia 15.8.2, macOS Tahoe 26.7.2. An app may be able to modify protected parts of the file system.
CVE-2026-116668 1 Tanium 1 Discover 2026-11-05 4.3 Medium
Tanium addressed an uncontrolled resource consumption vulnerability in Discover.
CVE-2026-116666 1 Tanium 1 Discover 2026-11-05 4.3 Medium
Tanium addressed an information disclosure vulnerability in Discover.
CVE-2026-116664 1 Tanium 1 Discover 2026-11-05 3.1 Low
Tanium addressed an improper access controls vulnerability in Discover.
CVE-2026-116669 1 Tanium 1 Discover 2026-11-05 6.5 Medium
Tanium addressed an improper access controls vulnerability in Discover.
CVE-2026-116667 1 Tanium 1 Discover 2026-11-05 4.2 Medium
Tanium addressed an improper access controls vulnerability in Discover.
CVE-2026-116665 1 Tanium 1 Discover 2026-11-05 4.3 Medium
Tanium addressed an information disclosure vulnerability in Discover.
CVE-2026-116648 1 Tanium 1 Discover 2026-11-05 4.1 Medium
Tanium addressed an improper output sanitization vulnerability in Discover.
CVE-2026-81190 2026-11-05 N/A
KurrentDB is a database engineered for modern software applications and event-driven architectures. In version 26.1.0, a user authorized to read the $all stream can use Secondary Indexing query capabilities to read arbitrary files accessible to the database process, enumerate directories, and issue HTTP GET requests from that process. The default configuration limits this privilege to administrators. The flaw does not permit file writes and does not expose environment variables. This issue is fixed in version 26.1.1.
CVE-2026-42169 2 Gimp, Redhat 6 Gimp, Enterprise Linux, Enterprise Linux Eus and 3 more 2026-11-05 7.3 High
A heap-buffer-overflow vulnerability exists in the APNG (Animated PNG) file loader of GIMP. This flaw occurs when the `fcTL` width exceeds the `IHDR` width, leading to pixel data being written past the end of a heap allocation. Additionally, a heap-based buffer overflow exists in the DDS plug-in due to a BPP mismatch in the `load_layer()` function. Both vulnerabilities can be triggered by opening a specially crafted image file, potentially leading to code execution.
CVE-2026-4271 2 Gnome, Redhat 4 Libsoup, Enterprise Linux, Enterprise Linux Eus and 1 more 2026-11-05 5.3 Medium
A flaw was found in libsoup, a library for handling HTTP requests. This vulnerability, known as a Use-After-Free, occurs in the HTTP/2 server implementation. A remote attacker can exploit this by sending specially crafted HTTP/2 requests that cause authentication failures. This can lead to the application attempting to access memory that has already been freed, potentially causing application instability or crashes, resulting in a Denial of Service (DoS).