The graphql-scalars package's PhoneNumber scalar is vulnerable to a regular expression denial of service (ReDoS) due to an exponential backtracking flaw introduced in version 1.24.1. This flaw allows specially crafted inputs of digits followed by a failing character to stall the JavaScript thread for seconds, with processing time doubling for each additional digit. The vulnerability affects all versions from 1.24.1 up to and including 2.0.0. The regex runs during GraphQL document validation and variable coercion, before any authentication or authorization, enabling unauthenticated requests to cause denial of service. A fix is available in version 2.0.1.
LangGraph API versions from 0.1.2 up to but not including 0.15.0 that use JavaScript or TypeScript custom authentication with namespace rewriting for Store authorization may allow authenticated users to access or modify data outside their authorized namespace. This vulnerability does not affect Python custom authentication or handlers that reject unauthorized namespaces. The issue is fixed in version 0.15.0.
filelock versions 4.1.0 through 4.2.0 contain a vulnerability in SoftReadWriteLock where a local user with write access to the lock's parent directory can replace the lock directory tree with symbolic links after the first lock acquire. This causes the lock user process to write lock records through the symbolic links, potentially corrupting files such as a git repository's HEAD file. The vulnerability requires local access and specific directory conditions but does not expose confidentiality or availability impacts. It has a low CVSS score of 3.3 and is fixed in version 4.2.1.
The filelock library versions 3.30.0 through 4.2.0 have a vulnerability in StrictSoftFileLock and AsyncStrictSoftFileLock where claim directories are created without applying the caller's restrictive mode, resulting in directories with permissions influenced by the process umask or parent directory ACLs. This can allow another local user with write access to these directories to unlink claim files, causing multiple holders to believe they hold the lock simultaneously, leading to integrity issues. The vulnerability requires a local attacker with low privileges and specific environment conditions such as a permissive umask or default ACLs. The issue is fixed in version 4.2.1.
filelock versions 3.30.0 through 4.2.0 have a vulnerability where StrictSoftFileLock and SoftReadWriteLock classes adopt a protocol directory created by another local user if it exists before the lock user's first acquire. This allows the other user to manipulate lock state files, causing integrity and availability issues such as multiple writers entering critical sections simultaneously and denial of service via spinning locks or memory exhaustion. The vulnerability requires local access and the ability to create directories in shared sticky-bit directories like /tmp before the lock user. It has no confidentiality impact but high integrity and availability impact. A fix is available in version 4.2.1.
The filelock library on Windows ignores the 'mode' argument when creating lock files, causing files intended to have restrictive permissions (0o600) to inherit the directory's ACL instead. This allows other local accounts with read or modify access to the directory to read or write the lock files and interfere with the locking mechanism. The issue affects filelock versions 3.10.0 through 4.2.0 on Windows and is confirmed by the maintainers. Unix systems are not affected. A fix is available in version 4.2.1.
filelock versions 3.20.4 through 4.2.0 contain a vulnerability in the ReadWriteLock and AsyncReadWriteLock mechanisms where a crafted SQLite lock database file can cause every acquire operation to stall or hang indefinitely, ignoring timeout and blocking settings. This is due to the lock code running PRAGMA journal_mode=MEMORY on a fresh SQLite connection for each acquire, which loads the entire schema from the file at the lock path. A local attacker who can place or overwrite this file can cause denial of service by making acquires hang or spin at 100% CPU. The impact is availability only; no confidentiality or integrity is affected. The vulnerability is fixed in filelock 4.2.1.
A vulnerability in filelock versions 3.22.0 through 4.2.0 allows a local user with write access to a lock marker file to forge the process ID (PID) recorded in the marker. This causes another process, running as the lock owner or root, to mistakenly consider the lock stale and remove the live marker, resulting in two processes concurrently holding the lock. The issue arises when the marker file is group- or other-writable due to explicit mode settings or permissive umask values in sticky or non-removable directories. The vulnerability has a medium severity with a CVSS score of 4.7 and impacts integrity but not confidentiality or availability. A fix is available in version 4.2.1.
A symlink swap vulnerability in filelock's SoftFileLock writability check allows a local user with directory write access to leak one bit of information about whether a path exists and is writable by the lock user. This occurs due to a time-of-check to time-of-use (TOCTOU) race condition involving os.lstat and os.access calls. The vulnerability affects filelock versions 3.32.6 through 4.2.0 and is mitigated by Linux kernel's protected symlinks feature in common sticky world-writable directories like /tmp. The impact is limited to leaking a single bit of path existence and writability information with high attack complexity and no integrity or availability impact. A fix is available in version 4.2.1.
The filelock library's UnixFileLock backend on Unix systems truncates and changes permissions of any regular file that another local user renames or hard-links onto the lock path. This occurs when the lock user acquires the lock and the file exists at the lock path, leading to unintended truncation and potential permission escalation. The vulnerability affects all filelock versions up to and including 4.2.0 and requires local user access with certain directory permission conditions. The issue is fixed in version 4.2.1.
A race condition vulnerability in filelock versions 3.30.0 through 4.2.0 allows a local unprivileged user to swap a symbolic link at the <path>.filelock directory after an lstat check but before subsequent operations. This can cause the lock user's process to create claim files in an attacker-chosen directory, potentially disrupting other locks by causing stranded claims that lead to denial of service until manually force-broken. The vulnerability requires write access to the directory containing <path>.filelock and is mitigated by patch 4.2.1.
filelock versions 4.0.0 through 4.2.0 contain a vulnerability in SoftReadWriteLock where the holder record refresh writes through a hard link or hangs on a named pipe (FIFO) placed by another local user who owns the lock's .rw directory. This can cause the lock user's write_lock or read_lock operations to hang indefinitely and the heartbeat thread to stop without notification, allowing multiple processes to believe they hold the lock simultaneously. The issue requires local user access and specific conditions such as permissive hard-link policies or ownership of the lock directory. The vulnerability has medium severity with no confidentiality impact but can cause integrity loss and high availability impact. A fix is available in version 4.2.1.
OpenTelemetry Java's W3C trace-context propagator has a vulnerability that allows crafted tracestate headers to cause excessive CPU consumption due to quadratic regex backtracking. This can lead to denial of service by blocking the parsing thread. The issue affects versions prior to 1.67.0 and is fixed in version 1.67.0. Mitigation includes upgrading to 1.67.0 or later or rejecting oversized tracestate headers before extraction.
A vulnerability in the @graphql-tools/executor-legacy-ws package causes per-request WebSocket connection parameters to persist across different users. This stale authentication state leads to later users inheriting previous users' authentication credentials in the connection_init payload, potentially allowing unauthorized access to downstream GraphQL subscriptions. The issue affects versions prior to 1.1.36 and is fixed in version 1.1.36.
The Echo web framework versions prior to 5.1.1 and 4.15.2 contain a vulnerability in the Scheme() method that trusts certain HTTP headers (X-Forwarded-Proto, X-Forwarded-Protocol, X-Url-Scheme) without validating their values. This allows attackers to inject arbitrary URI schemes into redirect URLs generated by the WWWRedirect and NonWWWRedirect middlewares, potentially leading to open redirect issues and cache poisoning. The vulnerability is fixed in Echo v5.1.1 and v4.15.2 by whitelisting accepted schemes.
A path traversal vulnerability (CWE-22) exists in langchain-ai's langgraph Python SDK and langgraph versions prior to 0.4.6 and 1.2.14 respectively. The issue arises when certain helper functions interpolate user-controlled assistant_id and thread_id values into authenticated GET request paths without proper encoding, allowing relative path segments to access unintended server paths. This vulnerability is fixed in langgraph-sdk 0.4.6 and langgraph 1.2.14.
The decode-uri-component package prior to version 0.5.1 contains an uncontrolled resource consumption vulnerability. Its fallback decoding function can cause quadratic CPU usage when processing malformed inputs with many distinct percent-encoded sequences, leading to blocking of the Node.js event loop. This issue is resolved in version 0.5.1.
A vulnerability in honojs node-server versions from 1.19.10 up to but not including 2.1.3 allows an unauthenticated attacker to bypass middleware protections on static file serving. The issue arises because the serveStatic function decodes the request path a second time after initial decoding by Hono, leading to inconsistent path evaluation. This can cause the static file handler to serve files from within the configured static root directory that should be protected by middleware. The flaw does not allow directory traversal outside the static root. The vulnerability is fixed in version 2.1.3.