Our news and updates

In Appsmith versions versions prior to 2.1 a medium severity vulnerability CVE-2026-7299 was detected. This vulnerability allows an authenticated user with Developer privileges to inject a persistent Cross-Site Scripting (XSS) payload, leading to arbitrary code execution in the sessions of other workspace members. This occurs because the SQL query editor’s autocomplete functionality fails to sanitize database object names before rendering them in innerHTML. An attacker can exploit this by creating malicious table or column names, which then trigger the payload when other users interact with the same datasource. To address this issue, users should upgrade Appsmith to version 2.1 and later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-7299.

In Portainer Community Edition versions 2.33.0 to before 2.33.8, 2.39.2, and 2.41.0 a high severity vulnerability CVE-2026-44848 was detected. This vulnerability allows a standard non-admin user with endpoint access to potentially achieve Remote Code Execution (RCE) on the host system. This occurs because the Docker plugin management endpoints (/plugins/*) lack proper authorization handler registration. As a result, standard users can bypass Resource Control access restrictions and directly call privileged operations, such as installing and enabling plugins, against the underlying Docker daemon. To address this issue, users should upgrade Portainer Community Edition to versions 2.33.8, 2.39.2, or 2.41.0. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-44848.

In MLflow versions prior to 3.11.0 a critical severity vulnerability CVE-2026-4035 was detected. This vulnerability allows an attacker to exfiltrate sensitive server-side environment credentials, such as AWS access keys, to an attacker-controlled endpoint. This occurs because the api_key field in AI Gateway secrets incorrectly resolves environment variable references (e.g., $ENV_VAR) against the MLflow server’s environment during runtime. The resolved secrets are then sent in provider authentication headers to a configured upstream api_base. This can be exploited by unauthenticated users in default deployments or low-privileged users in basic-auth deployments, potentially leading to artifact poisoning and cross-boundary code execution. To address this issue, users should upgrade MLflow to version 3.11.0. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-4035.

In Django versions 6.0 before 6.0.6 and 5.2 before 5.2.15 a low severity vulnerability CVE-2026-6873 was detected. This vulnerability allows a remote attacker to use a signed cookie in a context different from the one where it was originally signed. This occurs because the django.http.HttpRequest.get_signed_cookie function uses a non-injective salt derivation method that simply concatenates the cookie name and the salt argument. An attacker can exploit this by utilizing distinct (name, salt) pairs that produce the exact same string concatenation. To address this issue, users should upgrade Django to versions 6.0.6 or 5.2.15. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-6873.

In Budibase versions prior to 3.38.1 a high severity vulnerability CVE-2026-45715 was detected. This vulnerability allows an authenticated attacker with Builder permissions to perform a Server-Side Request Forgery (SSRF) attack, potentially accessing internal services such as cloud metadata or internal databases. This occurs because the REST datasource integration follows HTTP redirects without re-checking the new destination against the IP blacklist, enabling an attacker to bypass restrictions by redirecting the request through an attacker-controlled server. To address this issue, users should upgrade Budibase to version 3.38.1. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-45715.

In Grafana versions 6.7.0 through 11.6.13, 12.0.0 through 12.2.7, 12.3.0 through 12.3.5, 12.4.0 through 12.4.2, 13.0.0 a medium severity vulnerability CVE-2026-28383 was detected. This vulnerability allows an authenticated attacker to cause a Denial of Service (DoS) by triggering an out-of-memory condition. This occurs because the Grafana plugin resources endpoint reads the entire request body into memory without size limits, leading to unbounded memory allocation. To address this issue, users should upgrade Grafana to version 11.6.14+security-04, 12.2.8+security-04, 12.3.6+security-04, 12.4.3+security-02, 13.0.1+security-01. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-283833.

In Kibana versions up to and including 8.19.15, prior to 9.3.3, 9.2.8, up to and including 9.4.1 a high severity vulnerability CVE-2026-42398 was detected. This vulnerability allows an authenticated user with connector management privileges to perform a Server-Side Request Forgery (SSRF) attack and bypass operator-configured connection allowlists. This occurs because an attacker can configure a Webhook connector with a specially crafted target, forcing Kibana to issue outbound requests to destinations that were intended to be blocked by egress restriction controls. To address this issue, users should upgrade Kibana to version 9.2.8 or 9.3.2. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-42398.

In SQLite versions through 3.29.0 a medium severity vulnerability CVE-2019-16168 was detected. This vulnerability allows an attacker to cause a Denial of Service (DoS) by crashing a browser or any other application using the database. This occurs due to a severe division by zero error in the query planner (specifically within the whereLoopAddBtreeIndex function in sqlite3.c), which is triggered by missing validation of the sqlite_stat1 sz field. To address this issue, users should upgrade SQLite to version 3.29.0 and later. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2019-16168.

In Kubernetes (all versions) a medium severity vulnerability CVE-2020-8554 was detected. This vulnerability allows an attacker to intercept traffic intended for specific IP addresses, resulting in a Man-in-the-Middle (MitM) attack. This occurs because the Kubernetes API server allows users who can create a ClusterIP service to freely set the spec.externalIPs field. Additionally, an attacker with privileged access to patch the status of a LoadBalancer service can set the status.loadBalancer.ingress.ip field to achieve a similar effect. There’s no fix available for this issue at the moment. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2020-8554.