CVE-2025-62373 is a critical remote code execution (RCE) vulnerability in Pipecat, an open-source Python framework for building real-time voice and multimodal conversational agents. The flaw originates from the unsafe deserialization of untrusted data using Python's pickle module within the LivekitFrameSerializer class.
Kirby CMS versions prior to 4.9.0 and 5.0.0 through 5.3.x are vulnerable to XML Injection (CWE-91). An insecure heuristic within the Toolkit's XML handling methods permits an attacker to bypass entity encoding by prepending a CDATA identifier. This allows the injection of arbitrary XML elements into documents generated by the CMS or custom plugins.
The Azure go-ntlmssp package prior to version 0.1.1 contains a denial-of-service vulnerability stemming from improper input validation. Malicious servers can trigger an unrecoverable Go panic by supplying a crafted NTLM Challenge message, terminating the client application process.
Actual versions prior to 26.4.0 contain a critical privilege escalation vulnerability within the sync-server component. The flaw affects environments migrating to OpenID Connect (OIDC) and allows an authenticated user with a basic role to hijack an administrative account via an orphaned password record.
Kirby CMS versions prior to 4.9.0 and 5.4.0 contain a critical double template resolution vulnerability leading to Server-Side Template Injection (SSTI). The software also suffers from an authorization bypass in the REST API, allowing authenticated users to circumvent editorial workflows and publish content without appropriate status-change permissions.
Apktool versions 3.0.0 and 3.0.1 contain a high-severity path traversal vulnerability due to a security regression in resource decoding. By crafting a malicious APK with a modified resources.arsc file, an attacker can escape the intended output directory, leading to arbitrary file write and potential remote code execution on the analyst's machine.
Kirby CMS versions prior to 4.9.0 and 5.4.0 contain an incorrect authorization vulnerability in the REST API. Authenticated users with page creation permissions can bypass editorial workflows to publish content directly, circumventing the intended status change restrictions.
Melange versions 0.32.0 through 0.43.3 contain a path traversal vulnerability in the pipeline compilation mechanism. By supplying directory traversal sequences in the `pipeline[].uses` field, an attacker can load arbitrary YAML files from the host filesystem. When these files contain execution directives, they are evaluated within the build sandbox, leading to unauthorized command execution.
Melange versions prior to 0.43.4 are vulnerable to a path traversal attack when processing untrusted APK packages with the `--persist-lint-results` flag. Attackers can manipulate the `.PKGINFO` metadata to write JSON files outside intended directories.
CVE-2026-40886 is a high-severity denial-of-service vulnerability in Argo Workflows caused by an unhandled Go runtime panic. A malformed Kubernetes annotation triggers an out-of-bounds array access in the controller's pod informer, leading to a permanent crash loop that halts all workflow orchestration operations.
The OpenTelemetry .NET SDK is vulnerable to a Denial of Service (DoS) flaw due to unbounded memory allocation during the deserialization of gRPC status details. An attacker controlling the telemetry endpoint or performing a Man-in-the-Middle attack can crash the instrumented application by supplying a crafted Protobuf payload.
The OpenTelemetry .NET SDK contains a denial of service vulnerability due to excessive memory allocation during the parsing of propagation headers. Vulnerable versions utilize eager allocation strategies, specifically `string.Split()`, to process Baggage, B3, and Jaeger headers. Unauthenticated remote attackers can exploit this by submitting crafted headers containing dense sequences of delimiters, forcing the application to allocate thousands of objects per request. This results in severe garbage collection pressure and potential OutOfMemoryException conditions. The vulnerability is fixed in version 1.15.3.
Or generate a custom report
Search for a CVE ID (e.g. CVE-2024-1234) to generate an AI-powered vulnerability analysis
Automated vulnerability intelligence. 1,600+ reports.