Daily Digest
The single most urgent item is CVE-2019-1068 in Microsoft SQL Server, a remote code execution vulnerability that is actively exploited in the wild and listed in the CISA Known Exploited Vulnerabilities (KEV) catalog with a due date of 2026-08-29. This supersedes all other entries due to confirmed exploitation.
Summary: A remote code execution vulnerability exists in Microsoft SQL Server when it incorrectly handles processing of internal functions. It is exploitable over the network without authentication, allowing an attacker to execute arbitrary code on the affected system. CISA has confirmed active exploitation and set a remediation deadline of 2026-08-29.
Affected Features / Interoperability: Impacts core SQL Server functionality related to internal function processing. Could affect any service or application relying on SQL Server for backend data storage, including reporting services, integration services, and custom applications using SQL Server drivers.
Source:
Actions:
Summary: A flaw in the Data Science Pipelines Operator (DSPO) allows a namespace editor to inject dangerous parameters into the MySQL Data Source Name (DSN) string via the `spec.database.customExtraParams` field. This enables LOCAL INFILE functionality, potentially leading to exfiltration of sensitive files like service account tokens and privilege escalation to cluster-admin.
Affected Features / Interoperability: Impacts MySQL integrations within Kubernetes-based data science environments using the Data Science Pipelines Operator. Could affect dependent applications, pipelines, and services relying on secure database connections and operator-managed credentials.
Source:
Actions:
Summary: A weakness in the MongoDB C++ Driver allows special characters in caller-supplied namespace identifiers to pass without sanitization. Applications that build namespaces from untrusted input may have operations redirected to unintended targets, resulting in unauthorized read/write access across logical tenants.
Affected Features / Interoperability: Affects applications using the MongoDB C++ Driver, particularly those handling multi-tenant architectures or constructing namespaces dynamically. Could lead to cross-tenant data exposure or corruption.
Source:
Actions:
Summary: The MongoDB client library for PHP fails to sanitize special elements in application-supplied namespace identifiers. Applications incorporating untrusted text into these identifiers may have operations redirected to unintended storage locations.
Affected Features / Interoperability: Impacts PHP applications using the MongoDB driver, especially those with dynamic database or collection naming based on user input. Could result in data leakage or unauthorized modifications.
Source:
Actions:
Summary: Improper neutralization of delimiters in connection-URL construction allows connection-option injection in the MongoDB C# Driver. Untrusted text passed into the driver's connection-URL builder can introduce or suppress security-relevant connection settings.
Affected Features / Interoperability: Affects .NET applications using the MongoDB C# Driver, particularly those constructing connection strings from user input. Could lead to insecure connections or bypass of authentication mechanisms.
Source:
Actions:
Summary: The MongoDB Go Driver's `Client.BulkWrite` API may accept a caller-supplied database name containing a reserved separator character without escaping. Applications passing untrusted input as a database name could have writes directed at unintended databases or collections.
Affected Features / Interoperability: Affects Go applications using the MongoDB Go Driver, specifically those utilizing the `Client.BulkWrite` API with dynamic database names. Could result in unintended data writes or cross-database contamination.
Source:
Actions:
Summary: The MongoDB Rust Driver does not neutralize special characters in caller-supplied target identifiers. An actor influencing these identifiers may cause write operations to be applied to unintended targets within the same deployment.
Affected Features / Interoperability: Affects Rust applications using the MongoDB Rust Driver, particularly those constructing target identifiers from external input. Could lead to unauthorized data modifications.
Source:
Actions:
Summary: A NoSQL/expression injection weakness exists in the LINQ-to-aggregation query translation layer of the MongoDB C# Driver. Special elements in application-supplied values may be interpreted as query logic rather than data, altering query results.
Affected Features / Interoperability: Affects .NET applications using LINQ queries with the MongoDB C# Driver. Could result in unintended data exposure or manipulation of query outcomes.
Source:
Actions:
Summary: An unauthenticated client reaching a MongoDB Connector for BI deployment configured with Kerberos authentication may cause `mongosqld` to terminate due to a specific GSSAPI error-handling condition, interrupting BI Connector availability until restart.
Affected Features / Interoperability: Impacts MongoDB Connector for BI deployments using Kerberos authentication. Could lead to denial of service for BI tools and analytics platforms relying on the connector.
Source:
Actions:
Summary: Sensitive key-management credential material supplied by the application is reproduced verbatim in the MongoDB C# Driver's diagnostic representation of client settings, instead of being masked. Parties with access to logs or memory dumps may recover plaintext credentials.
Affected Features / Interoperability: Affects applications using client-side field-level encryption with the MongoDB C# Driver. Could expose encryption keys and compromise protected data.
Source:
Actions:
Summary: A weakness in the MongoDB C Driver allows special elements in caller-supplied database and collection name components to pass without sanitization. Applications incorporating untrusted input into these names can have operations directed at unintended resources.
Affected Features / Interoperability: Affects applications using the MongoDB C Driver with dynamic database or collection naming. Could result in unauthorized data access or modification.
Source:
Actions:
Summary: A document-replacement code path in the MongoDB C# Driver omits element-name/shape validation, allowing untrusted input to be interpreted as update logic rather than data. This affects applications passing loosely-typed input as replacement values.
Affected Features / Interoperability: Affects .NET applications using the MongoDB C# Driver for document replacement operations. Could lead to unintended data modifications or injection attacks.
Source:
Actions:
The most urgent item this cycle is CVE-2026-66384 in Docker (JFrog Artifactory), a CISA KEV-confirmed actively exploited vulnerability with an agency-mandated remediation deadline of September 10, 2026. Despite a moderate CVSS score of 5.3, confirmed in-the-wild exploitation and regulatory pressure make this higher priority than the Kubernetes CVEs (which carry higher CVSS scores but lack confirmed active exploitation). Kubernetes administrators should note that the 1.37 release continues legacy cleanup (kube-dns, IPVS, cgroup v1 deprecation) and GKE security hardening guidance has surfaced in industry publications.
Summary: An authenticated user can write data outside the intended Docker cache path under specific remote-repository conditions. This is a CISA KEV entry with a due date of 2026-09-10; the agency has directed affected organizations to apply mitigations per BOD 26-04 and conduct forensics triage.
Affected Features / Interoperability: JFrog Artifactory's Docker cache and remote repository handling. Downstream impact to container image integrity and potential artifact poisoning in CI/CD pipelines pulling from affected Artifactory instances. Specific Artifactory version details are not disclosed in the advisory.
Source: JFrog Security Advisories | CISA KEV Catalog | OpenAI/Hugging Face Incident Technical Report
Actions:
Summary: The MaaS API contains a flaw allowing any pod to forge `X-MaaS-Username` and `X-MaaS-Group` HTTP headers trusted verbatim by the Kuadrant AuthPolicy gateway. This bypasses first-party authentication, enabling unauthorized minting of ServiceAccount tokens in other tenants' namespaces, API key revocation, and exfiltration of sensitive model access configuration.
Affected Features / Interoperability: Kuadrant AuthPolicy enforcement, multi-tenant MaaS deployments, and any workload relying on AuthPolicy-gated API access. Kubernetes RBAC, service account authentication, and cross-namespace trust relationships are directly impacted.
Source: Red Hat Errata RHSA-2026:53262 | Red Hat Errata RHSA-2026:60520 | Red Hat CVE Page | Bugzilla #2496373
Actions:
Summary: The `guardrails-detectors` component is vulnerable to blind Server-Side Request Forgery (SSRF) via crafted XML Schema Definition (XSD) strings. A remote attacker can exploit this to access cloud metadata services (IMDS), the Kubernetes API, internal MinIO instances, and read local files including service account tokens and pod secrets.
Affected Features / Interoperability: The guardrails-detectors XSD parsing feature, cloud metadata endpoints (AWS IMDS, GCP IMDS, Azure IMDS), Kubernetes API server access from within pods, and MinIO-based object storage integrations.
Source: Red Hat Errata RHSA-2026:60520 | Red Hat CVE Page | Bugzilla #2498941
Actions:
Summary: Apache CloudStack's Kubernetes Service (CKS) plugin has an Improper Access Control flaw allowing cross-tenant manipulation of Kubernetes clusters during node addition and removal. The raw advisory does not specify the exact exploitation primitives.
Affected Features / Interoperability: Apache CloudStack CKS plugin (versions 4.21.0.0 through 4.22.1.0), multi-tenant Kubernetes cluster lifecycle management, node provisioning and deprovisioning workflows.
Source: Apache CloudStack Mailing List
Actions:
Summary: The Application Subscription controller in Red Hat Advanced Cluster Management for Kubernetes (ACM) fetches and applies Helm chart contents with elevated authority without verifying that the subscription creator holds `open-cluster-management:subscription-admin`. This allows a user with namespace-scoped "edit" privileges to include cluster-scoped resources (e.g., ClusterRoleBinding granting `cluster-admin`) in the chart, achieving full cluster privilege escalation.
Affected Features / Interoperability: ACM hub's application subscription lifecycle, Helm repository integrations, cluster-wide RBAC resources, and multi-cluster workload deployment.
Source: Red Hat Errata RHSA-2026:60386 | RHSA-2026:60387 | RHSA-2026:60388 | RHSA-2026:60389 | RHSA-2026:60390
Actions:
Summary: In Red Hat OpenShift AI (RHOAI), incorrect network binding allows a malicious actor within the cluster to bypass authentication and impersonate any user by providing an arbitrary access token. This grants unauthorized access to the Kubernetes API, potentially leading to arbitrary code execution, privilege escalation, or information disclosure.
Affected Features / Interoperability: RHOAI's web console (odh-dashboard), Kubernetes API authentication from within the cluster, user impersonation workflows, and AI/ML workload authentication.
Source: Red Hat Errata RHSA-2026:53261 | RHSA-2026:53262 | RHSA-2026:53263 | RHSA-2026:60520 | Red Hat CVE Page
Actions:
Summary: The RHOAI overlay for the training operator incorrectly aggregates `TrainJobs` management permissions into the native Kubernetes `edit` ClusterRole. Any user with `edit` permissions in a namespace can create, modify, and delete `TrainJobs`. When combined with a separate vulnerability (TRN-01) permitting arbitrary pod configurations, namespace editors can escalate to arbitrary code execution.
Affected Features / Interoperability: RHOAI training operator, TrainJobs CRD, Kubernetes `edit` ClusterRole, and AI/ML training workload lifecycle management.
Source: Red Hat Errata RHSA-2026:53262 | RHSA-2026:53263 | RHSA-2026:60520 | Red Hat CVE Page | Bugzilla #2511187
Actions:
Summary: The RHOAI training-operator allows any user with standard `edit` or `admin` roles to escalate privileges through training jobs. Attackers can impersonate service accounts, access the host filesystem, and potentially execute arbitrary code. This stems from training job permissions being aggregated onto native `edit` and `admin` ClusterRoles alongside unrestricted PodTemplateSpec passthrough.
Affected Features / Interoperability: RHOAI training-operator, PodTemplateSpec handling, service account impersonation, host filesystem access from pods, and Kubernetes `admin`/`edit` ClusterRoles.
Source: Red Hat Errata RHSA-2026:53261 | RHSA-2026:53262 | RHSA-2026:53263 | RHSA-2026:60520 | Red Hat CVE Page
Actions:
Summary: The governance-policy-addon-controller in Red Hat ACM allows a user with permissions to annotate the `ManagedClusterAddOn` resource to override the governance-policy container image. This enables running a controlled image with cluster-admin privileges on the managed cluster, leading to arbitrary code execution and privilege escalation.
Affected Features / Interopolability: ACM governance-policy-addon-controller, ManagedClusterAddOn lifecycle, container image integrity on managed clusters, and policy enforcement across cluster fleets.
Source: Red Hat Errata RHSA-2026:60386 | RHSA-2026:60387 | RHSA-2026:60388 | RHSA-2026:60389 | RHSA-2026:60390
Actions:
Summary: The Data Science Pipelines Operator (DSPO) ClusterRole includes excessive privileges beyond its operational requirements—such as executing commands within pods and managing cluster-wide roles. If the DSPO pod is compromised, an attacker could leverage these privileges for full cluster administrative control.
Affected Features / Interoperability: DSPO operator permissions, pod execution capabilities, cluster-scoped role management, and data science pipeline orchestration.
Source: Red Hat Errata RHSA-2026:53261 | RHSA-2026:53262 | RHSA-2026:53263 | RHSA-2026:60520 | Red Hat CVE Page
Actions:
Summary: Grafana Alloy's `prometheus.operator.servicemonitors` component allows users with ServiceMonitor write access to specify an arbitrary local file via `bearerTokenFile`. Alloy reads the file and sends its contents as a bearer token to an attacker-controlled scrape endpoint, potentially disclosing Alloy's projected Kubernetes service account token and granting the attacker Alloy's Kubernetes permissions.
Affected Features / Interoperability: Grafana Alloy prometheus operator, ServiceMonitor resources, Kubernetes service account tokens, and metrics scraping endpoint configuration.
Source: Grafana Security Advisory
Actions: