Red Hat OpenShift Container Platform 4.22.12 includes multiple security fixes addressing vulnerabilities in components such as curl, bind9, dracut, unbound, kernel smb client, and kbd. These vulnerabilities range from man-in-the-middle attacks, cache poisoning, denial of service, to local privilege escalation. Users of OpenShift Container Platform 4.22 are advised to upgrade to this release to mitigate these issues.
Composer is a dependency Manager for the PHP language. From 1.0 until 2.2.30 and 2.10.3, a malicious dependency package from a custom Composer repository or an untrusted composer.lock file could set source.type to perforce and source.url to an rsh: or jsh: P4PORT value. When the Perforce p4 client was installed and Composer installed the package from source through composer install or composer update, including --prefer-source, Composer\Util\Perforce passed the address to p4 without validation, causing p4 to run a local command with the privileges of the user or CI account. Packagist.org does not permit Perforce source metadata. This issue is fixed in versions 2.2.30 and 2.10.3.
Between August 28 and August 30, 2026, attackers conducted a BGP hijacking attack targeting the update infrastructure of Virtualizor VPS management software by Softaculous. This attack rerouted update requests to malicious servers, resulting in a small number of Virtualizor installations receiving malicious update packages. The vendor confirmed the impact was limited to a handful of servers and has since restored routing, revoked fraudulent certificates, and released a new Virtualizor version 3.2.9.9 with enhanced security features. Softaculous recommends affected users check for malicious services, rotate API credentials, audit systems for unauthorized access, and reset passwords if they accessed the client area during the incident. The investigation is ongoing, and no other Softaculous products appear affected.
A OS command injection vulnerability in yast2-auth-client allows an attacker who controls Active Directory configuration values to execute arbitrary commands as root on the configured host.
Auth::AuthConf in src/lib/auth/authconf.rb assembles the Samba net ads join, net ads lookup -S and net ads testjoin invocations by interpolating configuration values into a single command string and passing that string to Open3.popen2 / Open3.capture2, which causes Ruby to run it through /bin/sh. The Organizational Unit (ou), dnshostname, AD user name and AD domain name values are neither validated nor shell-quoted.
A flaw in the Node.js HTTP client can cause request desynchronization in Node.js-based forwarding proxies that rebuild outbound headers from visible IncomingMessage headers while reusing backend connections. This occurs because Node.js may omit headers beyond configured limits from user-visible header collections but still use those omitted headers internally for HTTP message framing, potentially hiding headers like Content-Length from userland. This affects all supported Node.js release lines including versions 22, 24, and 26. The CVSS score is 3.7, indicating medium severity.
A flaw in Node.js HTTP client can cause a request desynchronization for Node.js-based forwarding proxies that rebuild outbound headers from the visible `IncomingMessage` headers while piping the original body to a reused backend connection.
Node.js can omit headers beyond `maxHeadersCount` / `maxHeaderPairs` from `req.headers`, `req.rawHeaders`, and `req.headersDistinct`, while still using those omitted headers internally for HTTP message framing. In particular, `Content-Length` can be hidden from userland while the request body is still delivered.
This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
WWBN AVideo (current e01e41ecc and earlier) contains a brute-force rate limiting bypass in enforceRateLimit(), which protects login.json.php and 13 other endpoints. The function stores its attempt counter via a cache layer (ObjectYPT::setCacheGlobal) that silently discards writes for any client identified as a bot by isBot(). Because isBot() treats a missing User-Agent header as a bot by default — and also matches common bot identifiers such as 'curl', 'bot', 'crawler', and 'spider' — the counter never increments for such clients, so the rate limit never fires. An unauthenticated attacker can therefore submit unlimited login attempts (e.g., by omitting the User-Agent header or using curl's default User-Agent), enabling unrestricted password-guessing attacks.
startServer.ts in the mcp-http-server package of UI-TARS-desktop defaulted its listen address to '::' when no host was given, so startSseAndStreamableHttpMcpServer bound the Streamable HTTP and SSE MCP transports to every interface, and its authentication middleware was optional: middlewares are applied only when a caller supplies them. The @agent-infra/mcp-server-commands and @agent-infra/mcp-server-filesystem entry points call startSseAndStreamableHttpMcpServer with a host and port alone and pass no middleware, so neither server required a credential. The commands server exposes a run_command tool that hands its caller-supplied command string to promisify(child_process.exec), so any unauthenticated client able to reach the port could run arbitrary commands as the user running the server, and the filesystem server exposed its file read and write tools on the same terms. The listen default became 127.0.0.1 in commit c2ad42e3eb9b27830db41a3e6f51ca7179d9b168; the package version stayed at 1.2.4 across that change, so the boundary is the commit rather than a release.
Android 17 introduces Encrypted Client Hello (ECH) support to enhance user privacy by encrypting the hostname in TLS handshakes, preventing network observers from easily seeing visited websites. This platform-level integration works with compatible apps and browsers, such as Chrome 117+ and Firefox 119+, to obscure domain names from ISPs and Wi-Fi operators. Additional network protections include requiring app permissions for local network scanning, enabling Certificate Transparency by default, and allowing mobile operators to disable 2G to reduce exposure to certain attacks.
CVE-2026-80349 is a critical authentication bypass vulnerability in TarsCloud TarsWeb versions up to 3.0.14. The vulnerability arises because TarsWeb trusts the client-controlled X-Forwarded-For header without properly validating it, allowing an attacker to spoof the loopback address. This spoofing combined with a crafted uid query parameter enables unauthorized access as any user, including administrators, without credentials. Version 3.0.16 addresses this by separating the logic for trusted IPs and ignoring paths, assigning a default account instead of the user-supplied uid when the request comes from a trusted IP. The vulnerability has a CVSS 4.0 score of 9.3, indicating critical severity. No official patch or remediation level is currently confirmed.
Doorkeeper OpenID Connect versions prior to 1.10.4 have an improper authorization vulnerability in the Dynamic Client Registration endpoint. The endpoint accepts client-supplied scopes without validating them against the server's configured scopes, allowing self-registered clients to obtain unauthorized scopes. This privilege escalation is due to the scopes attribute being assigned directly from user input without validation, combined with default configuration settings that do not enforce scope restrictions. The issue is fixed in version 1.10.4.
CVE-2026-62861 is an authorization bypass vulnerability in typebot.io prior to version 3.18.0. Authenticated non-guest workspace members could remove another workspace's public custom domain, causing typebots on that domain to become unavailable. The flaw arises because the delete handler authorizes based on a client-supplied workspaceId but sends the client-supplied domain name to the shared Vercel project before verifying domain ownership. This issue is fixed in version 3.18.0.
CVE-2026-77585 is an OS command injection vulnerability in the Okta Privileged Access Client. The client does not properly reject usernames starting with a hyphen in SSH targets, causing the SSH process to potentially interpret the username as a command-line option. This flaw could lead to unauthorized command execution under certain conditions. The vulnerability has a medium severity with a CVSS score of 5.3. No patch or official remediation guidance is currently available.
CVE-2026-79717 is a server-side request forgery (SSRF) vulnerability in galaxy_ng, the Ansible Galaxy server plugin for Pulp, used in Red Hat Ansible Automation Platform 2. An authenticated user with namespace management permissions can set a namespace avatar URL to arbitrary addresses, including internal network and cloud metadata endpoints. A background worker fetches these URLs without destination checks, allowing attackers to probe internal services and enumerate reachable IPs. The HTTP client lacks an overall timeout, enabling denial of service by pinning workers with slow or unresponsive targets. There is no complete mitigation, but risk can be reduced by restricting permissions and applying network egress filtering.
A flaw was found in the JWT Bearer authorization grant implementation within the keycloak-services component of Red Hat Build of Keycloak. This component handles various OAuth2 and OpenID Connect grant types used for issuing access tokens. The issue occurs because the JWT Bearer grant fails to check if a client requires user consent before issuing a token. This allows an authenticated attacker with valid client credentials and a trusted identity provider assertion to bypass the consent requirement and obtain unauthorized access to a user account at a consent-gated client.
Netty versions prior to 4.1.137.Final and 4.2.17.Final contain a vulnerability in the MqttEncoder component where client identifiers, will topics, usernames, and PUBLISH topic names are not validated before encoding. This allows prohibited null bytes in MQTT UTF-8 string fields, potentially causing routing, access-control, or identity mismatches in downstream brokers. The issue is fixed in versions 4.1.137.Final and 4.2.17.Final.
---
_-= Per source details. Do not edit below this line.=-_
## Source: amazon-inspector (27ba065e8759299d381ed1c7abd5e7721037b4ea969a384a9e70cfb6bb799e17)
Package declares `scripts.preinstall`: `node index.js`, causing index.js to run automatically on `npm install`. The script collects hostname, username, home directory, INIT_CWD, local IPv4, public egress IP (via api.ipify.org, icanhazip.com, ifconfig.me), DNS resolver IP and client subnet (via o-o.myaddr.l.google.com), and the parent project's package.json fields (name, author, repository, homepage). The collected JSON is exfiltrated to the hardcoded callback host `da51rv0hb2uc72tg4gvgdepinjcallbk1.oast.fun` (Interactsh/OAST) via DNS-chunked queries and HTTPS POST to `/poc/<uuid>`. The unscoped name is published at version 999.9.12 to defeat internal resolvers that fall back to the public npm registry, so any build referencing `fund-portfolio` without a private-registry pin will resolve to and execute this payload.
## Source: ossf-package-analysis (ffad2f6c37441c2924e67b1d506d9c26dc9cb2fae325b74a596102ea5ed403bf)
The OpenSSF Package Analysis project identified 'fund-portfolio' @ 999.9.12 (npm) as malicious.
It is considered malicious because:
- The package communicates with a domain associated with malicious activity.
CVE-2026-49244 is a path traversal vulnerability in the SFTPGo open source file transfer solution. Versions from 2.2.0 up to but not including 2.7.2 allow unauthenticated users to exploit the public web-client partial ZIP download endpoint for browsable shares. The vulnerability arises because the endpoint validates file entries using a raw byte-prefix comparison instead of a directory-boundary-aware check. This flaw allows attackers to include files outside the intended shared directory in the ZIP download, potentially disclosing sensitive file contents. The issue is fixed in version 2.7.2.
Splunk Enterprise versions below 10.4.1, 10.2.5, 10.0.9, and 9.4.14 contain a vulnerability where an unauthenticated user able to access the management port can inject a malicious Search Processing Language (SPL) pipeline. This pipeline executes when an administrator opens the Add Data forwarder workflow, potentially compromising data confidentiality, system integrity, and availability. The issue arises from improper neutralization of special characters in Deployment Server client identifiers used in dispatched searches. Exploitation requires the attacker to register a crafted Deployment Server client identity and an administrator to trigger the workflow.