Daily Digest
The most urgent item in today's digest is CVE-2026-87911 (PostgreSQL ecosystem, CVSS 9.6 CRITICAL): an OS command injection flaw in Amazon's `awslabs/postgres-mcp-server` that allows an unauthenticated attacker to execute operating system commands on a self-managed PostgreSQL host by injecting a crafted `COPY ... TO PROGRAM` statement into MCP server content. With a CVSS of 9.6 and no CISA KEV entry to compete against, this is the highest-severity confirmed vulnerability affecting database infrastructure this cycle. No KEV-confirmed entries were present in today's data, so the highest CVSS score determines priority.
Summary: A SQL injection vulnerability exists in the `mysqli_query` function of the `Front-end/university.php` file in the Mstfakts College-Management-System's Search Handler. Manipulation of the `book_name` or `book_author` arguments enables remote SQL injection. The exploit has been made public, and the project uses a rolling release system, so no version-specific patch information is disclosed.
Affected Features / Interoperability: The Search Handler component and its `mysqli_query` function are directly impacted. Any downstream functionality relying on the search feature—such as university catalog queries or book lookups—could be compromised. No specific interoperability impacts (e.g., replication, client drivers) are documented in the raw data.
Source:
Actions:
---
Summary: An OS command injection weakness exists in the read-only enforcement of the SQL validation component in Amazon `awslabs/postgres-mcp-server` before version 1.1.7. An unauthenticated actor can execute operating system commands on the host of a self-managed PostgreSQL server by placing a crafted `COPY ... TO PROGRAM` statement into content processed when an authenticated user interacts with the MCP server in its default read-only mode.
Affected Features / Interoperability: The `postgres-mcp-server` component and its SQL validation/read-only enforcement are impacted. The `COPY ... TO PROGRAM` PostgreSQL feature is the attack vector. Downstream integrations relying on the MCP server for PostgreSQL access—including AI tooling, automation pipelines, and any client connecting through the MCP layer—could be compromised. The vulnerability bypasses the intended read-only mode of the MCP server.
Source:
Actions:
---
Summary: The `go-base` Go RESTful API boilerplate template, backed by PostgreSQL, hardcodes its JWT signing secret to the known string `"random"` in versions prior to 2026-05-18. Any attacker who reads the public repository can forge JWT tokens for arbitrary users, including admin roles, completely bypassing authentication on all protected endpoints. The secret is set in both the `dev.env` template and a programmatic fallback in `cmd/serve.go`, meaning the application uses it even when no `.env` file is present.
Affected Features / Interoperability: JWT-based authentication in `go-base` applications backed by PostgreSQL is compromised. All protected API endpoints are accessible with forged tokens. The original mitigation in `auth/jwt/tokenauth.go` only caught the exact string `"random"`, allowing other weak secrets through. The replacement in-memory key was not persisted, invalidating all tokens on every restart and causing a denial-of-service condition.
Source:
Actions:
---
Summary: In Open WebUI versions 0.6.41 through 0.11.1, the `get_user_by_oauth_sub` and `get_user_by_scim_external_id` functions in `backend/open_webui/models/users.py` used JSON contains matching that compiled to SQL LIKE substring matching on SQLite. An OAuth subject containing percent or underscore wildcard characters could resolve to a different stored identity, potentially selecting an administrator account and issuing the attacker that account's session. PostgreSQL deployments were explicitly not affected by this vulnerability.
Affected Features / Interoperability: Open WebUI's OAuth and SCIM authentication flows on SQLite-backed deployments are impacted. The vulnerability allows identity confusion via wildcard characters in OAuth subject claims. PostgreSQL deployments are not affected. Downstream functionality such as AI platform access control and user session management could be bypassed on affected SQLite deployments.
Source:
Actions:
---
Summary: The `pgjdbc` open-source PostgreSQL JDBC Driver (versions 42.2.0 through before 42.7.11) is vulnerable to a client-side denial of service during SCRAM-SHA-256 authentication. A malicious server can instruct the driver to perform SCRAM authentication with a very large iteration count, causing the client to spend an unbounded amount of CPU time inside PBKDF2 before authentication can fail. A single attempt ties up a CPU core, and repeated or concurrent attempts can exhaust client CPU and wedge connection pools. The `loginTimeout` setting did not fully mitigate this problem, as the worker thread could continue burning CPU even after the timeout expired.
Affected Features / Interoperability: The `pgjdbc` JDBC Driver's SCRAM-SHA-256 authentication path is impacted. Any Java application using `pgjdbc` to connect to a PostgreSQL server is vulnerable if connecting to a malicious or compromised server. Connection pools in affected Java applications could be exhausted, leading to service disruption. Downstream integrations relying on JDBC connections—such as Java-based data pipelines, application servers, and ETL tools—could be affected.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB PHP Library allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.
Affected Features / Interoperability: The GridFS component of the MongoDB PHP Library is impacted. File storage and retrieval operations via GridFS in PHP applications are compromised. Downstream integrations relying on GridFS for file storage—such as document management systems, media libraries, and content repositories—could experience data leakage or data loss. The rename operation may also corrupt file organization.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Rust Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable.
Affected Features / Interoperability: The GridFS component of the MongoDB Rust Driver is impacted. File storage and retrieval operations via GridFS in Rust applications are compromised. Downstream integrations relying on GridFS for file storage in Rust-based services could experience data leakage or data loss.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB C# Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.
Affected Features / Interoperability: The GridFS component of the MongoDB C# Driver is impacted. File storage and retrieval operations via GridFS in C#/.NET applications are compromised. Downstream integrations relying on GridFS for file storage in .NET-based services could experience data leakage or data loss. The rename operation may also corrupt file organization.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Python Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.
Affected Features / Interoperability: The GridFS component of the MongoDB Python Driver is impacted. File storage and retrieval operations via GridFS in Python applications are compromised. Downstream integrations relying on GridFS for file storage in Python-based services (including data science and ML pipelines) could experience data leakage or data loss. The rename operation may also corrupt file organization.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Ruby Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable.
Affected Features / Interoperability: The GridFS component of the MongoDB Ruby Driver is impacted. File storage and retrieval operations via GridFS in Ruby applications are compromised. Downstream integrations relying on GridFS for file storage in Ruby-based web applications could experience data leakage or data loss.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Java Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable. The affected rename operation may also rename a stored file other than the intended target.
Affected Features / Interoperability: The GridFS component of the MongoDB Java Driver is impacted. File storage and retrieval operations via GridFS in Java applications are compromised. Downstream integrations relying on GridFS for file storage in Java-based enterprise applications could experience data leakage or data loss. The rename operation may also corrupt file organization.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB C++ Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable.
Affected Features / Interoperability: The GridFS component of the MongoDB C++ Driver is impacted. File storage and retrieval operations via GridFS in C++ applications are compromised. Downstream integrations relying on GridFS for file storage in performance-critical C++ services could experience data leakage or data loss.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB C Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may obtain stored file content beyond the intended target or cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable.
Affected Features / Interoperability: The GridFS component of the MongoDB C Driver is impacted. File storage and retrieval operations via GridFS in C applications are compromised. Downstream integrations relying on GridFS for file storage in C-based services or embedded systems could experience data leakage or data loss.
Source:
Actions:
---
Summary: Improper neutralization of special elements in data query logic in the GridFS component of the MongoDB Go Driver allows a caller-supplied structured file identifier to be interpreted as a query condition rather than as a literal identifier. An authenticated user who can influence the identifier passed by an affected application may cause all GridFS file chunks in the affected bucket to be removed, rendering stored file content unreadable.
Affected Features / Interoperability: The GridFS component of the MongoDB Go Driver is impacted. File storage and retrieval operations via GridFS in Go applications are compromised. Downstream integrations relying on GridFS for file storage in Go-based microservices could experience data loss. Note that this entry specifically mentions chunk removal but does not explicitly mention content leakage or rename operations, unlike some other driver entries.
Source:
Actions:
The most urgent cloud security issue is the critical command‑injection flaw in the Kubernetes Logging Operator (CVE-2026-54680, CVSS 9.9 CRITICAL), which lets any user who can create Flow resources execute arbitrary commands inside the Fluentd aggregator; upgrading to Logging Operator 6.6.0 or later mitigates this risk.
Summary: Improper neutralization of special elements in Azure CLI enables an authorized attacker to inject and execute arbitrary commands over a network, potentially compromising automation scripts and CI/CD pipelines that rely on the CLI.
Affected Features / Interoperability: Azure CLI command processing; impacts any automation, deployment, or management workflows that invoke the CLI.
Source: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83948
Actions:
Summary: The cloud-healthcare-fhir-fetch-page tool accepts an unvalidated pageURL parameter and forwards authenticated requests to that URL, automatically attaching the caller’s OAuth/Bearer token, allowing credential exfiltration to an attacker‑controlled endpoint.
Affected Features / Interoperability: cloud-healthcare-fhir-fetch-page tool; could leak service‑account or user tokens, jeopardizing access to GCP services and protected health information.
Source: https://github.com/googleapis/mcp-toolbox/pull/3453
Actions:
Summary: A SSRF flaw in Google Cloud Gemini Enterprise Agent Platform App Builder (pre‑2026‑06‑01) lets an unauthenticated attacker leak the Compute Engine default service‑account access token by forcing the app to request an external URL. The issue was patched on 2026‑06‑01; existing deployments must be redeployed.
Affected Features / Interoperability: Gemini Enterprise Agent Platform App Builder; exposure of the default service‑account token could lead to broader GCP resource compromise.
Source: https://docs.cloud.google.com/gemini-enterprise-agent-platform/release-notes#July_20_2026
Actions:
Summary: The Logging Operator’s FluentRender component writes unescaped CRD strings into fluent.conf, allowing a user who can create Flow resources to inject a Fluentd `<match **>` block with `@type exec` and execute arbitrary commands inside the Fluentd aggregator. Fixed in version 6.6.0.
Affected Features / Interoperability: Logging Operator’s Fluentd configuration; compromise could affect log pipelines, expose sensitive logs, and provide a foothold for further cluster access.
Source:
Actions:
Summary: A YAML injection in Apache Camel K custom resource definitions lets an authorized CR author inject arbitrary Kubernetes objects, potentially enabling unauthorized resource creation with the operator’s privileges. Affected versions: 2.0.0 < 2.9.3 and 2.10.1 < 2.10.2; fixed in 2.9.3, 2.10.2, and 2.11.0.
Affected Features / Interoperability: Apache Camel K operator and CR handling; could lead to privilege escalation and unintended workload deployment.
Source:
Actions:
Summary: In Traefik v3.7.0‑v3.7.11, the Kubernetes ingress‑nginx provider mishandles Ingresses that carry both an authentication annotation and the `nginx.ingress.kubernetes.io/from-to-www-redirect` annotation, creating a bypass router that discards authentication and other middleware. Fixed in Traefik v3.7.12.
Affected Features / Interoperability: Traefik ingress‑nginx provider; impacts authentication, source‑IP allowlisting, and any annotation‑derived middleware for affected Ingress objects.
Source:
Actions:
Summary: The vault-secrets-webhook mutating webhook, prior to v1.23.1, incorrectly processes the `vault.security.banzaicloud.io/vault-serviceaccount` annotation, allowing an attacker‑controlled Vault address to receive a ServiceAccount JWT and potentially extract secrets. Fixed in version 1.23.1.
Affected Features / Interoperability: Vault‑secrets‑webhook secret injection; compromise could lead to unauthorized access to Vault and leakage of secrets injected into pods.
Source:
Actions:
Summary: Kyverno before v1.13.4 is vulnerable to SSRF via its Service Call feature; an attacker with permission to create Kyverno policies can specify an external URL, causing the controller to send pod‑level data (including secrets) to that endpoint. Fixed in v1.13.4.
Affected Features / Interoperability: Kyverno Service Call functionality; could result in exfiltration of secrets and other sensitive cluster data.
Source:
Actions:
Summary: Traefik v3.7.0‑v3.7.10 suffers from an authentication bypass in the Kubernetes Ingress NGINX provider due to TLS option name conflicts when two Ingresses share the same host, client CA secret, and auth mode; this causes Traefik to fall back to a default TLS config that does not request client certificates. Fixed in v3.7.11.
Affected Features / Interoperability: Traefik TLS option handling for Ingress NGINX provider; could allow unauthorized access to resources intended to be protected by client‑certificate authentication.
Source:
Actions:
Summary: Coolify versions before 4.2.0 insufficiently escape environment variable key names when constructing Docker commands over SSH, enabling authenticated attackers to inject shell metacharacters into env‑var keys and execute arbitrary commands on the host system.
Affected Features / Interoperability: Coolify’s SSH‑based Docker command execution; impacts host‑level security and could lead to full host compromise.
Source:
Actions:
Summary: Renovate versions prior to 44.3.1 do not apply the `minimumReleaseAge` check to digest updates, allowing potentially malicious newly‑published digests to trigger pull requests and CI runs before the configured stability age has elapsed. Fixed in Renovate 44.3.1; digest updates can also be disabled or gated.
Affected Features / Interoperability: Renovate dependency‑update automation; impacts the timing and safety of automated PRs for digest‑based dependencies (e.g., pinned Docker images, Go modules).
Source:
Actions: