A security vulnerability (CVE-2026-5674) affecting PipeWire, a multimedia server for Linux and Unix-like systems, allows sandbox escape and arbitrary code execution via malicious library loading. Red Hat has issued an important security advisory for this vulnerability affecting Red Hat Enterprise Linux 9.6 Extended Update Support and related variants. A security update is available to address this issue.
CVE-2026-72462 is a race condition vulnerability in the Linux kernel's AppArmor security module affecting unix socket mediation when peer_path is used. The flaw arises because holding a reference to the peer socket is insufficient to guarantee safe access to the peer socket path, allowing a race with unix_release_sock(). This issue has been fixed by taking the state lock and obtaining a reference to the path under lock. The vulnerability affects multiple Linux kernel versions prior to 7.0.0-1014.14 and related builds. A high-severity CVSS 3.1 score of 8.8 reflects the potential for complete confidentiality, integrity, and availability compromise. Official patches are available in Linux kernel versions 7.0.0 and later for the affected builds.
CVE-2026-47766 is a vulnerability in crun, an open source OCI Container Runtime written in C. Prior to version 1.28, crun's default device setup opens the container root filesystem's /dev directory without the O_NOFOLLOW flag. This allows crun to follow symbolic links in the rootfs/dev directory, potentially creating device nodes and symlinks outside the container rootfs. This behavior can overwrite existing files such as ptmx. The issue is fixed in crun version 1.28.
A vulnerability exists in the os.Root functionality of the Go programming language on Unix systems, where symbolic links with trailing slashes are improperly followed, allowing directory traversal outside the intended root directory. This flaw affects Go versions starting from 1.24 and is fixed in Go 1.25.12 and 1.26.5. The issue impacts Red Hat's build of OpenTelemetry 3.10.2 and related products that use the affected Go versions and os.Root API. No other breaking changes, deprecations, or bug fixes are noted in this release.
A vulnerability in the Summarize daemon prior to version 0.15.1 allows local attackers to read sensitive configuration files due to insecure default filesystem permissions. These permissions may make the daemon configuration directory and file world-readable on Unix-like systems, exposing bearer tokens and API credentials stored in ~/.summarize/daemon.json. This exposure can lead to unauthorized access to the daemon or recovery of sensitive API keys.
CVE-2025-68146 is a Time-of-Check-Time-of-Use (TOCTOU) race condition in the filelock library affecting Unix, Linux, macOS, and Windows. It allows local attackers with filesystem access and symlink creation ability to exploit a race window during lock file creation, causing arbitrary user files to be truncated or corrupted via symlink attacks. This impacts dependent software such as virtualenv, PyTorch, poetry, and tox. The vulnerability is fixed in filelock version 3.20.1 by preventing symlink following during file open operations.
IBM Db2 12.1.5 for Linux, UNIX and Windows (includes DB2 Connect Server) could allow a local attacker to cause a denial of service due to a memory leak.
A symlink following vulnerability was found in KubeVirt's virt-handler migration proxy. During live migration, virt-handler dials Unix sockets inside the target virt-launcher pod via /proc/<pid>/root/ paths using net.Dial() without symlink protection. These socket paths reside in qemu-owned directories writable by the virt-launcher user. An attacker with namespace edit and pods/exec permissions can replace a migration proxy socket with a symlink to the host CRI-O socket. Because virt-handler runs as root in the host mount namespace, absolute symlink targets resolve against the host filesystem, and the bidirectional io.Copy proxy relays attacker-controlled bytes to the container runtime, enabling full node compromise.
When kuma-dp is configured with the Envoy admin API on a Unix domain socket, which is the default, its readiness service on TCP port 9902 - bound to all interfaces - forwards almost the entire Envoy admin API to any caller that can reach the port, with no authentication.
An attacker with network access to a data plane's port 9902, for example another pod on the cluster network, can read Envoy and data plane configuration without credentials: config dumps, cluster and listener lists, stats, and the mesh trust bundle. Exposure is read-only - destructive Envoy admin actions are blocked and private keys are not exposed.
A vulnerability in p11-kit used by Red Hat Update Infrastructure 5.2 allows an unauthenticated local attacker with access to the p11-kit RPC Unix domain socket to cause a stack exhaustion and crash the p11-kit server process by sending a specially crafted request with deeply nested template attributes. This leads to denial of service affecting dependent services such as SSH agents, VPN clients, and browsers. The issue is due to unbounded recursion in RPC attribute parsing functions. Red Hat recommends updating to p11-kit version 0.26.3 or later to address this flaw.
The npm package sme-rko-finance-front-operations-providers version 35.8.1 contains malicious code that, upon require(), downloads and executes an opaque platform-specific binary from suspicious Cloudflare Workers subdomains. It writes the binary to temporary directories, sets executable permissions on Unix, and runs it detached via shell commands. If HTTPS delivery is blocked, a DNS-TXT fallback channel reconstructs the payload from base64-encoded shards resolved from a suspicious domain (wel1.ru). The downloaded executable is unrelated to the package's declared purpose and is unverified, indicating malicious intent.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (6eb386f3b0d35ecf71762d0e719f883a3e1e207a2a3a9e1f52e7729de7753ae0)
On require(), index.js loads./_ext.js which selects a per-OS asset path and downloads a binary payload from one of three runtime-assembled Cloudflare Workers hosts (oob-worker.cf101-adf.workers.dev, oob-worker.cf100-416.workers.dev, oob-worker.cf102-baf.workers.dev), with a DNS TXT covert-channel fallback that reassembles a base64 payload from numbered subdomains under sdk.dl.wel1.ru, ext.dl.wel1.ru, pkg.dl.wel1.ru, and net.dl.wel1.ru. The fetched bytes are written to /var/tmp/.cache_<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmod 0755, and spawned detached via spawn("/bin/sh", ["-c", path + " &"]) or spawn("cmd",...). Host strings are constructed via array-split.join("") to evade static inspection, and there is no hash or signature verification. Staging paths mimic system diagnostics names to blend in.
## Source: ghsa-malware (b9e509d532bb46f434ea0a124cf22b50558357d28e0a316974709d2a7bde00dc)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (81ba08fb4c9c52336f51b45ebe9089ba0b441f3da79529ac1c56f146d71861b6)
On require(), _support.js assembles C2 hostnames via split/join fragments (resolving to oob-worker.cf100-416.workers.dev, cf103-070.workers.dev, cf101-adf.workers.dev) and downloads a platform-specific binary via https.get, with a DNS TXT fallback under dl.wel1.ru that reads a chunk count from c.<domain> and base64 chunks from N.<domain>. The fetched payload is written to %TEMP%/dotnet_diag_<hex>.exe on Windows or /var/tmp/.cache_<hex> on Unix, chmod 0755, and spawned detached via cp.spawn('/bin/sh', ['-c', fp + ' &'], {detached:true}).unref(). A /tmp/.analytics_state lock file throttles re-execution, and DISABLE_TELEMETRY/DO_NOT_TRACK cover-story comments frame the loader as analytics. No hash or signature check is performed on the downloaded binary. The package name mimics a legitimate Vite plugin.
## Source: ghsa-malware (fd80bad16653380e79b1cbe72e8e4fc7c6912c9117d537c7f00c1d721cd1e7e6)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (48ce2aa10d245536ed6cfd1903fe1b553eef84d8e949b0bd1b970817b7f13e98)
On require of the package, index.js loads _loader.js which reconstructs attacker-controlled hostnames via string-split.join('') to evade scanners (mirrors of the form oob-worker.cf10{0,1,2}-{baf,adf}.workers.dev and DNS TXT fallback domains under wel1.ru such as sdk.dl.wel1.ru / ext.dl.wel1.ru / pkg.dl.wel1.ru / net.dl.wel1.ru), selects a platform/arch-specific asset, downloads a binary from one of the anonymous Cloudflare Workers hosts (with a DNS-over-TXT fallback that base64-reassembles bytes from <n>.<domain> TXT records), writes it to /var/tmp/.cache_<rand> on Unix or %TEMP%\dotnet_diag_<rand>.exe on Windows, chmod 0755, and spawns it detached via /bin/sh -c or cmd.exe. A marker file named.analytics_state and comments referring to 'opt-out environment variables' present a telemetry cover story. There is no hash or signature verification on the downloaded bytes, the destinations are anonymous hosts unrelated to any legitimate publisher, and the package name itself is a lookalike combining unrelated brand/technology tokens.
## Source: ghsa-malware (2e59b1d946c38b9a6e256cc86700987daaf2338dba0e56b59a124da3e582af25)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (abfa5d8518650ddd83b31e9587264a2ed049a47db5c8452af6d62eb50e9fa336)
On load, index.js requires./_loader.js which reconstructs anonymous host names via array-join obfuscation (['oob-worker.cf100-416.work','ers.','dev'].join('') and ['sdk.dl.wel','1.','ru'].join('')), selects a platform-specific payload path, downloads an opaque binary from those hosts with a DNS-TXT fallback via *.dl.wel1.ru, writes it to /var/tmp/.cache_<hex> on Unix or TEMP\dotnet_diag_<hex>.exe on Windows, chmods it 0755, and spawns it detached via /bin/sh -c or cmd. A marker file gates re-runs and env-var checks provide a cover-story opt-out. lib/telemetry.js repeats the same shape using string-concatenation obfuscation for require('child_'+'process') and fs['chmod'+'Sync']. No hash or signature verification is performed; the destinations are anonymous, mutable CDN hosts unrelated to any declared purpose. Filename shape (dolyame-boxy-atom-bnpl-info-card) is also consistent with a lookalike/lure name.
## Source: ghsa-malware (600a1ec6272503e4b2b7e2c31a33b996c07fb5eb543a5169c483ea1e7cef7a67)
Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.