Daily Digest
The most urgent item is the critical SQL injection flaw in MariaDB/MySQL (CVE-2026-44172, CVSS 9.1), which allows unauthenticated attackers to bypass escaping controls and execute arbitrary SQL when using the big5 character set, posing an immediate risk to data confidentiality and integrity.
Summary: MariaDB/MySQL versions 3.3.18 and 3.4.8 fail to properly escape user input when the big5 character set is used with `mysql_real_escape_string()`, enabling SQL injection via the text protocol. An attacker who can send crafted queries to the database server can exploit this without authentication.
Affected Features / Interoperability: The MySQL/MariaDB server’s text protocol handling and escaping logic are impacted; successful exploitation could lead to arbitrary SQL execution, compromising data confidentiality, integrity, and availability, and affecting any application or service that relies on the database.
Source:
Actions:
Summary: Anyquery versions prior to 0.4.5 expose SQLite virtual table modules (`json_reader`, `log_reader`) through an unauthenticated MySQL‑compatible port, allowing remote attackers to supply arbitrary URLs (including loopback or cloud‑metadata endpoints) and read internal resources.
Affected Features / Interoperability: The Anyquery server’s MySQL‑compatible listener and its virtual table modules are vulnerable; exploitation can lead to SSRF, internal API access, and potential credential leakage, affecting any downstream services that rely on Anyquery for data federation.
Source:
Actions:
Summary: Vendure versions before 3.6.5 inadequately sanitize regular‑expression input in the public Shop GraphQL API, permitting unauthenticated attackers to supply catastrophic backtracking patterns that cause denial of service by blocking the Node.js event loop.
Affected Features / Interoperability: The Vendure Shop GraphQL API’s `StringOperators.regex` handling is affected; repeated malicious requests can render the storefront and admin API unavailable, impacting any frontend or integration that depends on Vendure’s GraphQL endpoint.
Source:
Actions:
Summary: During RHEL 9→10 upgrades, the `leapp-upgrade-el9toel10` scan_mysql actor runs `mysqld --validate-config` as root, allowing a compromised mysql OS user to plant a malicious `mysqld-auto.cnf` and shared object that gets loaded with root privileges when an administrator subsequently runs the Leapp upgrade workflow.
Affected Features / Interoperability: The Leapp upgrade process and MySQL’s persisted configuration (`mysqld-auto.cnf`) are impacted; exploitation could lead to full root compromise on the host during OS upgrades, affecting system integrity and any services running on the upgraded machine.
Source:
Actions:
Summary: MikroORM versions prior to 6.6.16 and 7.1.7 fail to validate the `direction` value of an `orderBy` clause, allowing attacker‑controlled input to be injected directly into an `ORDER BY` statement and enabling blind or boolean‑based SQL extraction.
Affected Features / Interoperability: MikroORM’s SQL layer order‑by handling is vulnerable across multiple drivers (MySQL, PostgreSQL, SQLite, MSSQL, Oracle, etc.); exploitation could lead to data exfiltration or inference, affecting any application that uses MikroORM for data access.
Source:
Actions:
Summary: Craft CMS versions 5.0.0 through 5.10.12 treat a database connection failure as an indication that the system is not installed, leaving the installer/validate‑site endpoint accessible; an attacker with a valid guest session can then extract environment variables and secrets via `${NAME}` expansion.
Affected Features / Interoperability: The Craft CMS installer validation routine is affected when the DB is unavailable; exploitation could lead to disclosure of application secrets, database credentials, and other configuration data, impacting any integrated services that rely on those secrets.
Source:
Actions:
Summary: Marten versions 7.0.0 through 9.13.0 interpolate attacker‑controlled strings into single‑quoted SQL literals without proper escaping in several LINQ and tenant‑management code paths, enabling SQL injection that can bypass authentication and exfiltrate data.
Affected Features / Interoperability: Marten’s LINQ provider (`Where` filters, `SelectParser`, tenant‑partition handling) is vulnerable; successful exploitation could allow unauthorized data access or modification, affecting any .NET application that relies on Marten for PostgreSQL interaction.
Source:
Actions:
Summary: Magistrala versions before 1.0.0 contain a SQL injection flaw in the `timescale-reader` and `postgres-reader` HTTP APIs where a `format` query parameter is directly interpolated into the `FROM` clause, letting authenticated users execute arbitrary SQL with superuser privileges.
Affected Features / Interoperability: Magistrala’s reader APIs are impacted; exploitation could lead to reading password hashes, arbitrary file read/write, and code execution as the `postgres` OS user, affecting any service that depends on Magistrala for time‑series or PostgreSQL data access.
Source:
Actions:
Summary: Vendure versions prior to 3.6.5 allow unauthenticated attackers to supply catastrophic backtracking regular expressions via the public Shop GraphQL API’s `StringOperators.regex` field, causing denial of service by blocking the Node.js event loop.
Affected Features / Interoperability: Vendure’s Shop GraphQL API is affected; repeated malicious requests can render the storefront and admin API unavailable, impacting any frontend or integration that relies on Vendure’s GraphQL endpoint.
Source:
Actions:
Summary: MikroORM versions before 6.6.16 and 7.1.7 insufficiently validate the `direction` component of an `orderBy` clause, permitting attacker‑controlled SQL injection that can lead to blind or boolean data extraction.
Affected Features / Interoperability: MikroORM’s SQL layer order‑by handling is vulnerable across multiple drivers (including PostgreSQL); exploitation could allow data exfiltration or inference, affecting any application that uses MikroORM for data access.
Source:
Actions:
Summary: Oracle Database Server versions 23.4.0‑23.26.3 contain a vulnerability in the RDBMS component that allows a low‑privileged attacker with the `CREATE TABLE` privilege and network access via Oracle Net to take over the database.
Affected Features / Interoperability: The RDBMS component is impacted; successful exploitation could lead to full compromise of the database, affecting all dependent applications, replication, backup, and any integrated services.
Source:
Actions:
Summary: Oracle Database Server versions 19.3‑19.32, 21.3‑21.23, and 23.4.0‑23.26.3 are vulnerable in the RDBMS component; a low‑privileged attacker with the `EXECUTE ON DBMS_REDEFINITION` privilege and network access via Oracle Net can compromise the database.
Affected Features / Interoperability: The RDBMS component is affected; exploitation could lead to full database takeover, impacting data confidentiality, integrity, and availability for all reliant systems.
Source:
Actions:
Summary: Oracle Database Server versions 19.3‑19.32, 21.3‑21.23, and 23.4.0‑23.26.3 contain a flaw in the RDBMS component allowing a low‑privileged attacker with the `CREATE DB LINK` privilege and network access via Oracle Net to take over the database.
Affected Features / Interoperability: The RDBMS component is impacted; successful exploitation could result in complete database compromise, affecting all linked services, replication, and downstream integrations.
Source:
Actions:
Summary: Oracle Database Server versions 19.3‑19.32, 21.3‑21.23, and 23.4.0‑23.26.3 are vulnerable in the Oracle Text component; a low‑privileged attacker with the `CREATE INDEX` privilege and network access via Oracle Net can compromise Oracle Text, with potential scope changes affecting additional products.
Affected Features / Interoperability: Oracle Text is affected; exploitation could lead to takeover of the Oracle Text component,
The most urgent item this cycle is CVE-2026-85596 (Traefik Kubernetes Ingress NGINX provider, CVSS 9.8 CRITICAL), an authentication bypass that causes Traefik to fall back to the entry point's default TLS configuration — which does not request a client certificate — when two Ingress objects share the same host, CA secret, and client-authentication mode. This directly undermines mTLS client-certificate enforcement on Kubernetes ingress routes, making routes configured with `nginx.ingress.kubernetes.io/auth-tls-verify-client: "on"` reachable without a client certificate. In a healthcare environment running mTLS-based service mesh or ingress, this is the highest-priority remediation target.
Summary: Apache Airflow FAB provider versions 3.7.3 through 3.8.0 do not validate the issuer or audience of Azure AD `id_token`s during OAuth login. Because signing keys are fetched from Microsoft's multi-tenant JWKS endpoint, an `id_token` minted in any Azure tenant — including one an attacker creates — passes signature verification, and username and role assignments are then read from that attacker-controlled token. Anyone able to register an Azure tenant can authenticate to the Airflow UI with no prior access to the deployment. The fix for CVE-2026-59243 was incomplete; operators who already applied that fix are still affected and must upgrade again.
Affected Features / Interoperability: The Apache Airflow FAB auth manager when configured with Azure AD as an OAuth provider. Downstream impacts include unauthorized access to the Airflow UI, potential privilege escalation via role assignments read from the attacker-controlled token, and compromise of any workflow or DAG accessible through the authenticated session. Database replication, client drivers, and extensions are not directly mentioned in the advisory.
Source:
Actions:
---
Summary: The Azure Key Vault secrets backend in Apache Airflow's Microsoft Azure provider resolves a team-scoped Connection or Variable id through the team-agnostic lookup when the team-scoped lookup misses. In multi-team mode, a caller in one team can resolve a secret belonging to another team by supplying an id that spells out that team's namespace, obtaining its credentials in full. No unusual configuration is required beyond enabling multi-team mode and using this backend.
Affected Features / Interoperability: Apache Airflow's Microsoft Azure provider secrets backend in multi-team mode. Downstream impacts include cross-team credential leakage, potential access to Key Vault secrets belonging to other teams, and compromise of any workflow or connection configured with those credentials. Database replication and client drivers are not directly mentioned.
Source:
Actions:
---
Summary: Bucket squatting in Google Cloud Gemini Enterprise Agent Platform SDK for Python versions prior to 1.166.1 allows an attacker to achieve Remote Code Execution (RCE) and tenant-project token theft. The CVSS score and severity are not provided in the source data.
Affected Features / Interoperability: Google Cloud Gemini Enterprise Agent Platform SDK for Python. Downstream impacts include potential RCE on the deploying host and theft of tenant-project tokens, which could lead to further cloud resource compromise. Specific affected features beyond the SDK itself are not detailed in the advisory.
Source:
Actions:
---
Summary: Traefik versions from v3.7.1 fail to enforce crossProviderNamespaces restrictions on the `traefik.ingress.kubernetes.io/service.middlewares` Service annotation in the Kubernetes Ingress provider. A namespace-limited tenant excluded from the allowlist can attach an operator-owned middleware to its Service, and if that middleware injects backend credentials, those credentials can be recovered at a controlled backend. The fixed version is not explicitly stated in the advisory data.
Affected Features / Interoperability: Traefik Kubernetes Ingress provider's service middleware annotation handling. Downstream impacts include cross-namespace middleware injection, potential credential leakage to attacker-controlled backends, and compromise of traffic routing for affected Ingress resources. Database replication, client drivers, and extensions are not directly mentioned.
Source:
Actions:
---
Summary: Traefik versions >= v3.7.0 and <= v3.7.10 contain an authentication bypass in the Kubernetes Ingress NGINX provider. The TLS option generated for an Ingress carrying the `nginx.ingress.kubernetes.io/auth-tls-secret` annotation was named after the Ingress namespace and name. Two Ingress objects sharing the same host, the same client CA secret, and the same client-authentication mode produced two distinct TLS option names for that host. Traefik treats this as a TLS options conflict and falls back to the entry point's default TLS configuration, which does not request a client certificate, so a route configured with `nginx.ingress.kubernetes.io/auth-tls-verify-client: "on"` becomes reachable without a client certificate. Only the v3.7 line is affected; fixed in v3.7.11.
Affected Features / Interoperability: Traefik v3.7.x Kubernetes Ingress NGINX provider TLS option generation and client certificate authentication. Downstream impacts include complete bypass of mTLS client-certificate verification on affected routes, allowing unauthenticated access to services that require client certificates. This is particularly critical for healthcare environments relying on mTLS for service-to-service or external-to-internal authentication. Database drivers and extensions are not directly mentioned.
Source:
Actions:
---
Summary: Envoy Gateway prior to 1.7.4 and 1.8.1, the `to_absolute_normalized_path` function in `internal/gatewayapi/luavalidator/security.lua` does not collapse redundant separators before `is_critical_path` evaluates Lua submitted through `EnvoyExtensionPolicy` during default Strict validation. Linux resolves a double-slash absolute path as the corresponding single-slash path, but the validator does not match the redundant-separator form, allowing submitted Lua to read arbitrary files from the gateway controller pod. Exposed files can include Kubernetes service-account tokens, TLS certificates, and process environment data, and the disclosed credentials can provide access to sensitive Kubernetes API Server or Gateway xDS server information. Fixed in versions 1.7.4 and 1.8.1.
Affected Features / Interoperability: Envoy Gateway's Lua validator path normalization when processing `EnvoyExtensionPolicy` resources. Downstream impacts include arbitrary file read from the gateway controller pod, potential disclosure of service-account tokens and TLS certificates, and compromise of Kubernetes API Server or Gateway xDS server access. Database replication, client drivers, and extensions are not directly mentioned.
Source:
Actions:
---
Summary: Traefik from 3.0.0 until 3.6.25 and 3.7.10, the Kubernetes Gateway API provider builds HTTPRoute, GRPCRoute, TCPRoute, and TLSRoute router and service identities by hyphen-concatenating namespace, route name,