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.
Crass, a Ruby CSS parser, has a vulnerability prior to version 1.0.8 where it incorrectly treats a closing parenthesis after an escaped backslash as escaped when parsing bad URLs. This causes Crass to retain CSS declarations inside a bad URL token that browsers would normally treat as live CSS. This can allow CSS-based UI redress, external resource loading, or data exfiltration when sanitizing untrusted CSS, but it does not enable script execution in modern browsers. The issue is fixed in version 1.0.8.
A resource allocation vulnerability exists in open-telemetry's opentelemetry-python prior to version 1.45.0. The JaegerPropagator.extract() function processes inbound uberctx-* baggage values without limits on entry count or byte size. This can lead to excessive CPU usage and memory allocations when untrusted input contains many or large values, potentially causing denial of service. The issue is fixed in version 1.45.0.
CVE-2026-116693 is a high-severity vulnerability in DataDog's dd-trace-js Node.js APM client. Versions from 2.0.0 up to but not including 5.131.1, and from 6.0.0 up to but not including 6.20.1, contain an inefficient regular expression in the default DD_TRACE_OBFUSCATION_QUERY_STRING_REGEXP. This flaw allows crafted URL query strings to cause excessive CPU consumption and stall request processing, potentially making the instrumented application unavailable. The issue is fixed in versions 5.131.1 and 6.20.1.
MLflow versions from 3.12.0rc0 up to but not including 3.17.0 contain a critical code injection vulnerability. This flaw allows an attacker to execute arbitrary Python code by placing a malicious module within a writable allowed package and invoking it via MLflow's artifact endpoints. The vulnerability arises because the deserialization process accepts subclasses of allowed modules rather than strictly enforcing exact module matches. Authentication-disabled deployments are fully exposed, while basic-auth deployments require elevated privileges. The issue is resolved in version 3.17.0.
The dsh-vm-tester npm package versions 0.1.2, 0.1.3, and 0.1.4 contain malicious code that can fully compromise any computer on which it is installed or running. This compromise includes potential unauthorized access to all secrets and keys stored on the affected system. Removal of the package alone does not guarantee elimination of all malicious components, as the attacker may have established persistent control.
MLflow versions from 2.19.0 up to but not including 3.17.0 contain a vulnerability where the mlflow.crewai.autolog() function records CrewAI Agent objects without properly sanitizing nested credential values. This causes provider API keys to be included in plaintext within trace data sent to MLflow's trace backend or OTLP destinations. The issue is resolved in version 3.17.0.
fpdf2 contains a vulnerability where nested SVG <use> references cause exponential growth in memory and CPU usage during image processing. This occurs because fpdf2 deep-copies referenced SVG objects recursively, leading to resource exhaustion. A crafted SVG under 1 KB can cause the process to consume excessive memory and CPU, resulting in a MemoryError and denial of service in PDF generation workflows.
The pdfly library (fpdf2) implicitly dereferences image resource references when rendering content, which can lead to outbound HTTP(S) requests or local file access attempts if untrusted input is processed. This affects applications that render untrusted HTML, SVG, or image paths without sanitization. The issue can enable Server-Side Request Forgery (SSRF) and limited local file access depending on the image parsing success. A fix is available in version 0.5.1_25.
Sunhillo SureLine versions prior to 9.1.5 have an authentication bypass vulnerability due to reliance on session cookies that lack validation and integrity checking. An unauthenticated remote attacker can forge a session cookie containing only a cleartext username, such as default accounts like Admin or sftp_user, to impersonate any user with an active web session. This flaw allows attackers to bypass login checks and potentially execute root commands. The vulnerability is fixed in version 9.1.5.
Sunhillo SureLine versions from 8.6.0 up to but not including 9.1.5 contain an OS command injection vulnerability in the networkDiag.cgi endpoint. This flaw allows an authenticated remote attacker with any web account to execute arbitrary commands as root by injecting shell metacharacters into the ipAddr or dnsAddr parameters. The vulnerability arises because attackers can bypass a prior character denylist by using URL-encoded newline (%0a) or ampersand (%26) sequences, which act as command separators after decoding in diagnostic modes such as ping, nslookup, or traceroute. The issue is fixed in version 9.1.5.
Sunhillo SureLine versions prior to 9.1.5 contain a path traversal vulnerability in the radarUpdater.cgi endpoint. This flaw allows unauthenticated remote attackers to read arbitrary files with root privileges by exploiting insufficient sanitization of the filename parameter and lack of authentication checks. Sensitive files such as /etc/shadow, the web user database, root SSH private key, and TLS private key can be accessed, potentially leading to full system compromise. The vulnerability is fixed in version 9.1.5.
MLflow versions from 3.10.0 up to but not including 3.17.0 contain a path traversal vulnerability in the _create_model_version() function. This flaw allows remote attackers to read arbitrary files on the MLflow server by storing a server-local path as the model version artifact location and accessing it via the model-versions API. Unauthenticated servers are fully exposed, while basic-auth servers expose this to authenticated users who can create registered models. The issue is resolved in version 3.17.0.
A vulnerability in the follow-redirects Node.js library versions 1.16.0 through 1.16.1 allows sensitive headers to be improperly forwarded during cross-origin redirects. This occurs because the sensitiveHeaders option is checked using value instanceof Array, which fails for arrays created in different JavaScript realms, causing the sensitive headers list to be replaced with an empty array. As a result, custom credential headers can be sent to attacker-controlled redirect destinations. The issue is fixed in version 1.16.2.
CKEditor 5 versions from 45.0.0 up to but not including 47.7.4, and from 48.0.0 up to but not including 48.5.1, contain a cross-site scripting (XSS) vulnerability due to prototype pollution in a vulnerable es-toolkit version used by the editor engine. This flaw allows crafted editor content to execute unauthorized JavaScript in the browser. The issue is resolved in versions 47.7.4 and 48.5.1.
OAuthLib versions from 4.5.1_3 up to but not including 4.5.1_14 contain a vulnerability in the device workflow implementation of the OAuth 2.0 device authorization grant (RFC 8628). The token endpoint does not properly validate the device_code parameter, allowing an attacker who knows a valid client ID for a public client to obtain a bearer token without a valid device_code. This flaw arises because the DeviceCodeGrant.validate_token_request method lacks proper device_code validation and mishandles public clients. A fix is available in version 4.5.1_14.
CKEditor 5 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, contain a cross-site scripting (XSS) vulnerability when General HTML Support is enabled and configured to allow object content. This vulnerability allows specially crafted markup to execute attacker-controlled JavaScript in a browser context isolated from the embedding application's origin. The issue is fixed in versions 47.7.4 and 48.5.1.