CVE-20XX-?
agent?

The internet is broken right now.

63 critical CVEs without a fix in the last 48 hours. Somewhere a staging server is public. It always is. 161 more already have a fix that someone still has to apply.

3,280 CVEs · updated 2026-11-19 14:44 UTC

Reset all
  1. CVE-2026-132150

    A flaw was found in the file-xmc plugin in GIMP. When processing a specially crafted XMC image file, the plugin does not properly validate the comment subtype before using it as an array index. This missing validation leads to out-of-bounds memory access, invalid free and use-after-free issues. This vulnerability can result in an application crash, leading to a denial of service, or potentially allow for arbitrary code execution.

    Memory safety Web app Red Hat Red Hat Enterprise Linux 10

    7.8 HIGH No fix listed
  2. CVE-2026-109908

    A heap buffer overflow in reading encoding files in X.Org libfontenc before 1.11.0 could be used by local attackers able to inject enc files to the X server could crash or escalate privileges.

    Memory safety Server X.Org Libfontenc

    7.8 HIGH Fix listed
  3. CVE-2026-116446

    Dell PowerStore SDNAS contains an out-of-bounds memory vulnerability in the NAS NFS service that an unauthenticated remote attacker could exploit to cause a denial of service.

    Memory safety Dell PowerStore 500T

    9.8 CRITICAL Fix listed
  4. CVE-2026-95788

    An unauthenticated buffer overflow vulnerability exists in the underlying operating system of AOS-10 or AOS-8 and could allow an unauthenticated adjacent attacker to conduct a denial of service attack. Successful exploitation could allow an attacker to disrupt the availability of the affected system, with a limited impact to the integrity of the affected component.

    Memory safety Hewlett Packard Enterprise (HPE) ArubaOS (AOS)

    7.1 HIGH No fix listed
  5. CVE-2026-132138

    A flaw was found in cyrus-sasl. When processing authentication requests using the Salted Challenge Response Authentication Mechanism (SCRAM), a remote attacker can trigger a null pointer dereference by submitting unexpected channel-binding data. This causes the server process to crash before validating authentication proofs, leading to a Denial of Service (DoS).

    Memory safety Server Red Hat Red Hat Enterprise Linux 10

    5.3 MEDIUM Fix listed
  6. CVE-2026-126763

    In Eclipse Mosquitto versions 1.6 to 2.0.22 and 2.1.0 to 2.1.2, an MQTT v5.0 client connecting with a will-delay-interval that subsequently disconnects with a shorter interval causes all delayed wills to be suppressed.

    Memory safety Eclipse Foundation Eclipse Mosquitto

    unscored Fix listed
  7. CVE-2026-123123

    An attacker that is able to send a crafted network packet to the affected component may trigger an integer overflow during module size validation. This may cause insufficient bounds checking and result in out-of-bounds memory reads, potentially leading to a denial of service condition due to process termination.

    Memory safety Library SICK AG Sick Scan Xd

    7.5 HIGH Fix listed
  8. CVE-2026-122042

    WarehousePG (WHPG) 6.27.1 through 6.27.7 and 7.2.1 through 7.6.1 are affected by an out-of-bounds write vulnerability (CWE-787) in gpfdist, the file server used to load and unload external tables. When gpfdist attaches a request to a session, it sizes two internal arrays from the client-supplied X-GP-SEGMENT-COUNT header and writes to them at the index given by the X-GP-SEGMENT-ID header, without checking that the index is non-negative and smaller than the count (CWE-129). gpfdist does not authenticate callers unless gpfdists is used with client certificate verification, so an attacker who can reach the gpfdist port can crash it with a single HTTP request, failing every external table load or unload that uses that gpfdist instance. gpfdist is normally reachable only from the cluster's internal network.

    Memory safety Server EnterpriseDB WarehousePG

    7.1 HIGH No fix listed
  9. CVE-2026-108317

    Tanium addressed an information disclosure vulnerability in Tanium Server.

    Memory safety Server Tanium Server

    4.2 MEDIUM No fix listed
  10. CVE-2026-107519

    Dell PowerStore contains an integer underflow vulnerability. An attacker could exploit this vulnerability, potentially leading to denial of service of a cryptographic service.

    Memory safety Server Dell PowerStore 500T

    8.1 HIGH Fix listed
  11. CVE-2026-130667

    ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability in the TIFF decoder that allows attackers to corrupt heap memory by supplying a crafted TIFF image. Attackers can provide a malicious TIFF file that, when encoded in a specific output format, triggers a heap buffer over-write causing memory corruption.

    Memory safety ImageMagick

    4.8 MEDIUM Fix listed
  12. CVE-2026-130668

    ImageMagick before 7.1.2-35 contains a double free vulnerability that allows attackers to trigger an invalid memory free by using the DPC compare metric. Attackers can supply images for comparison with the DPC metric to corrupt memory and crash the application, causing denial of service.

    Memory safety ImageMagick

    2.0 LOW Fix listed
  13. CVE-2026-130670

    ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability that allows attackers to read beyond allocated memory when BGRO image data is imported. Attackers can supply crafted BGRO data for processing to crash the application or leak adjacent heap memory contents.

    Memory safety ImageMagick

    4.8 MEDIUM Fix listed
  14. CVE-2026-130662

    ImageMagick before 7.1.2-35 contains a use after free vulnerability in the MSL decoder that can be triggered when processing crafted MSL image files. Attackers can supply a specially crafted MSL image to cause memory corruption, potentially crashing the application or leading to further compromise.

    Memory safety ImageMagick

    6.3 MEDIUM Fix listed
  15. CVE-2026-130664

    ImageMagick before 7.1.2-35 contains a heap buffer overflow vulnerability that allows attackers to write beyond allocated heap memory by supplying crafted images. Attackers can provide a crafted set of images processed by the magick stream operation to corrupt heap memory and crash the application.

    Memory safety ImageMagick

    2.0 LOW Fix listed
  16. CVE-2026-130665

    ImageMagick before 7.1.2-35 contains a use after free vulnerability in the EXR decoder that is triggered when a specific memory allocation fails. Attackers can supply crafted EXR images processed under memory pressure to trigger the use after free, causing crashes or memory corruption.

    Memory safety ImageMagick

    6.3 MEDIUM Fix listed
  17. CVE-2026-130656

    ImageMagick before 7.1.2-35 contains an information disclosure vulnerability in the MNG decoder that allows attackers to expose uninitialized memory by supplying a crafted image. Attackers can submit malicious MNG files for processing to leak uninitialized memory contents, potentially revealing sensitive data from the process.

    Memory safety ImageMagick

    6.3 MEDIUM Fix listed
  18. CVE-2026-130658

    ImageMagick before 7.1.2-35 contains an information disclosure vulnerability in the RLA decoder that returns images containing uninitialized data. Attackers can supply a crafted RLA image to cause the decoded output to include uninitialized memory, potentially disclosing heap information.

    Memory safety ImageMagick

    6.3 MEDIUM Fix listed
  19. CVE-2026-130660

    ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability in the MVG decoder that allows attackers to read out-of-bounds memory by supplying a crafted file. Attackers can provide a malicious MVG file for processing to trigger the over-read, causing application crashes or exposure of heap memory contents.

    Memory safety ImageMagick

    4.8 MEDIUM Fix listed
  20. CVE-2026-130652

    ImageMagick before 7.1.2-35 contains a heap buffer over-read vulnerability that allows attackers to read beyond allocated heap memory by triggering the -copy operation. Attackers can supply crafted images or arguments processed with -copy to crash the application or disclose adjacent heap memory contents.

    Memory safety ImageMagick

    4.8 MEDIUM Fix listed
  21. CVE-2026-121481

    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.

    Memory safety OpenSSL

    unscored Fix listed
  22. CVE-2026-132049

    A flaw was found in lldpd. The service fails to verify that Link Layer Discovery Protocol - Media Endpoint Discovery (LLDP-MED) location records received from network neighbors match their declared lengths. An adjacent attacker on the local network can exploit this flaw by sending crafted packets, causing client applications using the liblldpctl library to read past buffer boundaries when parsing location data. This issue can lead to an information disclosure of adjacent process memory.

    Memory safety Library Red Hat Red Hat Enterprise Linux 10

    4.3 MEDIUM Fix listed
  23. CVE-2026-129149

    In Eclipse Mosquitto versions 2.1.0 to 2.1.2, using the mosquitto_ctrl utility in interactive shell mode to interact with a malicious server could result in a crash of the utility if the server sent a hostile response.

    Memory safety Server Eclipse Foundation Eclipse Mosquitto

    unscored Fix listed
  24. CVE-2026-110486

    In Eclipse Mosquitto versions 2.1 through 2.1.2, a listener configured with `protocol websockets` mishandles empty WebSocket data frames. `net__read_ws()` in `lib/net_ws.c` returns the number of framing bytes consumed (the 4 masking-key bytes) for a data frame with a zero-length payload, without writing any bytes to the caller’s buffer. The MQTT packet reader in `packet__read_single()` (`lib/packet_mosq.c`) trusts that return value as a payload byte count. A remote client can therefore advance the read position over an uninitialised heap allocation, causing the broker to process and forward uninitialised heap memory (information disclosure, including heap and libc pointers), and can underflow the unsigned `to_process` counter so that subsequent attacker-controlled frame data is written past the end of the allocation (heap out-of-bounds write). The out-of-bounds write is reachable from the CONNECT packet before any authentication check, so an unauthenticated client can corrupt the heap and crash the broker even when `allow_anonymous false` is set. Combining the disclosure and the write allows remote code execution as the broker’s user by any client able to establish a session.

    Memory safety Eclipse Foundation Eclipse Mosquitto

    9.8 CRITICAL Fix listed
  25. CVE-2026-19707

    A bug in the Airlock Gateway (8.5.2 and earlier, and 8.6.0) allows attacker-controlled HTML in a backend response to exploit the Smart Form Protection feature, possibly leading to a Denial of Service (DoS) or Remote Code Execution (RCE) attack against the Airlock Gateway. The issue has been fixed in Airlock Gateway version 8.5.3 and 8.6.1. For an attack to be executable, the Airlock Gateway needs to have 'Smart Form Protection' (or the corresponding expert settings) enabled on a mapping whose backend returns a response containing certain multi-byte HTML character references. The buffer overflow then happens during the parsing of that HTML response. Such a response can come either from a malicious or compromised backend, or from an otherwise trusted backend that returns attacker-supplied HTML, e.g. an application that stores and serves plain user-provided HTML files. Successfully exploiting the vulnerability can enable an attacker to perform a DoS attack or, in the worst case, an RCE attack against the Airlock Gateway in front of the affected backend. Compromising the functionality of the Airlock Gateway could in this way also affect the availability and protection of other well-intentioned backends deployed behind the same Gateway.

    Memory safety Web app Airlock By Ergon Airlock Gateway

    9.5 CRITICAL Fix listed
  26. CVE-2026-112213

    Out-of-bounds read vulnerability in the pixReadMemJp2kCore() function in Leptonica, located in jp2kio.c. The function retrieves the output dimensions only for component 0 and uses a common index to iterate through the buffers of all components. If the remaining components have smaller dimensions, the traversal exceeds the bounds of their sample buffers, which are allocated by OpenJPEG. When processing a specially crafted JPEG 2000 image, data read from adjacent dynamic memory may be incorporated into the pixels of the decoded image and result in information disclosure to anyone who can access the output.

    Memory safety Library Dan Bloomberg Leptonica

    6.9 MEDIUM No fix listed
  27. CVE-2026-99313

    In the Linux kernel, the following vulnerability has been resolved: HID: logitech-hidpp: fix race condition when accessing stale stack pointer The driver uses hidpp->send_receive_buf to point to a stack-allocated buffer in the synchronous command path (__do_hidpp_send_message_sync). However, this pointer is not cleared when the function returns. If an event is processed (e.g. by a different thread) while the send_mutex is held by a new command, but before that command has updated send_receive_buf, the handler (hidpp_raw_hidpp_event) will observe that the mutex is locked and dereference the stale pointer. This results in an out-of-bounds access on a different thread's kernel stack (or a NULL pointer dereference on the very first command). Fix this by: 1. Clearing hidpp->send_receive_buf to NULL before releasing the mutex in the synchronous command path. 2. Moving the assignment of the local 'question' and 'answer' pointers inside the mutex_is_locked() block in the handler, and adding a NULL check before dereferencing.

    Memory safety OS & kernel Linux

    8.8 HIGH No fix listed
  28. CVE-2026-99314

    In the Linux kernel, the following vulnerability has been resolved: ALSA: us122l: Add missing NULL check in usb_stream_hwdep_mmap() usb_stream_hwdep_mmap() reads us122l->sk.s and dereferences it without checking for NULL. The stream object is released by usb_stream_free(), which is reached through us122l_stop() both when the device is disconnected and when us122l_start() fails, and it leaves us122l->sk.s set to NULL. The hwdep file stays usable after that, so a later mmap() KASAN: null-ptr-deref in range [0x0000000000000010-0x0000000000000017] RIP: 0010:usb_stream_hwdep_mmap+0x107/0x890 sound/usb/usx2y/us122l.c:182 crashes while reading s->read_size, which sits at offset 0x10. That NULL is an expected state for this field: usb_stream_hwdep_vm_fault(), usb_stream_hwdep_poll(), usb_stream_hwdep_ioctl(), usb_stream_stop() and usb_stream_free() all test it before use. Only the mmap callback misses the check, so let it return -ENODEV, matching what the other hwdep mapping in usx2yhwdeppcm.c does when its shared buffer has not been allocated.

    Memory safety OS & kernel Linux

    unscored No fix listed
  29. CVE-2026-99318

    In the Linux kernel, the following vulnerability has been resolved: ALSA: bcd2000: Fix use-after-free of MIDI URBs on file close bcd2000_disconnect() calls snd_card_disconnect(), which only prevents new opens, and then frees the MIDI URBs. A rawmidi file that was already open can still be closed afterwards, and its close callback, bcd2000_midi_output_close(), calls usb_kill_urb() on midi_out_urb. The URB pointers are cleared on disconnect and their accesses are serialized with midi_lock, but bcd2000_midi_output_close() reads midi_out_urb without that lock. The check can therefore pass just before the pointer is cleared, and usb_kill_urb() then runs on the URB that has already been freed: BUG: KASAN: slab-use-after-free in usb_kill_urb+0x74/0x80 Read of size 8 at addr ffff8880078e7d40 usb_kill_urb bcd2000_midi_output_close close_substream rawmidi_release_priv snd_rawmidi_release Allocated by: usb_alloc_urb <- bcd2000_init_midi <- bcd2000_probe Freed by: usb_free_urb <- bcd2000_midi_free <- bcd2000_disconnect Take the lock in bcd2000_midi_output_close() and reference the URB with usb_get_urb() before releasing it. The URB then stays valid until usb_put_urb() after usb_kill_urb() has returned, even if a disconnect frees it in the meantime. usb_kill_urb() itself cannot run under midi_lock, as the completion handler takes the same lock.

    Memory safety OS & kernel Linux

    unscored No fix listed
  30. CVE-2026-125346

    Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)

    Memory safety Browser & mail

    8.8 HIGH No fix listed