A vulnerability in dnspython's dns.name.from_wire_parser() function allows a maliciously crafted DNS message to cause excessive CPU usage during DNS name decompression. This can degrade application performance or lead to denial of service (DoS) when processing untrusted DNS wire format messages. The issue is fixed in dnspython version 2.9.0. No known workarounds exist.
A regular expression denial of service (ReDoS) vulnerability exists in Datadog's dd-trace-py library affecting the URL query string obfuscation pattern used in HTTP tracing integrations. The vulnerable regex can cause excessive CPU consumption and stall request processing when handling certain attacker-controlled inputs, leading to denial of service. This issue affects ddtrace versions from 1.5.0 up to but not including 3.19.9, and from 4.0.0 up to but not including 4.15.6. A fix is available in versions 3.19.9 and 4.15.6. Workarounds involve setting environment variables to use a fixed regex pattern. The vulnerability is enabled by default in affected HTTP integrations that include query strings in URL span tags.
A vulnerability in dd-trace-py's IAST instrumentation can cause a denial of service by terminating the Python application process when processing certain attacker-controlled inputs. This issue affects only applications with IAST enabled, which is disabled by default. The flaw arises from improper handling of internal errors in string-processing instrumentation. Exploitation requires the vulnerable dd-trace-py version with IAST enabled and exposure of the affected operation to attacker input. A fix is available in version 4.15.5.
A vulnerability in the MongoDB Python driver (PyMongo) affects the C extension's BSON decoder when processing malformed Regex elements. This flaw allows an out-of-bounds read past the end of the caller's buffer, potentially causing a process crash via an uncatchable SIGSEGV signal. The issue impacts applications decoding untrusted BSON from mmap or array buffers, which lack NUL termination. The vulnerability affects all PyMongo releases from 3.9.0 up to but not including 4.18.3 when the C extension is loaded. The issue is fixed in version 4.18.3, where malformed Regex elements raise an InvalidBSON exception on all buffer types.
vLLM versions from 0.7.3 up to but not including 0.31.0 have a vulnerability where an attacker can control the mm_processor_kwargs.code_revision parameter in multimodal requests. When the operator enables trust_remote_code and serves a model whose Hugging Face processor uses dynamic auto_map code, this allows the attacker to execute arbitrary Python code by importing a malicious processor module revision. The vulnerability is exploitable via unauthenticated /tokenize endpoints unless protected externally. A fix is available in vLLM version 0.31.0.
The strands-agents FileSessionManager stores session data in a world-writable directory (/tmp/strands/sessions/) using predictable file paths and writes that follow symbolic links. This allows a local attacker to create symlinks to arbitrary files, causing the application to overwrite those files with attacker-controlled session data. This can lead to local privilege escalation by overwriting shell configuration files, SSH keys, cron jobs, or systemd user services. Additionally, the lack of integrity verification on session files enables persistent prompt injection attacks by tampering with session data.
The strands-agents package has a local confidentiality vulnerability in its default FileSessionManager storage. By default, session data is stored under /tmp/strands/sessions with directory and file permissions that allow other local users on shared systems to read sensitive session data. This can expose prompts, model outputs, tool inputs/outputs, intermediate states, and secrets stored in session files. The issue arises because the storage directories and files are created with permissions relying on the process umask, commonly 022, resulting in directories with 0755 and files with 0644 permissions. A fix is available in version 1.48.0 that addresses these permission issues.
A heap buffer overflow vulnerability exists in the Snappy.uncompress*Array typed-array methods of snappy-java before version 1.1.10.9. The issue arises because the methods size the result array by dividing the declared uncompressed byte length by the element size, but native code writes the full byte length, potentially writing up to 7 bytes past the end of the Java array if the length is not a multiple of the element size. This heap corruption can lead to application instability or crashes. The vulnerability is fixed in version 1.1.10.9, where the methods now reject uncompressed lengths that are not multiples of the element size by throwing a SnappyIOException. Users can mitigate by verifying the uncompressed length is a multiple of the element size before calling these methods.
A vulnerability in snappy-java prior to version 1.1.10.9 allows JVM crashes due to unchecked array range parameters in Snappy.arrayCopy and related stream read/write methods. The flaw arises from native memcpy calls without validating offsets and lengths, leading to out-of-bounds memory access and JVM crashes. This issue has been fixed in version 1.1.10.9 by adding proper range checks.
Several decompression functions in snappy-java versions prior to 1.1.10.9 allocate memory based on the uncompressed length declared in the compressed data without proper validation. This can lead to excessive memory allocation up to 2 GB or trigger exceptions, causing denial of service. The issue affects multiple entry points including Snappy.uncompress methods and input streams. The vulnerability is fixed in version 1.1.10.9 by validating and limiting the declared uncompressed length relative to the compressed input size.
A vulnerability in Grav versions from 1.7.53.3 up to but not including 1.7.53.6 allows unauthorized users to bypass authorization checks in the Debugger::isDebuggerRequestAuthorized() function. This flaw enables unauthenticated visitors to access /__clockwork/ profiler data by exploiting a fallback to loopback REMOTE_ADDR. When Grav is behind a same-host reverse proxy, remote requests can be treated as loopback, allowing attackers to read sensitive stored records such as administrator plaintext passwords and configuration credentials.
A race condition vulnerability exists in a2aproject a2a-java up to version 1.2.0.Final in the TaskManager.saveTaskEvent function. This vulnerability can be exploited remotely and may lead to integrity and availability impacts. Upgrading to version 1.3.0.Final resolves the issue.
A resource consumption weakness exists in a2aproject a2a-java up to version 1.2.0.Final in the Push Notification Config Store component. The vulnerability affects the InMemoryPushNotificationConfigStore.setInfo function and can be exploited remotely to cause resource exhaustion. Upgrading to version 1.3.0.Final mitigates the issue.
PowerProtect Data Domain Virtual Edition versions 7.7.1.0 through 8.7, and multiple LTS releases including 7.13.1.0 through 7.13.1.70, 8.3.1.0 through 8.3.1.30, and 8.6.1.0 through 8.6.1.10, contain a process control vulnerability. This flaw could allow a high privileged attacker with remote access to bypass protection mechanisms. The vulnerability has a CVSS 3.1 score of 7.2, indicating high severity.
A resource consumption vulnerability exists in the a2aproject a2a-java component ChildQueue's queue.offer function up to version 1.2.0.Final. This flaw can be exploited remotely and leads to denial of service conditions by exhausting resources. Upgrading to version 1.3.0.Final resolves the issue.
KGS Software tia Viewer has a stored cross-site scripting (XSS) vulnerability in its annotation API. An authenticated attacker can inject malicious JavaScript into stickynote annotations, which executes when any user opens the affected document. This vulnerability can lead to session compromise. The issue is fixed in version 1.2.8.
Dell PowerProtect Data Domain versions 7.7.1.0 through 8.8 (Feature Release), 7.13.1.0 through 7.13.1.80 (LTS2024), 8.3.1.0 through 8.3.1.40 (LTS2025), and 8.6.1.0 through 8.6.1.20 (LTS2026) contain a path traversal vulnerability. This flaw allows a highly privileged local attacker to potentially cause a denial of service. The vulnerability does not impact confidentiality but affects integrity and availability.
PowerProtect Data Domain versions 7.7.1.0 through 8.7, including certain LTS2024, LTS2025, and LTS2026 releases, contain a Relative Path Traversal vulnerability in the certificate handling. This flaw allows a high privileged attacker with remote access to potentially cause a denial of service condition. The vulnerability has a CVSS score of 6.5, indicating medium severity. No public exploits or patches are currently documented.
Dell PowerProtect Data Domain versions 7.7.1.0 through 8.8 (Feature Release), 7.13.1.0 through 7.13.1.80 (LTS2024), 8.3.1.0 through 8.3.1.40 (LTS2025), and 8.6.1.0 through 8.6.1.20 (LTS2026) contain a stack-based buffer overflow vulnerability. This flaw could be exploited by a high privileged attacker with remote access to cause a denial of service. The vulnerability does not impact confidentiality or integrity but affects availability. No public exploits or known active exploitation have been reported. The CVSS v3.1 base score is 4.9, indicating medium severity.