Overview of incoming advisories.
1553 results found
A missing authentication vulnerability exists in PraisonAI versions 4.6.34 through 4.6.57, a multi-agent teams system. The application accepts an --api-key parameter via the 'praisonai serve agents' command, but the internal _create_agents_app() function fails to enforce authentication on POST /agents and POST /agents/{agent_name} endpoints. This allows any network caller to invoke configured agents without supplying credentials, even when an API key has been configured. The vulnerability essentially renders the API key mechanism ineffective, exposing agent functionality to unauthorized access. The flaw was fixed in version 4.6.58 via a committed patch. Users are advised to upgrade immediately to the patched release to prevent unauthorized agent invocation.
View original advisory →Nokogiri versions prior to 1.18.4 bundle a vulnerable version of libxslt (prior to 1.1.43) that contains two use-after-free vulnerabilities. CVE-2025-24855 involves a use-after-free of the XPath context node due to xsltEvalXPathStringNs leaking xpathCtxt->node. CVE-2024-55549 involves a use-after-free related to excluded result prefixes and namespaces. Processing specially crafted XSLT input can trigger memory corruption exploiting these flaws. The vulnerabilities are inherited through Nokogiri's bundled dependency on libxslt, representing a supply chain risk. Nokogiri 1.18.4 resolves both issues by upgrading the bundled libxslt to version 1.1.43. Users of Nokogiri are advised to upgrade to version 1.18.4 or later immediately.
View original advisory →NLTK versions before 3.10.3 contain a vulnerability in the dependencygraph.dot2img and AlignedSent._repr_svg_ functions that fail to use validated absolute paths when invoking the Graphviz dot binary. This allows attackers to execute arbitrary code by placing a malicious dot binary in the search path or current working directory. On Windows systems, attackers can exploit bare-name binary resolution via the current working directory, while on Unix-like systems they can abuse relative PATH entries. The vulnerability enables a classic binary hijacking/path traversal attack vector. Successful exploitation results in full arbitrary code execution with the privileges of the NLTK process. Users are advised to upgrade to NLTK version 3.10.3 or later to remediate the issue.
View original advisory →A high-severity vulnerability (CVE-2026-65083) has been identified in NVIDIA OpenShell for Linux, specifically within its sandbox provisioning API. The flaw allows an attacker to cause an incomplete list of disallowed inputs, effectively bypassing sandbox restrictions. Successful exploitation of this vulnerability can lead to multiple severe impacts including arbitrary code execution, escalation of privileges, information disclosure, data tampering, and denial of service. The vulnerability is classified with a high criticality rating. NVIDIA has published a security advisory through their product-security GitHub repository. The issue affects the Linux version of NVIDIA OpenShell and is tracked by both the NVD and CVE databases. Users and administrators running affected versions are advised to review NVIDIA's advisory for remediation guidance.
View original advisory →CVE-2026-75037 describes an authentication bypass vulnerability in LACT (Linux AMD GPU Control Tool) affecting versions through 0.10.0. The flaw resides in the Polkit authentication mechanism, which relies on UnixProcessSubject and Peer PID for identity verification. This approach is susceptible to PID reuse attacks, allowing an attacker to bypass authentication checks. The vulnerability runs on Linux systems where LACT is installed and used for GPU management. A fix has been committed via commit d0478fe42c2219454e272f96b1cbd29ab37ee566 in the upstream GitHub repository. The issue was also tracked in the SUSE Bugzilla system under bug ID 1276480. Users are advised to update to a patched version beyond 0.10.0 to mitigate this risk.
View original advisory →Nokogiri versions before 1.15.6 and 1.16.x before 1.16.2 (CRuby with packaged libxml2) are affected by a use-after-free vulnerability in libxml2 tracked as CVE-2024-25062. The flaw exists in the xmlTextReader module, which underlies Nokogiri::XML::Reader. Exploitation requires using the XML Reader interface with DTD validation and XInclude expansion enabled, where processing a crafted XML document can trigger an xmlValidatePopElement use-after-free condition. The vulnerability is resolved in Nokogiri 1.15.6 and 1.16.2 by upgrading the packaged libxml2 to versions 2.11.7 and 2.12.5 respectively. JRuby-based installations and those using the system-installed libxml2 are not affected by this issue.
View original advisory →CVE-2026-45019 affects Chainlit, a Python framework for conversational AI, in versions 2.4.0rc0 through 2.12.0. When the MCP feature is enabled, the POST /mcp endpoint is exposed without authentication. Attackers can supply arbitrary URLs and headers to SSE and streamable-HTTP transports, causing the Chainlit server to make blind outbound requests to internal or external services. This enables Server-Side Request Forgery (SSRF) attacks, including probing cloud metadata endpoints, internal port scanning, and issuing state-changing authenticated requests using attacker-controlled Authorization and Cookie headers. The SSE sink has been present since version 2.4.0rc0, with header forwarding and streamable-HTTP support added in 2.6.4. The vulnerability is caused by missing scheme validation, private-address filtering, and allowlist enforcement in backend/chainlit/types.py and server.py. The issue is fully remediated in Chainlit version 2.12.0.
View original advisory →A Server-Side Request Forgery (SSRF) vulnerability exists in PraisonAI versions prior to 4.6.58. The flaw resides in JobSubmitRequest.validate_webhook_url(), which incorrectly accepts webhook URLs when DNS resolution fails with a socket.gaierror exception due to a silent exception handler (except socket.gaierror: pass). A subsequent fresh DNS lookup in JobExecutor._send_webhook() can be exploited via DNS rebinding, allowing an attacker to redirect requests to internal services. This constitutes a classic Time-of-Check to Time-of-Use (TOCTOU) vulnerability in DNS validation. The issue enables attackers to potentially access internal infrastructure not intended to be publicly reachable. The vulnerability has been patched in PraisonAI version 4.6.58. A GitHub security advisory (GHSA-rg5q-pp8p-f7jm) has been published alongside the fix. Users are strongly advised to upgrade to the patched version immediately.
View original advisory →CVE-2026-24170 affects NVIDIA UFM Enterprise, specifically its web interface authorization component. An authenticated user can exploit this vulnerability by sending specially crafted HTTP requests, triggering improper authentication behavior. Successful exploitation may lead to arbitrary code execution and escalation of privileges on the affected system. The vulnerability requires an authenticated session to exploit, slightly limiting the attack surface but not eliminating the risk. NVIDIA has published an advisory through their product-security GitHub repository. The flaw is catalogued by both NVD and CVE.org. Given the potential for code execution and privilege escalation, the vulnerability is rated high criticality. Organizations using NVIDIA UFM Enterprise should review the vendor advisory and apply patches promptly.
View original advisory →Grav CMS versions before 2.0.16 contain a path traversal vulnerability in the MediaUploadTrait::deleteFile() method. Authenticated users with media management permissions can exploit this flaw to delete arbitrary files on the server by supplying filenames containing directory traversal sequences (../). The vulnerability exists because the method only validates the basename portion of the filename, while leaving the directory path portion unvalidated. These unvalidated paths containing ../ sequences are then passed directly to PHP's unlink() function, allowing deletion of files outside the intended media storage directory. The flaw is fixed in Grav version 2.0.16. This is a significant security risk as it can lead to deletion of critical system or application files, potentially causing denial of service or aiding further compromise.
View original advisory →CVE-2026-59981 affects the OpenEXR library, the reference implementation for the EXR image format used in the motion picture industry. The vulnerability exists in the OpenEXRUtil library's SampleCountChannel::row() API, which returns an out-of-bounds pointer when processing deep images with a non-zero dataWindow origin. The conflict between 0-based row indexing and absolute pixel coordinate offsets causes row(0) to point far outside the allocated sample-count buffer when the data window has a large negative vertical origin. An attacker can craft a malicious deep EXR file that, when opened by a vulnerable application, triggers an out-of-bounds read. This can result in process crashes or, under a controlled heap layout, exposure of adjacent heap memory contents. Affected versions include through 3.2.10, 3.3.0-3.3.12, and 3.4.0-3.4.13. Fixes are available in versions 3.2.11, 3.3.13, and 3.4.14.
View original advisory →CVE-2026-65096 is a high-severity vulnerability in NVIDIA NemoClaw for Linux affecting the Telegram bridge component. The flaw allows an attacker to perform OS command injection, potentially leading to arbitrary code execution on the affected system. Successful exploitation could also result in privilege escalation, information disclosure, and data tampering. The vulnerability is specific to the Linux version of the product. NVIDIA has published a security advisory referencing this CVE. The issue is tracked in NVIDIA's product security repository under the 2026/5872 path. No active exploitation details are currently mentioned, but the potential impact is significant given the range of consequences described.
View original advisory →CVE-2026-55546 affects QWED-MCP, a deterministic verification gateway for MCP, in versions prior to 0.2.1. The vulnerability exists in the verify_math_expression() function within math_engine.py, which passes attacker-controlled strings directly to SymPy's parse_expr() without adequate sanitization. Because parse_expr() internally calls Python's eval() with built-ins available, an attacker can leverage Python's import functionality to execute arbitrary OS commands. Potential impacts include arbitrary code execution, data exfiltration, secret theft, and access to internal services. Exploitation requires a downstream integration that passes untrusted user input to the library API, as the default MCP tool registry does not expose the vulnerable function. The issue has been patched in version 0.2.1 of QWED-MCP.
View original advisory →Ech0 versions 4.3.4 and earlier contain a vulnerability where scoped access token (least-privilege) restrictions are not reliably enforced on several privileged admin API routes. Multiple endpoints such as /api/inbox, /api/panel/comments, and /api/backup/export omit scope checks and authorize requests based solely on the user's admin role. The backup export handler additionally discards token scope metadata entirely. An attacker with a deliberately limited low-scope admin access token can access broader privileged functionality than intended, including reading the inbox and exporting a full database backup as a ZIP archive. This represents a broken access control / authorization bypass issue. The vulnerability has been fixed in version 4.4.3. The issue is documented in the NVD, GitHub Security Advisories, and VulnCheck advisories.
View original advisory →Ech0 versions before 4.5.1 contain an authorization bypass vulnerability in the RequireScopes middleware. Session tokens skip scope validation, allowing authenticated non-admin users to access admin-only endpoints. Exploiting this flaw, attackers can read system logs, visitor statistics, and user email addresses. They can also subscribe to live WebSocket log streams by sending valid session tokens to unprotected endpoints. The vulnerability requires the attacker to already have a valid session token (i.e., be a logged-in user). No privilege escalation of credentials is needed beyond a standard user account. A fix was introduced in version 4.5.1. The issue is tracked as CVE-2026-79665 and has been assigned a high criticality rating.
View original advisory →A vulnerability in OpenEXR, the reference implementation for the EXR image format used in the motion picture industry, allows crafted EXR files with a nonzero dataWindow.min to cause TypedFlatImageChannel::row() to return an invalid heap pointer. This results in out-of-bounds or use-after-free writes when an application writes rows through FlatHalfChannel::row(). Affected versions include those before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13. Tools, converters, render pipeline components, and image-processing services that accept untrusted EXR files are at risk. The vulnerability can be triggered by processing maliciously crafted EXR files from untrusted sources. Fixes have been released in versions 3.2.11, 3.3.13, and 3.4.14. Users are advised to upgrade to the patched versions immediately to mitigate the risk of memory corruption attacks.
View original advisory →A vulnerability has been identified in the system firmware of NVIDIA DGX Spark, tracked as CVE-2026-47626. The flaw allows a privileged attacker to trigger an out-of-bounds write condition within the firmware. Successful exploitation can result in a range of severe impacts including arbitrary code execution, escalation of privileges, denial of service, information disclosure, and data tampering. The vulnerability requires privileged access to exploit, somewhat limiting the attack surface. NVIDIA has published a security advisory via their product-security GitHub repository. The vulnerability is catalogued by both NVD (National Vulnerability Database) and the CVE Program. Given the potential for code execution and privilege escalation at the firmware level, the severity is considered high. Organizations using NVIDIA DGX Spark hardware should monitor for firmware patches and apply mitigations as soon as available.
View original advisory →Grav Flex Objects plugin versions 1.4.0 through 1.4.7 contain an authorization bypass vulnerability in the flex-objects shortcode handler. Users with page-edit access can render any registered Flex collection without proper permission checks. Attackers can embed the shortcode in published pages to expose sensitive directory contents, including user account information. The vulnerability bypasses the authorize ACL enforced in the admin panel. This represents a privilege escalation risk where lower-privileged users can access data beyond their authorization scope. The flaw is specifically tied to the shortcode rendering path, which lacks the same access controls applied elsewhere. Organizations running affected versions of the plugin on Grav CMS installations should prioritize patching. References include the NVD entry, a GitHub security advisory, and a VulnCheck advisory.
View original advisory →CVE-2026-56705 affects Adminer versions before 5.4.3, which fails to sanitize the server field before constructing a PDO DSN string. This allows unauthenticated attackers to inject ODBC parameters using semicolons. By injecting TraceFile and TraceOn parameters, attackers can write arbitrary PHP code to the web root. When the resulting trace file is subsequently accessed via the web server, remote code execution is achieved. The vulnerability requires no authentication, making it particularly dangerous for publicly exposed Adminer instances. The fix is available in Adminer 5.4.3. The issue has been documented by both the GitHub security advisory and VulnCheck.
View original advisory →The Total Donations plugin for WordPress contains a SQL Injection vulnerability affecting all versions up to and including 2.0.5. The flaw stems from insufficient escaping of user-supplied parameters and inadequate preparation of existing SQL queries. Unauthenticated attackers can exploit this vulnerability by appending additional SQL queries to extract sensitive information from the database. No authentication is required to exploit this vulnerability, making it particularly dangerous for any site running the affected plugin versions. Users are advised to update or remove the plugin to mitigate the risk of data exfiltration.
View original advisory →