Chromium: CVE-2025-4664 Insufficient policy enforcement in Loader

OPA server Data API HTTP path injection of Rego

Libsoup: information disclosure may leads libsoup client sends authorization header to a different host when being redirected by a server

Libsoup: memory leak on soup_header_parse_quality_list() via soup-headers.c

In tar in BusyBox through 1.37.0, a TAR archive can have filenames hidden from a listing through the use of terminal escape sequences.

GitHub: CVE-2025-46334 Git Malicious Shell Vulnerability

Go Snowflake Driver has race condition when checking access to Easy Logging configuration file

PyTorch before 3.7.0 has a bernoulli_p decompose function in decompositions.py even though it lacks full consistency with the eager CPU implementation, negatively affecting nn.Dropout1d, nn.Dropout2d, and nn.Dropout3d for fallback_random=True.

In PyTorch before 2.7.0, bitwise_right_shift produces incorrect output for certain out-of-bounds values of the "other" argument.

In PyTorch before 2.7.0, when torch.compile is used, FractionalMaxPool2d has inconsistent results.

In PyTorch before 2.7.0, when inductor is used, nn.Fold has an assertion error.

In PyTorch through 2.6.0, when eager is used, nn.PairwiseDistance(p=2) produces incorrect results.

Chromium: CVE-2025-4609 Incorrect handle provided in unspecified circumstances in Mojo

Systemd-coredump: race condition that allows a local attacker to crash a suid program and gain read access to the resulting core dump

pyjwt v2.10.1 was discovered to contain weak encryption. NOTE: this is disputed by the Supplier because the key length is chosen by the application that uses the library (admittedly, library users may benefit from a minimum value and a mechanism for opting in to strict enforcement).

The x509 application adds trusted use instead of rejected use

Crossbeam-channel: crossbeam-channel vulnerable to double free on drop

Unbounded recursion in Python Protobuf

Nodes can bypass dynamic resource allocation authorization checks

GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in wh