Vulnerabilities

NocoDB is software for building databases as spreadsheets. Prior to 2026.04.4, deleted API tokens continued to authenticate requests until their cache entry expired, because the auth cache was not invalidated by token value at deletion time. The API token deletion path removed the database row but did not evict the token-value keyed entry from the auth cache. The auth middleware therefore continued to accept the deleted token until the cache entry aged out, leaving a deletion-to-revocation window of up to three days. This vulnerability is fixed in 2026.04.4.

NocoDB is software for building databases as spreadsheets. Prior to 2026.05.1, the public shared-view relation endpoints accepted a caller-supplied column ID without verifying that the column was visible in the shared view, so anyone holding a share UUID could read links from any LTAR column on the view's table — including columns the view owner had hidden. publicMmList, publicHmList, and relDataList already ensured that the requested column belonged to the view's model, but did not check the view-column entry's show flag. This vulnerability is fixed in 2026.05.1.

NocoDB is software for building databases as spreadsheets. Prior to 2026.04.1, a reflected XSS vulnerability exists in the Page Leaving Warning page. The ncRedirectUrl and ncBackUrl query parameters are used in window.location.href and tag bindings without validation, allowing javascript: URI injection. This vulnerability is fixed in 2026.04.1.

FOSSBilling is a free, open-source billing and client management system. In versions 0.7.2 and prior, a query-construction flaw in client list endpoints allowed authenticated clients to bypass tenant scoping and retrieve other clients’ data. Details<br /> In ServiceTransaction::getSearchQuery() and Order\Service::getSearchQuery(), OR-based search/action filters were appended without grouping, allowing SQL operator precedence to evaluate OR clauses independently of the enforced client_id constraint. Crafted requests could therefore return records and metadata belonging to other clients, including identifiers, amounts, status, timestamps, and related fields. This issue was fixed in version 0.8.0.

A flaw was found in GStreamer&amp;#39;s gst-plugins-bad package. When processing a specially crafted H.264 video file containing malformed MVC or SVC extension slice NAL units, a 1-byte heap out-of-bounds read can occur during parsing. This happens when the parser attempts to check slice boundary information without first verifying that the NAL unit contains enough data beyond the extension header. An attacker could exploit this by tricking a user into opening a malicious H.264 video file, potentially causing the application to crash or leak a single byte of heap memory.

A flaw was found in the GStreamer gst-plugins-bad package. When processing a malformed H.266/VVC video stream with a crafted aspect ratio indicator value, the H.266 parser performs an out-of-bounds read of up to 8 bytes from adjacent memory. This flaw allows an attacker to craft a malicious H.266 video file or stream that, when processed by a GStreamer-based application, could leak limited memory contents through video metadata, potentially exposing sensitive information from the application&amp;#39;s address space.

A flaw was found in the community.general Ansible collection&amp;#39;s nexmo module.<br /> The module constructs HTTP requests to the Vonage/Nexmo SMS API by encoding<br /> API credentials (api_key and api_secret) into URL query parameters and<br /> sending them via GET requests. This causes credentials to be exposed in web<br /> server access logs, proxy logs, HTTP Referer headers, and network monitoring<br /> tools, despite the Ansible argument specification marking these parameters<br /> as no_log. An attacker with access to any of these logging or monitoring<br /> points can obtain the full API credentials and gain unauthorized access to<br /> the victim&amp;#39;s Vonage/Nexmo account.

Module: plugins/modules/keyring_info.py <br /> <br /> CVSS 3.1: 5.5 MEDIUM — AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N <br /> <br /> Issue: The module retrieves a passphrase from the OS native keyring (GNOME Keyring, macOS Keychain, Windows Credential Manager) and places it directly into result["passphrase"] with no output suppression, no no_log protection, and no documentation warning. <br /> <br /> Root Cause:<br /> <br /> Line 105 (protected): keyring_password=dict(type="str", required=True, no_log=True)<br /> Line 127 (NOT protected): result["passphrase"] = passphrase<br /> <br /> Observed Output:<br /> <br /> {<br /> "changed": false,<br /> "passphrase": "MyMasterP@ssw0rd!SSH_Key_Secret"<br /> }<br /> Visible via register + debug:<br /> {<br /> "keyring_result": {<br /> "changed": false,<br /> "passphrase": "MyMasterP@ssw0rd!SSH_Key_Secret"<br /> }<br /> }<br /> <br /> Impact: <br /> <br /> Master passwords, SSH key passphrases and service credentials appear in all Ansible output <br /> <br /> register: keyring_result followed by debug: var=keyring_result prints passphrase in full <br /> <br /> Ansible fact caching backends (Redis, JSON file, memcached) may persist the passphrase <br /> <br /> AWX/Tower job logs silently store the live credential<br /> <br /> Fix:<br /> <br /> module.exit_json(changed=False, passphrase=passphrase, _ansible_no_log=True)<br /> <br /> Also add a documentation warning requiring callers to use no_log: true at the task level.<br /> <br /> PoCs<br /> <br /> <br /> Fig 1: PoC execution showing passphrase in plaintext output<br /> <br /> <br /> Fig 2: Source code showing no_log=True on input (line 105) vs unprotected output (line 127)

A missing authorization vulnerability was found in the Event-Driven Ansible (EDA) websocket API. The /api/eda/ws/ansible-rulebook endpoint does not verify user permissions when processing Worker messages. Any authenticated user can send a forged message with an arbitrary activation_id to receive plaintext credentials associated with that activation, including OAuth tokens, vault passwords, and SSH keys.

A flaw was found in the foreman-mcp-server. A session management vulnerability in the MCP Server allows unauthenticated attackers to hijack active administrative sessions due to an improper cache of authenticated client connections, by trusting a non-secret session ID without re-validating authentication tokens and by logging all newly created session IDs to standard logs. This issue can result in privilege escalation and infrastructure-wide code execution.

Traefik is an HTTP reverse proxy and load balancer. From 3.7.0-ea.1 until 3.7.5, there is a medium severity vulnerability in Traefik&amp;#39;s Kubernetes Ingress NGINX provider that causes affected routes to fail open. When an Ingress explicitly enables BasicAuth or DigestAuth through the supported nginx.ingress.kubernetes.io/auth-type and auth-secret annotations, but the referenced auth Secret cannot be resolved or parsed, Traefik logs the resolution error, skips installing the authentication middleware, and still emits a router to the backend service. A route that operators intended to protect is therefore published to the data plane without its authentication control, allowing unauthenticated access to the backend. The trigger is an invalid or unresolved auth dependency — a missing, malformed, unreadable, or policy-denied Secret — rather than an intentionally unprotected route. This vulnerability is fixed in 3.7.5.

Traefik is an HTTP reverse proxy and load balancer. Prior to 3.6.21 and 3.7.5, there is a high severity vulnerability in Traefik&amp;#39;s Kubernetes Gateway provider affecting the crossProviderNamespaces allowlist. For HTTPRoute rules that declare multiple (WRR) backendRefs, Traefik evaluates the allowlist against the target backendRef.namespace instead of the route&amp;#39;s own namespace. As a result, an HTTPRoute created in a namespace that is not allow-listed can reference a cross-provider TraefikService such as api@internal, dashboard@internal or rest@internal by pointing backendRef.namespace at an allow-listed namespace covered by a Gateway API ReferenceGrant, exposing internal Traefik services on the data plane. Exploitation requires the ability to create an accepted HTTPRoute and a matching ReferenceGrant from an allow-listed namespace; it does not require any change to Traefik static configuration, RBAC, or the deployment itself. This vulnerability is fixed in 3.6.21 and 3.7.5.