A cross-site scripting (XSS) vulnerability in GitLab CE/EE versions from 16.1.0 before 18.9.6, 18.10.0 before 18.10.4, and 18.11.0 before 18.11.1 could allow an unauthenticated user to access tokens in the Storybook development environment due to improper input validation. This issue has been remediated in the specified fixed versions.
Rclone versions from 1.48.0 up to but not including 1.73.5 contain a critical vulnerability in the Remote Control (RC) endpoint operations/fsinfo. This endpoint is exposed without authentication and accepts attacker-controlled input that allows instantiation of malicious backends. Specifically, the WebDAV backend executes a command during initialization, enabling unauthenticated local command execution on deployments where the RC server is running without authentication. The issue is patched in version 1.73.5.
Rclone versions from 1.45.0 up to but not including 1.73.5 contain a critical vulnerability in the Remote Control (RC) server. The exposed RC endpoint 'options/set' lacks authentication enforcement, allowing unauthenticated attackers to disable authorization for other RC methods. This enables unauthorized access to sensitive administrative functions and potentially command execution. The vulnerability is patched in version 1.73.5.
The golang packages provide the Go programming language compiler.
Security Fix(es):
* golang: internal/syscall/unix: Root.Chmod can follow symlinks out of the root (CVE-2026-32282)
* crypto/tls: golang: Go crypto/tls: Denial of Service via multiple TLS 1.3 key update messages (CVE-2026-32283)
* crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building (CVE-2026-32280)
* golang: cmd/compile: no-op interface conversion bypasses overlap checking (CVE-2026-27144)
* cmd/go: golang: Go (golang) and cmd/go: Arbitrary Code Execution via malicious SWIG file names (CVE-2026-27140)
* golang: cmd/compile: possible memory corruption after bound check elimination (CVE-2026-27143)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
The Grafana plugin for Performance Co-Pilot includes datasources for scalable time series from pmseries and Redis, live PCP metrics and bpftrace scripts from pmdabpftrace, as well as several dashboards.
Security Fix(es):
* crypto/x509: Incorrect enforcement of email constraints in crypto/x509 (CVE-2026-27137)
* crypto/x509: golang: Go crypto/x509: Certificate validation bypass due to incorrect DNS constraint application (CVE-2026-33810)
* golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing (CVE-2026-39821)
* mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header (CVE-2026-42504)
* encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal (CVE-2026-33818)
* net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution (CVE-2026-56860)
* net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service (CVE-2026-56853)
* html/template: golang: Go html/template: Cross-Site Scripting via pathological input (CVE-2026-56858)
* crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages (CVE-2026-56862)
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Red Hat OpenShift Service Mesh 3.0.10, which is based on the open source Istio project, addresses a variety of problems in a microservice architecture by creating a centralized point of control in an application.
Fixes/Improvements:
Security Fix(es):
* istio-rhel9-operator: Incorrect parsing of IPv6 host literals in net/url (CVE-2026-25679)
* istio-cni-rhel9: Incorrect parsing of IPv6 host literals in net/url (CVE-2026-25679)
* istio-pilot-rhel9: Incorrect parsing of IPv6 host literals in net/url (CVE-2026-25679)
* istio-proxyv2-rhel9: Incorrect parsing of IPv6 host literals in net/url (CVE-2026-25679)
* istio-proxyv2-rhel9: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation (CVE-2026-33186)
* istio-proxyv2-rhel9: BuildKit: Arbitrary file write and code execution via untrusted frontend (CVE-2026-33747)
* istio-proxyv2-rhel9: BuildKit: Unauthorized file access via Git URL fragment subdir components (CVE-2026-33748)
The method "sock_recvfrom_into()" of "asyncio.ProacterEventLoop" (Windows only) was missing a boundary check for the data buffer when using nbytes parameter. This allowed for an out-of-bounds buffer write if data was larger than the buffer size. Non-Windows platforms are not affected.
Composer, a PHP dependency manager, contains a command injection vulnerability in versions 1.0 through 2.2.26 and 2.3 through 2.9.5. The vulnerability exists in the Perforce::syncCodeBase() and Perforce::generateP4Command() methods, which improperly escape user-supplied parameters, allowing arbitrary command injection. This can be exploited via malicious package metadata from compromised or malicious Composer repositories when installing or updating dependencies from source. The issue is fixed in Composer 2.2.27 and 2.9.6. Workarounds include avoiding source installs by using --prefer-dist or trusted repositories.
Composer, a PHP dependency manager, contains a command injection vulnerability in versions 1.0 through 2.2.26 and 2.3 through 2.9.5. The vulnerability exists in the Perforce::generateP4Command() method, which improperly escapes user-supplied Perforce connection parameters. An attacker can exploit this by crafting a malicious composer.json file declaring a Perforce VCS repository, leading to arbitrary command execution with the privileges of the user running Composer. This issue cannot be exploited through composer.json files of dependencies, only from the root composer.json or composer config directory. The vulnerability is fixed in versions 2.2.27 and 2.9.6.
Valkey is a distributed key-value database. Prior to versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12, a malicious actor with access to the Valkey clusterbus port can send an invalid packet that may cause an out bound read, which might result in the system crashing. The Valkey clusterbus packet processing code does not validate that a clusterbus ping extension packet is located within buffer of the clusterbus packet before attempting to read it. Versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12 fix the issue. As an additional mitigation, don't expose the cluster bus connection directly to end users, and protect the connection with its own network ACLs.
CVE-2026-5052 is a Server-Side Request Forgery (SSRF) vulnerability in HashiCorp Vault's PKI engine ACME validation. The vulnerability allows local network targets to be requested during http-01 and tls-alpn-01 challenge issuance, potentially leading to information disclosure. This issue affects Vault version 1.15.0 and was fixed in Vault Community Edition 2.0.0 and Vault Enterprise versions 2.0.0, 1.21.
If a Vault auth mount is configured to pass through the "Authorization" header, and the "Authorization" header is used to authenticate to Vault, Vault forwarded the Vault token to the auth plugin backend. Fixed in 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
An authenticated user with access to a kvv2 path through a policy containing a glob may be able to delete secrets they were not authorized to read or write, resulting in denial-of-service. This vulnerability did not allow a malicious user to delete secrets across namespaces, nor read any secret data. Fxed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0, 1.21.5, 1.20.10, and 1.19.16.
Vault is vulnerable to a denial-of-service condition where an unauthenticated attacker can repeatedly initiate or cancel root token generation or rekey operations, occupying the single in-progress operation slot. This prevents legitimate operators from completing these workflows. This vulnerability, CVE-2026-5807, is fixed in Vault Community Edition 2.0.0 and Vault Enterprise 2.0.0.
A command injection vulnerability exists in mlflow/mlflow when serving a model with the option enable_mlserver=True. The model_uri parameter is embedded directly into a shell command executed via bash without proper sanitization, allowing an attacker to execute arbitrary commands if shell metacharacters are included. This can lead to privilege escalation if the service runs with higher privileges and serves models from directories writable by lower-privileged users. The vulnerability affects versions prior to 3.11.1 and is classified as critical.
A command injection vulnerability exists in mlflow versions prior to 3.7.0 in the mlflow/sagemaker/__init__.py file. The flaw allows attackers to execute arbitrary commands by supplying malicious input through the --container parameter of the CLI, due to unsanitized interpolation of user input into shell commands executed via os.system(). This affects environments using MLflow, including development, CI/CD pipelines, and cloud deployments. The vulnerability is rated high severity and a patch is available.
NGINX Open Source and NGINX Plus have a vulnerability in the ngx_mail_smtp_module that might allow an unauthenticated attacker to over-read NGINX SMTP authentication process memory; as a result, the server side may leak arbitrary bytes sent in a request to the authentication server. This issue happens during the NGINX SMTP authentication process and requires the attacker to make preparations against the target system to extract the leaked data. The issue affects NGINX only if (1) it is built with the ngx_mail_smtp_module, (2) the smtp_auth directive is configured with method "none," and (3) the authentication server returns the "Auth-Wait" response header.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
A cross-tenant isolation vulnerability was found in Grafana’s Correlations feature affecting legacy correlation records. Due to a backward compatibility condition allowing org_id = 0 records to be returned across organizations, a user with datasource management privileges could read and permanently delete legacy correlation data belonging to another organization. This issue affects correlations created prior to Grafana 10.2 and is fixed in >=11.6.11, >=12.0.9, >=12.1.6, and >=12.2.4.
Thanks to Gyu-hyeok Lee (g2h) for reporting this vulnerability.
In Grafana's alerting system, users with edit permissions for a contact point, specifically the permissions “alert.notifications:write” or “alert.notifications.receivers:test” that are granted as part of the fixed role "Contact Point Writer", which is part of the basic role Editor - can edit contact points created by other users, modify the endpoint URL to a controlled server. By invoking the test functionality, attackers can capture and extract redacted secure settings, such as authentication credentials for third-party services (e.g., Slack tokens). This leads to unauthorized access and potential compromise of external integrations.