Multiple security issues were addressed in the libosmocodec-devel-1.14.2-2.1 package for openSUSE Tumbleweed. These fixes resolve vulnerabilities present in prior versions of the package. No specific details about the nature of the vulnerabilities or their impact are provided.
Apache Wicket versions 9.14.0 through 9.24.0 and 10.0.0 through 10.9.1 contain a vulnerability in the form-less file upload resource where resource allocation limits can be bypassed by client-supplied parameters. This allows an unauthenticated attacker to upload arbitrarily large files or many parts without effective size or count limits, potentially exhausting server disk or memory resources. The issue does not affect the ordinary upload paths and is fixed in versions 9.25.0 and 10.12.0.
CVE-2026-83594 is a high-severity vulnerability in Apache Wicket affecting versions 9.14.0 through 9.24.0 and 10.0.0 through 10.11.0. It involves memory allocation with an excessive size value in the FileUploadToResourceField component, which can be exploited by sending crafted requests that cause the server to allocate large byte arrays, potentially exhausting heap memory. The vulnerability arises because the component trusts client-supplied JSON data about file uploads without verifying the actual stored files. The issue is fixed in Apache Wicket versions 9.25.0 and 10.12.0.
PrefabHQ prefab-ui versions 0.14.0 through 0.20.2 contain a critical protection mechanism failure in the Generative UI sandbox. The sandbox runs caller-supplied Python code inside Pyodide within a Deno subprocess but starts Deno with unrestricted read, write, and network permissions. This allows an attacker supplying code to read and write files as the server OS user and persist code execution by writing files into the server's virtual environment. The vulnerability is fixed in version 0.21.0 by revoking Deno permissions before accepting code and restricting network access.
This security update for the SUSE Linux Enterprise Kernel 4.12.14-122.275 addresses multiple security vulnerabilities affecting various kernel components such as crypto, xfrm, sctp, ipvs, SUNRPC, nfsd, and ipv4. The update fixes issues including improper handling of initialization vectors, stale pointers after asynchronous crypto operations, overflow in peer transport count, improper clearing of IPv4 options, error path bugs in SUNRPC, buffer length underflow, incorrect XDR length calculation, and freeing of options after RCU grace periods.
FFmpeg versions 2.3 through 9.0.2 contain a vulnerability in the Huffyuv decoder where uninitialized heap memory can be leaked into decoded video frames. This occurs when processing crafted Huffyuv BGR24/BGRA videos with entropy data that ends prematurely, causing uninitialized bytes to be included in output frames and exposing heap contents.
FFmpeg versions 4.4 through 9.0.2 contain a use of uninitialized variable vulnerability in the CDXL decoder. This flaw causes stack memory to leak into decoded pixels via unfilled HAM palette entries. An attacker can craft a specially designed type-0 CDXL file to expose stack bytes and pointer fragments in the BGR24 output.
FFmpeg versions 0.10 through 9.0.2 contain a vulnerability in the sunrast_decode_frame() function where uninitialized heap memory can be leaked when decoding truncated 1-bit and 4-bit paletted Sun Raster images. This occurs because the temporary bitmap is not cleared properly, leading to exposure of stale heap contents in the decoded output.
FFmpeg versions 2.1 through 9.0.2 contain a vulnerability in the PCX image decoder where uninitialized heap memory can be leaked. This occurs when a crafted PCX image has truncated RLE scanline data, causing the decoder to copy uninitialized buffer contents into the decoded output. The vulnerability has a medium severity rating and can lead to information disclosure.
FFmpeg versions 2.0 through 9.0.2 contain a use of uninitialized variable vulnerability in the Go2Meeting decoder. This flaw allows attackers to leak stack memory by crafting a specially designed G2M3/G2M4 stream with a short Kempf palette, causing uninitialized stack bytes to be copied into the decoded output. The vulnerability has a medium severity with a CVSS score of 5.5.
FFmpeg versions 5.0 through 9.0.2 contain a path traversal vulnerability in the IMF demuxer. This flaw allows attackers to open files outside the intended package by using crafted ASSETMAP Path elements with '..' or absolute paths. Exploitation can lead to unauthorized reading of local MXF files, probing file existence and size, or triggering server-side requests.
ShowDoc versions from 2.8.14 up to but not including 3.9.6 contain a code injection vulnerability in the Mock feature. Authenticated users can exploit this flaw by storing specially crafted mockjs templates that execute shell commands with root privileges in the official Docker image. The vulnerability is fixed in version 3.9.6.
joserfc version range >=2.14.0_4 <2.15.0_5 has a vulnerability where the compact JWS size guard allocates attacker-controlled segments before rejecting them, causing unnecessary memory allocation. This occurs because the library calls bytes.split() on the input before validating its size, leading to a copy of the payload being made even if it will be rejected. The issue is fixed in version 2.15.0_5.
OAuthlib contains a vulnerability in its token grant handlers where an authenticated client can supply a different client_id in the token request body, causing grant and scope validation to be performed under that other client identity. This affects the client_credentials and Resource Owner Password Credentials grant flows. The flaw allows a lower-privilege client to obtain tokens with scopes or grant types assigned to a higher-privilege client if the application validator authorizes based on the attacker-supplied client_id argument. The issue is fixed in OAuthlib versions 1.1.3 and 2.14.1_5.
The Hustle WordPress plugin (up to version 7.8.14.3) has an authorization bypass vulnerability that allows authenticated users with the hustle_create capability to overwrite the site's active email service provider (ESP) integration credentials. This can redirect lead submissions to an attacker-controlled ESP account and, in the case of HubSpot, delete critical OAuth tokens irreversibly.