Tarfile infinite loop during parsing with negative member offset

LibTIFF thumbnail.c setrow buffer overflow

LibTIFF tiffmedian.c get_histogram use after free

: null pointer dereference in libssh kex session id calculation

Chromium: CVE-2025-8011 Type Confusion in V8

Chromium: CVE-2025-8010 Type Confusion in V8

Usage of unsafe random function in form-data for choosing boundary

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

Chromium: CVE-2025-7656 Integer overflow in V8

GNU Binutils elf.c bfd_elf_set_group_contents out-of-bounds write

GNU Binutils objcopy.c copy_section heap-based overflow

Polkit: xml policy file with a large number of nested elements may lead to out-of-bounds write

SQLite integer overflow in key info allocation may lead to information disclosure.

Libxslt: heap use-after-free in libxslt caused by atype corruption in xmlattrptr

Libxslt: type confusion in xmlnode.psvi between stylesheet and source nodes

Domain Name Validation Bypass with Apple Native Certificate Validation

In the OpenSSL compatibility layer implementation, the function RAND_poll() was not behaving as expected and leading to the potential for predictable values returned from RAND_bytes() after fork() is called. This can lead to weak or predictable random numbers generated in applications that are both using RAND_bytes() and doing fork() operations. This only affects applications explicitly calling RAND_bytes() after fork() and does not affect any internal TLS operations. Although RAND_bytes() documentation in OpenSSL calls out not being safe for use with fork() without first calling RAND_poll(), an additional code change was also made in wolfSSL to make RAND_bytes() behave similar to OpenSSL after a fork() call without calling RAND_poll(). Now the Hash-DRBG used gets reseeded after detecting running in a new process. If making use of RAND_bytes() and calling fork() we recommend updating to the latest version of wolfSSL. Thanks to Per Allansson from Appgate for the report.

Gdk‑pixbuf: heap‑buffer‑overflow in gdk‑pixbuf

on-headers vulnerable to http response header manipulation

mruby nregs codegen.c scope_new heap-based overflow