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.
Read more DatabaseIn 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.
Read more DatabaseIn 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.
Read more Application DevelopmentIn 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.
Read more Data AnalyticsIn Budibase versions prior to 3.39.0 a high severity vulnerability CVE-2026-48152 was detected. This vulnerability allows an authenticated attacker with basic permissions to exfiltrate stored REST datasource authentication credentials. This occurs because the single-datasource routes are improperly guarded by generic table permissions rather than specific builder/admin roles. A Basic user can update a REST datasource’s base URL (config.url) while maintaining the original redacted authentication secrets. When a saved query is subsequently executed, the application sends the stored authorization headers to the newly set, attacker-controlled URL, leading to credential disclosure. To address this issue, users should upgrade Budibase to version 3.39.0. For more details, visit https://nvd.nist.gov/vuln/detail/CVE-2026-48152.
Read more Application DevelopmentIn 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.
Read more Developer Tools