GNU Binutils Linker elf-eh-frame.c _bfd_elf_parse_eh_frame heap-based overflow

GNU Binutils objdump.c dump_dwarf_section out-of-bounds

Libsoup: out-of-bounds read in cookie date handling of libsoup http library

Kubernetes: Vulnerability in Kubernetes NGINX Ingress Controller

Kubernetes: Vulnerability in Kubernetes NGINX Ingress Controller

missing SFTP host verification with wolfSSH

PostgreSQL quoting APIs miss neutralizing quoting syntax in text that fails encoding validation

Libxslt: use-after-free with key data stored cross-rvt

Chromium: CVE-2025-10892 Integer overflow in V8

Chromium: CVE-2025-10891 Integer overflow in V8

Chromium: CVE-2025-10890 Side-channel information leakage in V8

axboe fio init.c __parse_jobs_ini use after free

axboe fio options.c str_buffer_pattern_cb null pointer dereference

Use-after-free vulnerability in Qt SVG qsvghandler.cpp allows denial of service via crafted SVG

Uncontrolled recursion in Qt SVG module

Chromium: CVE-2025-10585 Type Confusion in V8

In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet). The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).

Chromium: CVE-2025-10502 Heap buffer overflow in ANGLE

Chromium: CVE-2025-10501 Use after free in WebRTC

Chromium: CVE-2025-10500 Use after free in Dawn