A critical authentication bypass vulnerability exists in gpustack versions from 0.7.1 up to but not including 2.2.2. The SAML callback endpoint processes unverified SAML responses without validating signatures or other security checks, allowing attackers with network access to authenticate as any user, including administrators, or provision new non-admin users. This leads to full account takeover and potential control over the deployment and managed infrastructure. The issue affects all deployments regardless of whether SAML SSO is configured. The vulnerability is fixed in gpustack 2.2.2 by enforcing proper SAML response validation and restricting callback routes to active providers only.
A denial of service vulnerability exists in the @nuxt/content module's POST /__nuxt_content/:collection/query endpoint. This endpoint accepts unauthenticated SQL queries and executes them against a local SQLite database after insufficient validation. The validator blocks only a few SQL keywords but does not block resource-intensive SQLite functions like randomblob(), zeroblob(), hex(), or length(). An attacker can exploit this to cause high memory and CPU usage, leading to server-wide denial of service. The vulnerability affects versions >=3.0.0 and <3.15.2 and is fixed in version 3.15.2.
compose-lint versions prior to 0.25.0 follow symlinks when reading project files, potentially exposing contents of files outside the project in its output. This can occur when a pull request commits a symlink pointing to sensitive files on the CI runner. The exposure includes quoted lines from non-YAML files and key names from env_file targets, visible in job logs and code scanning outputs. The issue is fixed starting from version 0.25.0, which restricts symlink resolution outside the project and removes quoted source lines from parse errors.
compose-lint versions from 0.2.0 up to but not including 0.32.0 automatically read a .compose-lint.yml policy file beside the Compose file. If this file is a symlink pointing outside the project directory, compose-lint follows it and reads the target file. When the target file contains invalid YAML, the parse error message includes a quoted snippet of the target file's content, exposing about 30 characters around the error line. This can leak small fragments of sensitive data, such as credentials, to pull request authors via job logs and code scanning uploads. The issue is fixed in version 0.32.0, which refuses to read symlinked policy files resolving outside the working directory and no longer quotes parse error lines.
compose-lint versions 0.22.0 through 0.31.0 can inadvertently disclose secret values from a CI-generated .env file when those secrets are referenced in the image field of a Docker Compose file. This occurs because compose-lint resolves ${VAR} references from the .env file and includes the resolved values in its findings, logs, JSON output, and SARIF reports. Although GitHub masks secrets in job logs, it does not mask them in uploaded JSON or SARIF artifacts or Code Scanning alert text, potentially exposing secrets in pull request workflows that have access to the .env file. The issue is fixed in version 0.32.0, which quotes the variable reference instead of the resolved secret value in outputs.
A flaw in compose-lint versions 0.9.0 through 0.17.0 causes the `fix --apply` command to incorrectly delete lines following the intended fix line when certain Unicode line break characters are present inside quoted values. This can unintentionally remove security-related settings such as network restrictions. The issue arises from inconsistent line break handling between the YAML parser and the fix application logic. The problem is fixed in version 0.18.0, which unifies line break definitions and rejects files with ambiguous line breaks.
The compose-lint GitHub Action prior to version 0.31.0 outputs text that can be interpreted by the GitHub Actions runner as workflow commands. This allows a malicious Compose file in a pull request to inject commands that create fake error or warning annotations, fold logs to hide real verdicts, or mask strings in the log output. The issue arises because the Action does not neutralize the legacy command syntax '##[' in its text report output. The vulnerability was fixed in version 0.31.0 by escaping these sequences and using a stop-commands token to prevent command processing during output.
compose-lint versions from 0.22.0 up to but not including 0.31.0 improperly follow symlinks when reading the .env file, allowing a symlink outside the project directory to be read. This can expose environment variables from the CI runner, including secrets in certain configurations, via log outputs in JSON or SARIF formats. The issue is fixed in version 0.31.0 by enforcing containment checks on .env reads and refusing .env files that resolve outside the project directory.
Cocos AI's intra-handshake attested TLS implementation is vulnerable to a Time-Of-Check to Time-Of-Use (TOCTOU) attack. An attacker who can modify the attested workload's code, memory state, or configuration after the initial attestation but without terminating the TLS connection can cause the peer to continue trusting a stale attestation state. This vulnerability affects long-lived TLS connections because attestation is only performed once at connection establishment, with no mechanism for re-attestation during the connection lifetime. The issue was discovered through formal analysis and affects versions prior to 0.9.0.
A critical vulnerability in node-opcua allows unauthenticated (Anonymous) clients to write protected variables and call privileged methods on nodes lacking explicit per-node permissions. This occurs because the server incorrectly grants all permissions when the namespace default role permissions are unset or null, violating OPC UA's default-deny security model. The flaw arises from a fail-open authorization logic and a disconnect between configuration and runtime enforcement, causing namespace default permissions to be ignored. This affects node-opcua versions from 2.42.0 up to but not including 2.180.0. A fix is available in version 2.180.0.
A path traversal vulnerability exists in the Dagu MCP DAG specification read functionality (CVE-2026-102943) prior to version 2.11.0. The vulnerability arises because a traversal fix applied as HTTP middleware does not apply to in-process API calls made by the MCP service, allowing arbitrary YAML file reads with a viewer-role key. The flaw bypasses path containment and workspace isolation checks, enabling read-only access to .yaml/.yml files outside intended directories. The issue is confirmed at the HEAD commit after version 2.10.7 and fixed in version 2.11.0.
A vulnerability in the gopacket library's SCTP protocol decoder allows crafted SCTP segments to cause runtime panics due to out-of-bounds slice reads. This occurs because sub-decoders for SCTP chunk types do not validate chunk lengths against required minimums, leading to crashes when processing malicious input. The issue affects all released versions through v1.7.1 and the current master branch. It was fixed in version 1.7.2 by adding proper length checks in the sub-decoders, preventing panics and returning decode errors instead.
The npm package @web3-common/utils version 1.0.0 contains malicious code that fully compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected machine should be rotated immediately from a different, trusted device. Removal of the package alone does not guarantee the elimination of all malicious software introduced by the package.
Eclipse Kura versions 3.1.0 through 5.6.2 contain a vulnerability in the iBeacon and Eddystone advertisement decoders where the AD-structure length field of BLE advertising payloads is improperly parsed. An unauthenticated attacker within BLE range can send a crafted two-byte advertising payload that causes the beacon-scanner thread to enter an infinite loop, consuming a CPU core and halting beacon ingestion until the gateway is restarted. This attack requires the iBeacon/Eddystone scanner component to be installed and active, which is not the default configuration.
Improper input validation in Ivanti EPMM before version 12.11.0.0, 12.10.0.1, and 12.9.0.3 allows a remote authenticated attacker with admin privileges to set arbitrary Linux kernel parameters as root.
A path traversal vulnerability in Ivanti Sentry before versions 11.0, 10.8.3, and 10.7.4 allows a remote authenticated attacker with administrative privileges to create arbitrary directories and files with root privileges.
An insecure default initialization of resource in the Tomcat shutdown listener of Ivanti Sentry before versions 11.0, 10.8.3, and 10.7.4 allows a local authenticated attacker to cause a denial of service.
The npm package 'fapshi' version 1.1.4 contains malicious code that compromises any computer on which it is installed or running. The compromise is severe enough that all secrets and keys stored on the affected system should be rotated immediately from a different, clean computer. Removing the package alone does not guarantee removal of all malicious software, as full control may have been given to an external attacker.
An uncontrolled XML entity expansion vulnerability in the Flock Installer app for Android before version 2.35.0 allows an attacker who has a valid technician account and controls or impersonates the camera being set up to crash the app, on devices running Android 10, 11 or 12, by returning a camera configuration response that contains nested XML entity declarations. The vulnerability does not allow the attacker to read or change data on the device, and no customer license plate, video or location data is exposed. Android 13 and later reject the response. The issue is fixed in version 2.35.0; update to 2.35.0 or later.
Argument injection in Ivanti Sentry before version 11.0, 10.8.3, and 10.7.4 allows a remote authenticated attacker with admin privileges to execute arbitrary on-disk binaries.