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. 153 more already have a fix that someone still has to apply.

3,237 CVEs · updated 2026-11-19 14:13 UTC

Reset all
  1. CVE-2026-95401

    In knee_function_info of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  2. CVE-2026-95402

    In slice_header of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  3. CVE-2026-95397

    In sub_layer_hrd_parameters of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  4. CVE-2026-59631

    In s_inter_rps_pred of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  5. CVE-2026-59635

    In cpb_cnt of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  6. CVE-2026-101183

    UAF vulnerability in the location service module. Impact: Successful exploitation of this vulnerability may affect availability.

    Memory safety Library

    5.9 MEDIUM 0.1% exploit odds No fix listed
  7. CVE-2026-16659

    MCUboot's serial-recovery image-upload handler bs_upload() in boot/boot_serial/src/boot_serial.c declares const struct flash_area *fap = NULL and assigns it only via flash_area_open() part-way through the function. Two early validation failures (goto out_invalid_data) — a CBOR map that fails to decode, or an upload packet missing the off/data members — branch past the open while fap is still NULL, then fall into the shared epilogue. In MCUBOOT_ENC_IMAGES builds that epilogue unconditionally calls boot_handle_enc_fw(fap), which reaches boot_image_load_header() and flash_area_read() and dereferences the NULL flash_area. The defect is reachable pre-authentication: the trigger is the very first serial-recovery upload command carrying a malformed payload. The guarding conditions are default-true on a fresh recovery session — img_num, curr_off and img_size are zero-initialized statics, so curr_off == img_size and the primary-slot test both hold. It requires a non-default build: encrypted images (MCUBOOT_ENC_IMAGES / Zephyr CONFIG_BOOT_ENCRYPT_IMAGE) together with an active serial-recovery transport, on the Zephyr or Mynewt port (the two that build both boot/boot_serial/src/boot_serial.c and boot_serial_encryption.c with MCUBOOT_ENC_IMAGES). The impact is a transient denial of service of the bootloader during recovery. fap is a hard NULL rather than an attacker-controlled value, so there is no memory-corruption or information-leak primitive and image authentication is unaffected. Whether the dereference faults is platform-dependent — on targets where address 0x0 is mapped readable flash the read merely returns an error and execution continues, while targets that trap NULL (MPU / null-pointer-exception detection) take a hard fault. Because serial recovery is unauthenticated by design and already permits the console attacker to write the secondary slot, the added capability is only a low-value transient crash. The related unconditional flash_area_close(fap) call in the same epilogue is a safe no-op on the ports that reach it, so it does not contribute to the dereference. The affected ports are the Zephyr port — boot/zephyr/CMakeLists.txt compiles boot_serial.c under CONFIG_MCUBOOT_SERIAL and boot_serial_encryption.c under CONFIG_BOOT_ENCRYPT_IMAGE — and the Mynewt port, whose mcuboot_config.h defines MCUBOOT_SERIAL unconditionally and MCUBOOT_ENC_IMAGES under any BOOTUTIL_ENCRYPT_ syscfg, with boot/boot_serial/pkg.yml declaring no explicit source list so the whole directory is built. The Espressif port is not affected**: it compiles boot_serial.c but not boot_serial_encryption.c, and defines no MCUBOOT_ENC_IMAGES, so the #ifdef MCUBOOT_ENC_IMAGES block containing the call is preprocessed away. The NuttX, Cypress and Mbed ports do not build boot_serial.c at all.

    Memory safety Device

    4.0 MEDIUM 0.1% exploit odds Fix listed
  8. CVE-2026-59042

    In __pkvm_pages_to_ppages of mmu.c, there is a possible out-of-bounds write due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel Google Android

    7.4 HIGH 0.1% exploit odds Fix listed
  9. CVE-2026-55321

    In parse_prime256v1 of keymint_asn1.c, there is a possible Heap Buffer Overflow due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  10. CVE-2026-55344

    In TzSharedMemory of TzSharedMemory.c, there is a possible Heap buffer overflow due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  11. CVE-2026-56969

    In edgetpu_group_clear_responses of edgetpu_group.c, there is a possible Use After Free due to a logic error in the code. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  12. CVE-2026-56944

    In smmu_detach_dev of private/google-modules/iommu/arm-smmu-v3/drivers/iommu/arm/arm-smmu-v3/pkvm/arm-smmu-v3.c, there is a possible Use After Free due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  13. CVE-2026-58927

    The vulnerability is a Use-After-Free (UAF) in the EVS AIDL HAL, arising from a data race on an unsynchronized `std::weak_ptr` within `EvsEnumerator::openCamera()`. Specifically, concurrent calls from a privileged UID (e.g., `AID_AUTOMOTIVE_EVS`) can cause a torn `weak_ptr` state, leading to a virtual call through a freed object's vtable at `cameraObj->getCameraInfo(&desc)`. This allows for potential arbitrary code execution within the `hal_evs_default` process.

    Memory safety Device Google Android

    6.7 MEDIUM 0.1% exploit odds Fix listed
  14. CVE-2026-59573

    In max_num_ref_frames of avc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  15. CVE-2026-58790

    In CMD_ENC_SET_PARAM of encoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  16. CVE-2026-58791

    In pic_timing of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  17. CVE-2026-58786

    In cnm_memset of hevc_decoder, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  18. CVE-2026-58757

    In mfc_alloc_enc_roi_buffer of mfc_buf.c, there is a possible out-of-bounds write due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  19. CVE-2026-58697

    In codec3p_secure of codec3p_secure, there is a possible Heap Buffer Overflow due to a missing bounds check. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  20. CVE-2026-56933

    In RecordApTx of efw_ap_transport.c, there is a possible Non-Heap Buffer Overflow due to a buffer overflow. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  21. CVE-2026-55312

    In insert_node of remap.c, there is a possible way to trigger an out of bounds write in the address remapping table due to a non-heap buffer overflow. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  22. CVE-2026-59048

    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.

    Memory safety Device Google Android

    5.5 MEDIUM 0.1% exploit odds Fix listed
  23. CVE-2026-101185

    OOB read vulnerability in the peripheral module. Impact: Successful exploitation of this vulnerability may affect service confidentiality.

    Memory safety Device

    5.9 MEDIUM 0.1% exploit odds No fix listed
  24. CVE-2026-58740

    In BitmapImageBuffer of bitmap_image_buffer.h, there is a possible out-of-bounds write due to an integer overflow. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed
  25. CVE-2026-58995

    In getEntryFileName of ZipFileRO.cpp, there is a possible memory safety issue due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  26. CVE-2026-58966

    In multiple functions of hppsfilter.c, there is a possible out-of-bounds write due to a stack buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  27. CVE-2026-58871

    In set_type4_frame_classifier of sta_iface.cpp, there is a possible memory safety issue due to a heap buffer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Network gear Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  28. CVE-2026-59014

    In multiple locations, there is a possible out-of-bounds write due to an integer overflow. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  29. CVE-2026-58975

    In multiple locations, there is a possible out-of-bounds write due to a missing bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety

    8.4 HIGH 0.1% exploit odds No fix listed
  30. CVE-2026-58879

    In descramble of multiple files, there is a possible out-of-bounds write due to improper casting. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  31. CVE-2026-58769

    In multiple locations, there is a possible out-of-bounds read due to a missing bounds check. This could lead to local information disclosure with System execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel

    2.3 LOW 0.1% exploit odds No fix listed
  32. CVE-2026-58778

    In multiple locations, there is a possible use-after-free due to a race condition. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel

    6.4 MEDIUM 0.1% exploit odds No fix listed
  33. CVE-2026-59043

    In arm_lpae_split_blk_unmap of io-pgtable-arm-common.c, there is a possible memory corruption due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    7.4 HIGH 0.1% exploit odds Fix listed
  34. CVE-2026-59010

    In deserialize of legacy.rs, there is a possible denial of service due to a missing bounds check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    6.2 MEDIUM 0.1% exploit odds Fix listed
  35. CVE-2026-58988

    In isValid of ShimConverter.cpp, there is a possible out of bounds read due to a missing bounds check. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    4.0 MEDIUM 0.1% exploit odds Fix listed
  36. CVE-2026-58997

    In validateImageInfo of Bitmap.cpp, there is a possible out-of-bounds read due to a precondition check failure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    4.0 MEDIUM 0.1% exploit odds Fix listed
  37. CVE-2026-58971

    In _mupdf_get_hdr of wprint_mupdf.c, there is a possible out-of-bounds read due to an integer overflow. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety

    4.0 MEDIUM 0.1% exploit odds No fix listed
  38. CVE-2026-58926

    A Use-After-Free (UAF) vulnerability exists in the EVS HAL, allowing a privileged client to free a `buffer_handle_t` while the producer thread is still using it. This race condition, triggered via `doneWithFrame` and `setMaxFramesInFlight`, enables an attacker to manipulate freed heap memory, potentially leading to the leakage of file descriptors from the EVS HAL process.

    Memory safety Device Google Android

    2.5 LOW 0.1% exploit odds Fix listed
  39. CVE-2026-56938

    In port_shutdown of ipc.c, there is a possible Use After Free due to a race condition. This could lead to local escalation of privilege with execution privileges needed. User interaction is for exploitation.

    Memory safety OS & kernel

    7.0 HIGH 0.1% exploit odds No fix listed
  40. CVE-2026-133167

    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.

    Memory safety OFFIS DCMTK

    6.8 MEDIUM Fix listed
  41. CVE-2026-133168

    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.

    Memory safety OFFIS DCMTK

    8.5 HIGH Fix listed
  42. CVE-2026-126826

    A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause an application crash, data corruption, or potentially execute arbitrary code in the context of the current process.

    Memory safety Autodesk 3ds Max

    7.8 HIGH Fix listed
  43. CVE-2026-126825

    A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger an Out-of-Bounds Read (table-index lookup) vulnerability. A malicious actor may leverage this vulnerability to cause an application crash or potentially read sensitive data from the current process.

    Memory safety Autodesk 3ds Max

    5.5 MEDIUM Fix listed
  44. CVE-2026-126824

    A maliciously crafted SBSAR file, when imported or loaded through the Substance in 3ds Max plugin in Autodesk 3ds Max 2027, can trigger an Out-of-Bounds Read (unvalidated element begin-pointer) vulnerability. A malicious actor may leverage this vulnerability to cause an application crash or potentially read sensitive data from the current process.

    Memory safety Autodesk 3ds Max

    5.5 MEDIUM Fix listed
  45. CVE-2026-116440

    Dell PowerStore SDNAS contains a buffer overflow vulnerability that could allow an unauthenticated remote attacker to cause a denial of service or potential code execution on the NAS node.

    Memory safety Dell PowerStore 500T

    9.8 CRITICAL Fix listed
  46. CVE-2026-132129

    Passing a different column type while using deprecated range predicates, allow OOB read of any memory address. Users should update to 1.17.2 or 1.18.2

    Memory safety Server Apache Software Foundation Apache Kudu

    4.2 MEDIUM Fix listed
  47. CVE-2026-115677

    Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in AirTies Kablosuz İletişim Sanayi ve Dış Ticaret A.Ş. Air 5444 allows Overflow Buffers. This issue affects Air 5444: through 2026-11-19. NOTE: The vendor was contacted and it was learned that the product is not supported.

    Memory safety AirTies Kablosuz İletişim Sanayi Ve Dış Ticaret A.Ş. Air 5444

    7.5 HIGH No fix listed
  48. CVE-2026-92613

    In Eclipse iceoryx-rs, versions 0.0.11 to 0.0.13 and 0.1.0 as well as on the latest main branch. `SampleReceiver::<T>::take()` and `Sample::<T>::deref()` are safe functions that hand the caller a `&T` pointing at a chunk written by another iceoryx process, but the subscriber path neither requires `T: ShmSend` nor verifies that the received chunk is at least `size_of::<T>()` bytes / `align_of::<T>()`-aligned. A peer process that publishes an undersized chunk, or any chunk at all when the subscriber chose a pointer-bearing `T`, drives a `#![forbid(unsafe_code)]` subscriber into out-of-bounds reads of adjacent shared-memory chunks or dereference of a publisher-controlled pointer. Resolution: It will not be fixed since this is a known limitation in iceoryx as it is the users responsibility to specify the same data type on sender and receiver side. [iceoryx2](https://github.com/eclipse-iceoryx/iceoryx2) is the successor of iceoryx-rs where the API is designed to prevent this by default. It is strongly recommended to migrate to iceoryx2 which is actively maintained and receives security support. The iceoryx-rs package has officially reached End-of-life and will not receive any features, bugfixes or security fixes.

    Memory safety Library Eclipse Foundation Eclipse iceoryx™

    1.0 LOW Fix listed
  49. CVE-2026-99320

    In the Linux kernel, the following vulnerability has been resolved: ipv6: raw: fix use-after-free in rawv6_send_hdrinc() rawv6_send_hdrinc() caches the route before handing the skb to l3mdev_ip6_out(). The VRF output path may replace skb->dst and release the original route, leaving the cached pointer stale. The function later dereferences that pointer for statistics accounting and as the output device passed to NF_HOOK(). Its RCU read-side critical section starts after l3mdev_ip6_out(), so it cannot prevent the old route from being reclaimed in between. Reload the route from the current skb destination after l3mdev_ip6_out() returns. KASAN reports a slab-use-after-free in rawv6_sendmsg(), with the route allocated by ip6_dst_alloc(), freed by dst_destroy() from rcu_core(), and the related RCU callback queued from vrf_l3_out().

    Memory safety OS & kernel Linux

    7.0 HIGH No fix listed
  50. CVE-2026-132825

    Ruby before 3.3.14, 3.4.13, and 4.0.10 has a heap-based buffer overflow during case conversion. One byte can be written outside a buffer for, for example, ISO-8859-1 or Windows-1252.

    Memory safety Library ruby-lang Ruby

    7.4 HIGH Fix listed