Updated daily
The most urgent formal issue is CVE-2026-113709 in Argo CD (CVSS 9.9): a malicious GitOps repository can trigger command execution in the repository server when Helm support is enabled for Kustomize builds. No supplied entry is confirmed as CISA KEV-exploited, so urgency is based on the critical CVSS score, network-exposed repository configuration, and potential credential theft and code execution. Other priorities include the Azure Kubernetes Service authorization flaw, three independently exploitable Traefik ingress authentication bypasses, and a Trigger.dev deployment flaw that permits unauthenticated account takeover and access to backing data stores.
Summary: Incorrect authorization in Microsoft Azure Kubernetes Service lets an authorized attacker elevate privileges over the network. The issue requires an attacker who already has some authorized access to the affected AKS environment; the supplied data does not provide a CISA KEV status or remediation due date.
Affected Features / Interoperability: Microsoft Azure Kubernetes Service authorization and privilege boundaries are affected. Successful exploitation could compromise cluster workloads or other resources available to the elevated identity; the raw data does not identify specific affected API versions, add-ons, or Kubernetes configurations.
Source: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50516
Actions:
Summary: Argo CD versions 2.1.0 through 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2 contain a Helm plugin-loading vulnerability when the operator enables `--enable-helm` for Kustomize builds. A repository-controlled `helmGlobals.configHome` can cause a downloader plugin to be loaded and executed inside `argocd-repo-server`, allowing malicious repository content to expose credentials and execute commands as that service account.
Affected Features / Interoperability: Argo CD's Kustomize/Helm integration, Helm configuration and data directories, and repository-server plugin execution are affected. Repository credentials and other secrets accessible to the repository-server service account may be exposed; the supplied description was truncated before identifying all possible downstream impact.
Source:
Actions:
Summary: Incorrect authorization in Microsoft Azure Kubernetes Service allows an authorized attacker to elevate privileges over the network. The issue requires an attacker who already has some authorized access; no CISA KEV status or remediation due date is supplied.
Affected Features / Interoperability: AKS authorization and privilege boundaries are affected. Successful exploitation could compromise workloads or resources accessible to the elevated identity; specific API versions and add-ons are not identified in the raw data.
Source: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50516
Actions:
Summary: Traefik 3.7.13 before 3.7.14 fails to apply access-control annotations to the HTTP router generated for SSL-passthrough ingresses on non-TLS entry points. An unauthenticated attacker who can reach the HTTP entry point and provide the Ingress host can bypass `auth-type`, `auth-url`, or source-range protections, with the access not logged.
Affected Features / Interoperability: The Traefik Kubernetes Ingress NGINX provider and SSL-passthrough ingress routing are affected. Authentication and source-whitelist enforcement for protected backends can fail, exposing those backends to unauthorized requests.
Source:
Actions:
Summary: Traefik versions 3.7.0 through 3.7.13 can merge client certificate authorities when authentication TLS secret names collide after dot-to-dash normalization. A remote attacker holding a certificate issued by another host's CA may access a host that requires its own client CA, while legitimate clients are denied.
Affected Features / Interoperability: The Traefik Kubernetes Ingress NGINX provider's `auth-tls-secret` handling and client-certificate authentication are affected. Mutual-TLS isolation between hosts may fail, and legitimate client access may be disrupted.
Source:
Actions:
Summary: Traefik versions 3.7.0 through 3.7.13 may forward client-supplied `Ssl-Client-*` headers on the plaintext HTTP router. When SSL redirect is disabled and certificate details are forwarded upstream, an unauthenticated attacker can spoof an mTLS identity by supplying headers such as `Ssl-Client-Verify: SUCCESS`.
Affected Features / Interoperability: The Traefik Kubernetes Ingress NGINX provider, plaintext HTTP routing, and forwarding of `Ssl-Client-*` headers are affected. Upstream applications that trust those headers for client-certificate identity or authorization may admit unauthenticated attackers.
Source:
Actions:
Summary: Ansible Operator Plugins process attacker-controlled custom resource values through Jinja2 without adequate sanitization. A low-privileged Kubernetes user can inject template expressions that execute inside an operator pod, potentially obtaining the operator service account's cluster-wide permissions.
Affected Features / Interoperability: Ansible Operator Plugins, custom-resource value rendering, and operator-pod execution are affected. An exploited operator may gain access to cluster resources permitted to its service account, potentially enabling broader privilege escalation.
Source:
Actions:
Summary: A tenant permitted to create a StreamsHub Console custom resource can point `spec.kafkaClusters[].credentials.kafkaUser.namespace` at another namespace. Using cluster-wide Secret RBAC, the operator reads that namespace's KafkaUser secret and copies the plaintext SASL credentials or TLS private key into the attacker's namespace.
Affected Features / Interoperability: The StreamsHub Console operator, KafkaUser Secret access, and tenant namespace isolation are affected. Cross-namespace Kafka credentials—including SASL secrets and TLS private keys—may be exposed, while the operator's cluster-wide Secret permissions make the cross-namespace behavior possible.
Source:
Actions:
Summary: The Red Hat OpenShift AI dashboard exposes an API route that reads Kubernetes Secrets using the dashboard service account and returns the complete Secret objects without authorization checks. Any authenticated dashboard user may obtain the cluster NVIDIA NGC API-key Secret and NIM image-pull Secret.
Affected Features / Interoperability: The `odh-dashboard` backend-for-frontend API for NIM serving, dashboard service-account Secret access, and NIM credential handling are affected. Administrative controls prevent creation and deletion of the credentials but do not protect the read path.
Source:
Actions:
Summary: Oracle TimesTen In-Memory Database's Kubernetes Operator contains a vulnerability that allows a low-privileged attacker with HTTPS network access to obtain unauthorized read access to a subset of database data. Affected versions are 22.1 through 22.1.40.0 and 26.1 through 26.1.1.2.0.
Affected Features / Interoperability: The TimesTen Kubernetes Operator and the subset of TimesTen data accessible through it are affected. The raw data does not identify specific operator commands, services, or downstream database integrations.
Source: https://www.oracle.com/security-alerts/cpuoct2026.html
Actions:
Summary: Lagoon's `ssh` service allows an authenticated Lagoon user to execute arbitrary code, potentially resulting in elevated administrative permissions. Versions before 2.33.1 are affected, and suspicious attempts may produce the string `too many arguments` in the service container logs.
Affected Features / Interoperability: The Lagoon core `ssh` service and its authenticated administrative interface are affected. Successful exploitation may compromise the service and enable actions with elevated administrative privileges.
Source:
Actions:
Summary: Trigger.dev self-hosted Docker Compose deployments using the default secrets from `hosting/docker/.env.example` contain a hardcoded magic-link secret. An unauthenticated attacker can forge valid tokens for any email address, log in as that user, and use default credentials to reach Postgres, Redis, and ClickHouse on runner infrastructure networks.
Affected Features / Interoperability: Trigger.dev authentication, magic-link tokens, and the self-hosted Docker Compose deployment are affected. Postgres, Redis, and ClickHouse instances reachable from runner containers may expose all tenant data to an unauthenticated attacker.
Source:
Actions:
Summary: In Splunk SOAR versions below 8.7.0, an authenticated user without Automation Broker edit permission can download the Automation Broker Docker Compose configuration. The file reveals the SOAR instance URL, container image location, and broker version.
Affected Features / Interoperability: Splunk SOAR Automation Broker configuration download and authorization are affected. The disclosed metadata can aid reconnaissance but does not by itself provide direct access to the SOAR instance or broker.
Source: https://advisory.splunk.com/advisories/SVD-2026-1010
Actions:
Summary: In affected Mailu releases, a domain manager can enable spoofing for another hosted domain they do not control. The malicious administrator can then send email authenticated through the victim domain's SPF and DKIM despite lacking control of that domain.
Affected Features / Interoperability: Mailu domain-management and mail-authentication controls are affected. SPF, DKIM, and message-spoofing protections can be undermined across hosted domains, potentially damaging the reputation of the affected domain.
Source:
Actions:
The following are unverified community and news reports, separate from the formal vulnerability data above.