CVE-20XX-?
agent?

Just published.

The newest CVEs, straight from CVE.org and NVD.

3,361 CVEs · updated 2026-11-19 15:16 UTC

Reset all
  1. 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
  2. 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
  3. CVE-2026-59007

    In decode_packed_entry_number of codebook.c, there is a possible out-of-bounds read due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Device Google Android

    5.3 MEDIUM 0.2% exploit odds Fix listed
  4. CVE-2026-58984

    In multiple locations, there is a possible memory corruption due to a use-after-free. 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
  5. 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
  6. CVE-2026-58990

    In l2c_fcr_process_peer_cfg_req of l2c_fcr.cc, there is a possible memory safety issue due to an integer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    5.3 MEDIUM 0.2% exploit odds Fix listed
  7. 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
  8. 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
  9. CVE-2026-58968

    In oapvd_vlc_metadata of oapv_vlc.c, there is a possible memory corruption due to a double free. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    9.8 CRITICAL 0.3% exploit odds Fix listed
  10. 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
  11. 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
  12. 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
  13. CVE-2026-58942

    In do_fault_around of memory.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 no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  14. CVE-2026-58949

    In parseMetaData of StagefrightMetadataRetriever.cpp, there is a possible denial of service due to a stack buffer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    7.5 HIGH 0.3% exploit odds Fix listed
  15. CVE-2026-58953

    In dec_vlc_read of oapv_vlc.c, there is a possible out-of-bounds read due to a heap buffer overflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    5.3 MEDIUM 0.2% exploit odds Fix listed
  16. CVE-2026-58882

    In decodeWapPdu of WapPushOverSms.java, there is a possible out of bounds read due to an integer overflow. This could lead to a remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    7.5 HIGH 0.4% exploit odds Fix listed
  17. CVE-2026-58933

    In process of C2SoftApvDec.cpp, there is a possible out-of-bounds read due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    5.3 MEDIUM 0.2% exploit odds Fix listed
  18. CVE-2026-58936

    In png_set_tRNS of pngset.c, there is a possible memory corruption due to a use-after-free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    9.8 CRITICAL 0.3% exploit odds Fix listed
  19. CVE-2026-58868

    In onOutputReceived of FrameDecoder.cpp, there is a possible out-of-bounds write due to a heap buffer overflow. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    9.8 CRITICAL 0.4% exploit odds Fix listed
  20. 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
  21. CVE-2026-58876

    In multiple locations, there is a possible memory safety issue due to a use-after-free. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    9.8 CRITICAL 0.3% exploit odds Fix listed
  22. 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
  23. CVE-2026-58844

    In multiple locations, there is a possible out of bounds read/write due to an incorrect 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 Google Android

    8.4 HIGH 0.2% exploit odds Fix listed
  24. CVE-2026-58845

    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 Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  25. CVE-2026-58847

    In kvm_vfio_pviommu_attach of vfio.c, there is a possible double free due to a logic error in the code. 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

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

    In multiple functions of ipphelper.c, there is a possible stack bugger overflow due to a missing bounds check. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    7.5 HIGH 0.4% exploit odds Fix listed
  27. CVE-2026-58857

    In decrypt of CryptoHalHidl.cpp, there is a possible use-after-free due to a race condition. This could lead to remote code execution with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    8.1 HIGH 0.3% exploit odds Fix listed
  28. CVE-2026-58824

    In __pkvm_load_tracing of trace.c, there is a possible out-of-bounds write due to an incorrect 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 OS & kernel Google Android

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

    In multiple functions of fork.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 no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety OS & kernel Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  30. CVE-2026-58826

    In ksys_unshare of fork.c, there is a possible memory corruption due to a use after free. 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

    8.4 HIGH 0.2% exploit odds Fix listed
  31. CVE-2026-58827

    In multiple functions of dma-buf.c, there is a possible use after free 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 Google Android

    8.4 HIGH 0.1% exploit odds Fix listed
  32. CVE-2026-58828

    In multiple functions of base.c, there is a possible use-after-free 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 Google Android

    8.4 HIGH 0.2% exploit odds Fix listed
  33. CVE-2026-58829

    In fuse_backing_mmap of backing.c, there is a possible memory corruption due to a use after free. 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

    8.4 HIGH 0.1% exploit odds Fix listed
  34. CVE-2026-58814

    In parseContentType of PduParser.java, there is a possible denial of service due to an integer overflow. This could lead to remote denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    7.5 HIGH 0.3% exploit odds Fix listed
  35. CVE-2026-55292

    In rw_ci_data_cback of rw_ci.cc, there is a possible memory safety issue due to integer underflow. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    5.3 MEDIUM 0.2% exploit odds Fix listed
  36. CVE-2026-55275

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

    Memory safety Google Android

    8.4 HIGH 0.2% exploit odds Fix listed
  37. CVE-2026-55283

    In multiple locations, there is a possible memory safety issue due to a use-after-free. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

    Memory safety Google Android

    8.4 HIGH 0.2% exploit odds Fix listed
  38. CVE-2026-119739

    The VobSub subtitle decoder libsub_vob (part of the Amlogic DroidLogic SubTitleService), as shipped on Nexbox A95X (Amlogic S905X) TV boxes, contains an out-of-bounds write vulnerability in vob_fill_pixel() that allows remote attackers to corrupt stack memory by sending a crafted SET_CONTR command with an attacker-controlled alpha value that drives an unbounded array index (change_data) past the end of the fixed four-element PixelDatas array. Attackers can exploit this by sending malicious VobSub data over the unauthenticated tcp/10100 socket or via a malicious .sub file to zero out adjacent stack bytes, resulting in silent stack corruption or process crash.

    Memory safety Device

    6.9 MEDIUM 0.4% exploit odds No fix listed
  39. CVE-2026-120067

    For updatable cursors, which are enabled by default, psqlODBC adds hidden ctid and, for tables with OIDs, oid columns to the query. It copies each value into a 32-byte stack buffer using the length the server sent, without checking it against the buffer size, so a value of 32 bytes or more writes past the buffer. A server not trusted under current SSL settings can send such a value. So can any database user who can create a view with its own column named ctid that the application reads with an updatable cursor. Builds with _FORTIFY_SOURCE abort; other builds overwrite adjacent stack memory. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety Server

    5.9 MEDIUM 0.3% exploit odds Fix listed
  40. CVE-2026-120060

    psqlODBC trusts counts and lengths in server data in three places. SQLBulkOperations uses a server-supplied row count in a size subtraction that can underflow. SQLStatistics iterates index keys using a server-supplied key count without bounding it to the fixed storage. Bytea octal decoding reads up to two bytes past the end of a truncated escape sequence. A server not trusted under current SSL settings can crash the client or make it read out of bounds. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety Server

    5.9 MEDIUM 0.2% exploit odds Fix listed
  41. CVE-2026-120061

    The psqlODBC parser for ODBC escape sequences in application SQL text writes the argument offsets of a {fn} escape into a fixed 16-entry stack array without a bound and does not initialize the array. An escape with too many arguments overflows the stack, and a reference to an unsupplied argument copies arbitrary bytes into the query. The copy of a {d}, {t}, {ts}, or {escape} body also writes one byte past a 128-byte stack buffer. An application that forwards untrusted SQL text to the driver exposes its process to memory corruption. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety OS & kernel

    7.5 HIGH 0.3% exploit odds Fix listed
  42. CVE-2026-120063

    When psqlODBC quotes a schema or table name into a 128-byte stack buffer, its length check lets it write up to two bytes past the end of the buffer for a long name. The names come from the application's SQL text: the table of a statement the driver parses to describe its columns, and the target of the last INSERT when the driver rewrites SELECT @@IDENTITY. In the @@IDENTITY rewrite, a column name sent by the server can also write one byte past the buffer. The bytes written past the buffer are a double quote and a NUL. An application that forwards untrusted SQL text to the driver exposes its process to stack corruption. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety Server

    5.9 MEDIUM 0.3% exploit odds Fix listed
  43. CVE-2026-120064

    Several psqlODBC entry points use an application-supplied column number or row index as an array index without validating it. SQLBindCol with a column number above 32767 wraps the binding count negative and a later copy runs off the array. A negative SQL_DESC_COUNT on an application row descriptor unbinds columns at negative indexes. SQLColAttribute with a very large column number uses a negative index. SQLSetPos(SQL_ADD) does not check the row number against the rowset size. An application that forwards untrusted column or row numbers exposes its process to out-of-bounds reads and writes. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety Server

    7.5 HIGH 0.3% exploit odds Fix listed
  44. CVE-2026-120057

    psqlODBC copies the reply to a large-object read (loread) into the application's buffer using the length sent by the server, without comparing it to the buffer size. A server not trusted under current SSL settings, or a man-in-the-middle, can return more bytes than the buffer holds and overwrite adjacent memory in the client process with server-chosen bytes. Fetching any large-object column is sufficient to trigger it. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety Server

    7.5 HIGH 0.2% exploit odds Fix listed
  45. CVE-2026-120058

    psqlODBC sizes its row cache from the column count of a cursor's first result, but recomputes the column count from each later FETCH reply without checking that it matches. A server not trusted under current SSL settings can answer a later FETCH with more columns and make the driver write tuple records past the end of the heap allocation. A keyset reply with fewer columns than the key fields also underflows the unsigned field count. This is reachable with UseDeclareFetch enabled. Versions before psqlODBC 18.00.0006 are affected.

    Memory safety Server

    7.5 HIGH 0.3% exploit odds Fix listed
  46. CVE-2026-117068

    An integer underflow vulnerability in the NAS decoder of OpenAirInterface (OAI) CN5G AMF v2.2.1 allows an unauthenticated remote attacker to cause a denial of service (DoS) via crafted NAS Registration Requests containing a truncated SUCI in the 5GS Mobile Identity IE. Insufficient length validation in the DecodeSuci() function results in an out-of-bounds heap read, causing the AMF process to crash.

    Memory safety

    7.5 HIGH 0.4% exploit odds Fix listed
  47. CVE-2026-106808

    OpenAirInterface Core Network v2.2.1 has a stack-based buffer overflow vulnerability in the OAI CN5G UDM Nudm_UEAU Generate Authentication Data endpoint. The UDM passes attacker-controlled resynchronizationInfo.rand and auts values to conv::hex_str_to_uint8(), which converts arbitrary-length hex strings into fixed-size stack buffers without validating the destination size. An unauthenticated attacker with access to the SBI interface and a valid SUPI can submit an oversized value to overwrite adjacent stack memory, corrupt the stack canary, and terminate the UDM process.

    Memory safety

    7.5 HIGH 0.5% exploit odds No fix listed
  48. CVE-2026-106803

    A stack-based buffer overflow exists in Kamailio v6.1.3 and v6.1.4 in the ims_registrar_pcscf module. When processing a crafted application/reginfo+xml NOTIFY message, process_contact() copies an attacker-controlled port value from the alias parameter into a fixed 5-byte stack buffer without validating its length. An unauthenticated remote attacker can trigger stack corruption and terminate the P-CSCF process, resulting in denial of service.

    Memory safety Library

    9.8 CRITICAL 0.5% exploit odds Fix listed
  49. CVE-2026-106804

    A stack-based buffer overflow exists in Kamailio v6.1.3 and v6.1.4 in the ims_qos_npn module. The w_rx_aar_register() function copies the attacker-controlled host field from the SIP `Via` header into a fixed 46-byte stack buffer without validating its length. An unauthenticated remote attacker can trigger the vulnerability with a crafted SIP `REGISTER` request, causing stack corruption and termination of the affected Kamailio instance, resulting in denial of service.

    Memory safety Library

    7.5 HIGH 0.6% exploit odds No fix listed
  50. CVE-2026-99235

    In the Linux kernel, the following vulnerability has been resolved: tracing: Save the event file instead of the compatible histogram create_field_var_hist() creates a histogram on the matched event to supply a field variable, and records it on the target so it can be torn down later: hist_data = find_compatible_hist(target_hist_data, file); ... /* Save the compatible histogram information */ var_hist->hist_data = hist_data; hist_data is not the histogram it creates. It is one that was already there, whose keys the new one copies. The saved pointer has a single user, unregister_field_var_hists(), which runs when the target is removed: file = hist_data->field_var_hists[i]->hist_data->event_file; find_compatible_hist() matches on keys alone, so it can pick one with no variables of its own. check_var_refs() then returns false and the user can remove it while the target still points at it: BUG: KASAN: slab-use-after-free in event_hist_trigger_free+0x2b2/0x320 Read of size 8 at addr ffff8880093b90e0 by task init/1 Freed by task 1: kfree+0x154/0x420 event_hist_trigger_free+0x1d5/0x320 event_hist_trigger_parse+0x35f3/0x69e0 trigger_process_regex+0x1a6/0x250 Save the event file instead. It is all the dereference ever wanted, and it does not go away when the user removes a trigger.

    Memory safety OS & kernel

    7.8 HIGH 0.1% exploit odds No fix listed

The newest published CVE records from CVE.org and NVD, refreshed every few minutes, with severity, exploit odds and fix status.