A vulnerability in Node.js HTTP/2 session teardown allows any unauthenticated client to abort the server process by triggering a reachable assertion failure. This occurs when an Http2Stream holding nghttp2-allocated header buffers outlives its session, causing a memory accounting assertion to fail and terminate the process. The issue affects Node.js versions 26.x (since 26.9.0) and 24.x (since 24.22.0).
A vulnerability in the Node.js zlib streaming API can cause an uncatchable exception that crashes the process when a peer disconnects during data compression. This occurs if deflate.params() is called while streaming, which is uncommon. The issue affects Node.js versions 22.x, 24.x, and 26.x. The CVSS score is low, reflecting limited impact and exploitability.
CVE-2026-123829 is a permission model bypass vulnerability in Node.js recursive file watching on macOS and Windows. It allows processes with read permission on a directory to learn the names and timing metadata of files and directories within subdirectories they cannot read. The flaw affects Node.js versions 22.x, 24.x, and 26.x and does not disclose file contents, only metadata. Exploitation requires files created by another actor under the watched directory.
A one-byte heap buffer overflow vulnerability exists in Node.js HTTP/2 Alt-Svc handling. This flaw allows a remote, unauthenticated attacker to corrupt process memory by sending a specially crafted request with a long but valid :authority header. The vulnerability affects Node.js versions 24.x and 26.x. Exploitation results in process abort due to out-of-bounds write, potentially enabling denial of service or other memory corruption impacts.
A vulnerability in the xfs_admin utility of xfsprogs allows local attackers to execute arbitrary operating system commands due to improper validation of user-supplied parameters. This flaw can lead to local privilege escalation depending on how xfs_admin is executed. The vulnerability affects multiple specific versions of xfsprogs, including various Ubuntu package versions. Red Hat rates this vulnerability as important and has not provided an official fix or mitigation that meets their criteria.
A buffer overflow vulnerability exists in the GNU C Library (eglibc) versions 2.2 through 2.44 when calling wide scanf functions (such as swscanf, fwscanf, wscanf, vswscanf, vfwscanf, and vwscanf) with %s or %[ conversions without the 'l' length modifier. This causes an extra null byte to be written one byte past the end of the destination array if the converted multibyte string exactly fills the buffer, potentially corrupting adjacent memory or crashing the process.
The regcomp and regexec functions in GNU C Library versions 2.3 to 2.44 may read freed memory and free the same heap block twice if a memory allocation fails during regular expression compilation or matching. This can cause a process crash under memory pressure conditions. The issue affects all architectures and ABIs supported by the GNU C Library.
Red Hat Quay 3.14.10 is a container image registry that has been updated in a critical security advisory. The advisory includes multiple fixes addressing a wide range of vulnerabilities identified by numerous CVEs, including CVE-2026-49825. The update provides container images for Red Hat Quay 3.14.10 and references detailed release notes for further information.
An integer overflow vulnerability exists in the volume_id component of BusyBox when calculating buffer boundaries during filesystem metadata probing. This flaw can be triggered by an attacker supplying a specially crafted filesystem image on an attached storage device. When utilities like blkid, findfs, or mount probe the malicious filesystem, the application crashes, causing a denial of service that prevents mounting or resolving storage devices. The vulnerability primarily affects minimal environments or rescue shells using BusyBox for filesystem probing. Standard Red Hat Enterprise Linux systems using util-linux are not significantly exposed. No effective mitigation or patch is currently available that meets Red Hat's criteria.
A vulnerability in BusyBox's tar utility allows improper resolution of deferred hardlink targets across symbolic links pointing outside the extraction directory. This flaw can be exploited by an attacker providing a specially crafted archive to overwrite arbitrary files on the system during extraction. The vulnerability requires local user interaction to extract the archive and has a medium severity rating with a CVSS score of 6.3. In typical Red Hat environments, exposure is minimal since BusyBox is mainly used in constrained environments rather than general extraction workflows. No effective mitigation or patch meeting Red Hat's criteria is currently available.
A vulnerability in BusyBox's cpio utility with path traversal protection enabled allows crafted archives to create hardlinks pointing outside the extraction directory. This can enable attackers to modify or overwrite arbitrary files outside the intended extraction path during subsequent extraction operations. Exploitation requires user or automated process interaction to extract a malicious archive. The issue is rated medium severity with a CVSS score of 6.3. Red Hat notes limited exposure due to BusyBox's specialized use in their distributions and no current mitigation meeting their criteria is available.
Multiple vulnerabilities in OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13 allow crafted EXR files to cause memory corruption issues including integer overflow, out-of-bounds reads and writes, use-after-free, and crashes. These flaws affect the decoding and processing of deep tiled EXR files and arise from improper handling of dataWindow origins and buffer size calculations. The issues are fixed in versions 3.2.11, 3.3.13, and 3.4.14.
A use-after-free vulnerability exists in BusyBox's udhcpc6 DHCPv6 client. A malicious local network DHCPv6 server can send a crafted reply lacking usable address options, causing the client to read stale heap memory. This may lead to a denial of service via application crash or disclosure of previously assigned network address data in subsequent discovery requests. The vulnerability requires an adjacent attacker and affects custom environments where BusyBox udhcpc6 is used, but not standard Red Hat Enterprise Linux installations which use NetworkManager by default.
A vulnerability in BusyBox's volume identification component for HFS+ filesystems allows improper validation of header values. An attacker with local access to attach a storage device or supply a crafted filesystem image can cause an application crash, leading to denial of service and preventing device resolution. This flaw is rated medium severity with a CVSS score of 5.5. The impact is limited to local denial of service without confidentiality or integrity loss. BusyBox is typically used in rescue or initramfs environments, reducing exposure in standard enterprise workflows. No official fix or mitigation is currently available that meets Red Hat's criteria for ease of use and deployment.
A vulnerability in BusyBox's volume identification component causes improper validation of cluster parameters in FAT filesystems. This flaw can be triggered by presenting a specially crafted storage device or disk image, leading to a divide-by-zero error during partition scanning. The resulting crash causes a denial of service (DoS), potentially disrupting device discovery and system boot processes. The issue requires local access or the ability to supply crafted storage media. It primarily affects recovery environments or minimal container images using BusyBox for storage probing. No official fix or mitigation is currently available that meets Red Hat's criteria.
A vulnerability in BusyBox's HTTP daemon (httpd) with pre-compressed file support enabled allows authentication checks to be bypassed. The flaw occurs because authentication is checked against the requested URL path, not the actual pre-compressed file served. An attacker can exploit this by requesting an uncompressed file path with gzip encoding, bypassing password protections configured for the compressed file. This can lead to unauthorized disclosure of sensitive files. The issue is considered moderate risk due to its niche configuration requirements and limited exposure in typical deployments. Mitigations include configuring directory-level authentication, protecting both uncompressed and compressed filenames, or restricting network access to the httpd service.
A stack-based buffer overflow vulnerability exists in the udhcpc6 DHCPv6 client of BusyBox due to improper validation of network option sizes received from a DHCPv6 server. An attacker on the local network with control over a malicious DHCPv6 server can exploit this flaw to execute arbitrary code with root privileges or cause a denial of service (DoS) by crashing the client process. This vulnerability affects BusyBox versions used in specialized or embedded environments where udhcpc6 is explicitly invoked for IPv6 configuration. Standard Red Hat Enterprise Linux installations are not exposed as they use NetworkManager instead of BusyBox for networking. No effective mitigation or patch is currently available that meets Red Hat's criteria for ease of use and stability.
A stack-based buffer overflow vulnerability exists in BusyBox's httpd web server when processing subdirectory configuration files with an overly long index page name. An attacker with write permissions to such configuration files could exploit this flaw to execute arbitrary code with elevated privileges or cause a denial of service by crashing the server process. The vulnerability requires the BusyBox httpd service to be running and serving content from directories writable by untrusted users. Mitigations include restricting write permissions on web directories and running the httpd process under an unprivileged user account.
A heap buffer overflow vulnerability exists in the BusyBox TFTP client when it requests a custom small block size and then falls back to the default block size without resizing the allocated memory buffer. A malicious TFTP server can exploit this by sending standard-sized packets, potentially leading to arbitrary code execution or denial of service by crashing the client application. This flaw requires an active connection to an untrusted server using a non-default, reduced block size. The vulnerability has been rated as high severity with a CVSS score of 7.5.
A security advisory from Red Hat addresses multiple vulnerabilities in Red Hat AI Base Images 3.5.7 (ROCm 7.14), including CVE-2026-11856 which affects libcurl. This libcurl flaw involves incorrect reuse of Digest authentication headers across different HTTP origins, potentially leading to unintended information disclosure. The vulnerability requires a specific programming pattern where a libcurl handle is reused improperly. No fixes are currently provided in the Red Hat AI Base Images 3.5.7 release. The advisory highlights the importance of correct libcurl handle usage to mitigate this issue.