A ReDoS vulnerability exists in dd-trace's URL query string obfuscation regex, causing excessive CPU usage when processing crafted inputs. This can stall request processing and lead to denial of service in applications using affected HTTP tracing integrations. The issue affects dd-trace versions >=2.0.0 <5.131.1 and >=6.0.0 <6.20.1. A fixed version is available in 5.131.1 and 6.20.1. A workaround involves setting an updated regex pattern via DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP and restarting the application.
A stored Cross-Site Scripting (XSS) vulnerability exists in the media plugin of TinyMCE. This flaw allows attackers to inject malicious scripts via elements crafted through the data-mce-object attribute, which are executed before proper sanitization. The vulnerability affects TinyMCE versions 7.9.3 and 8.5.1 up to but not including 7.9.4 and 8.9.3 respectively. It has been patched in TinyMCE 7.9.4 and 8.9.3. No official workaround is available other than upgrading.
The Model Context Protocol (MCP) Python SDK versions 1.10.0 through 1.29.1 and 2.0.0 through 2.1.1 have a vulnerability in server-side bearer-token authentication. The SDK does not verify that a token's audience matches the intended server, allowing tokens issued for other services by the same authorization server to be accepted. This can lead to unauthorized access. Fixed in versions 1.30.0 and 2.2.0, the fix requires enabling a new setting to validate the token audience explicitly.
A vulnerability in the OpenTelemetry Python Jaeger propagator (opentelemetry-propagator-jaeger) prior to version 1.45.0 allows unbounded memory allocation when processing inbound 'uberctx-*' baggage headers. This can lead to increased CPU and memory usage per request, potentially causing denial-of-service conditions. The issue affects deployments that enable the Jaeger propagator and accept untrusted inbound propagation headers, especially where transport-level limits are absent or set higher than baggage limits. The vulnerability does not expose or modify telemetry data nor allow code execution. It is mitigated by upgrading to version 1.45.0 or later, which enforces limits on baggage extraction.
The Model Context Protocol (MCP) Python SDK versions 1.8.0 through 1.29.1 and 2.0.0 through 2.1.1 have a vulnerability where their HTTP client transports follow cross-origin HTTP redirects and send custom headers and request bodies to the redirected host. This behavior can expose sensitive headers such as API keys if the trusted endpoint redirects to an attacker-controlled domain. The SDK's OAuth client providers are similarly affected. The lone Authorization bearer header is not exposed due to existing HTTP library protections. The issue is fixed in MCP versions 1.30.0 and 2.2.0 by restricting redirects to the same origin only and failing otherwise.
The Model Context Protocol (MCP) Python SDK versions 1.10.0 through 1.29.1 and 2.0.0 through 2.1.1 contain a vulnerability where the client fetches server-chosen $ref URLs during tool result validation. This allows a malicious server to cause the client to make network or local file requests synchronously without timeout, potentially freezing the client session. The issue is fixed in versions 1.30.0 and 2.2.0.
A Cross-Site Scripting (XSS) vulnerability exists in CKEditor 5 engine versions from 29.0.0 up to but not including 47.7.4, and from 48.0.0 up to but not including 48.5.1. This issue occurs when the General HTML Support feature is enabled and configured to allow certain HTML content, enabling injection of malicious JavaScript code in a browser context isolated from the embedding application's origin. The vulnerability has a low severity score and has been patched in versions 47.7.4 and 48.5.1.
A Cross-Site Scripting (XSS) vulnerability exists in CKEditor 5 due to a prototype pollution issue in the es-toolkit library. This flaw allows unauthorized JavaScript execution when processing style attribute values. The vulnerability is fixed in CKEditor 5 versions 47.7.4 (LTS) and 48.5.1 and later.
A logic error in the legacy WebRTC input handling of the Neko server allows authenticated room members to bypass authorization checks and send mouse and keyboard inputs even when controls are locked. This issue only affects the legacy WebRTC input path when legacy mode and implicit hosting are enabled. The modern control API remains unaffected. The vulnerability is fixed in version 0.0.0-20260805142851-395ca1a6f62b.
Atlantis contains an OS command injection vulnerability in its handling of the Terraform workspace name specified in a pull request's atlantis.yaml file. The workspace name is passed into a shell command without proper escaping, allowing an attacker controlling a pull request to execute arbitrary shell commands as the Atlantis service account during the plan phase. This does not require custom workflows or apply permissions. The vulnerability affects versions from 0.4.0 up to but not including 0.47.1 and has been fixed in version 0.47.1.
FileBrowser contains a vulnerability where symbolic links (symlinks) inside a user's accessible directory can point outside the intended scope, allowing arbitrary file reads outside the served directory. This occurs because the application resolves symlinks without verifying that the resolved target remains within the user's authorized directory. Both authenticated users with download access and unauthenticated users accessing public shares can exploit this to read arbitrary files accessible to the server process. The issue affects version prior to 0.0.0-20260814233832-4126edeb07a0 and is fixed in that version.
CVE-2026-57195 is a high-severity vulnerability in Asterisk's Manager Interface (AMI) that allows an unauthenticated attacker to cause a denial of service via a NULL pointer dereference. This occurs when Digest Authentication is used over HTTP and the HTTP server, AMI, and AMI HTTP access are all enabled. The HTTP server binds to 127.0.0.1 by default, limiting exposure. The issue is fixed in Asterisk versions 20.20.1, 21.12.3, 22.10.1, 23.4.1, and Certified Asterisk 20.7-cert11 and 22.8-cert3.
SkyW4lker is a phishing kit active since June 2026 that targets Microsoft 365 authentication by exploiting OAuth 2.0 device-code flows to bypass MFA. It uses password-protected email attachments leading victims through CAPTCHA pages to malicious sites requesting device codes. The kit primarily targets US firms, especially in technology, manufacturing, and government sectors, and shares infrastructure with the Gabagool phishing kit.
Access of resource using incompatible type ('type confusion') in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
CVE-2026-116775 is a low-severity vulnerability in the Eugeny russh library affecting versions from 0.2.0 up to but not including 0.2.5. The issue arises from the PageantStream type trusting a peer-controlled length prefix without enforcing the fixed transport capacity limit, which can lead to excessive memory allocation or retention of partial frames. This can cause client memory exhaustion when bridging an SSH forwarded-agent channel to the raw stream. The vulnerability is fixed in version 0.2.5.
CVE-2026-116774 is a resource consumption vulnerability in the russh Rust SSH client and server library versions 0.60.0 through 0.64.9. The flaw allows an authenticated client or malicious server to cause asynchronous write operations to hang indefinitely by specifying a maximum_packet_size of zero, leading to stranded writes and accumulation of affected tasks, channels, and connections without error. This can result in denial of service due to uncontrolled resource consumption. The issue is fixed in version 0.65.0.
CVE-2026-116773 is a resource exhaustion vulnerability in the russh Rust SSH client and server library prior to version 0.65.0. The client improperly handles repeated private EXT_INFO messages (msg::EXT_INFO = 7) sent before authentication, appending extension names to a vector without limits or deduplication. This can lead to progressive memory exhaustion on the client side. The issue is fixed in russh version 0.65.0.
A vulnerability in dnspython's dns.name.from_wire_parser() function can cause excessive CPU usage when processing maliciously crafted DNS messages. This can degrade or deny service to applications that handle untrusted DNS wire format messages using dnspython. The issue is fixed in dnspython version 2.9.0. No workarounds are currently known.
CVE-2026-116696 is a resource allocation vulnerability in the russh Rust SSH client and server library prior to version 0.65.0. The issue occurs in the SSH agent protocol implementation where repeated SSH_AGENT_CONSTRAIN_CONFIRM records can be added without limits, causing unbounded memory growth. This memory growth persists for the lifetime of the process because keys without lifetime constraints do not expire. The vulnerability is fixed in russh version 0.65.0.
