Overview of incoming advisories.
2186 results found
CVE-2026-24262 is a vulnerability discovered in the system firmware of NVIDIA DGX Spark. A privileged attacker can exploit an out-of-bounds write flaw in the firmware. Successful exploitation may result in arbitrary code execution, privilege escalation, 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 through their product-security GitHub repository. The vulnerability is tracked by both NVD and CVE.org. Given the range of potential impacts including code execution and privilege escalation, this is considered a high-severity issue. The DGX Spark is an AI computing platform, making this vulnerability particularly relevant to high-performance AI infrastructure environments.
View original advisory →The getgrav/grav-plugin-login Composer plugin before version 3.9.1 contains a timing side-channel vulnerability in its password reset and account activation token comparison logic. The affected code uses a non-constant-time === string comparison instead of the secure hash_equals() function in classes/Controller.php and login.php. Additionally, the token submission endpoint (taskReset) lacks rate limiting, compounding the risk. An attacker with knowledge of a valid username could theoretically send repeated token guesses and use timing differences to recover a valid reset or activation token. The vendor acknowledges the flaw but rates practical exploitability as low, and no end-to-end network exploit has been publicly demonstrated. The fix is available in version 3.9.1 of the plugin.
View original advisory →PraisonAI, a multi-agent teams system, contains a critical vulnerability in its Jobs API where the create_app function mounts the /api/v1/runs endpoint without any authentication. Prior to version 4.6.51, any reachable caller could exploit this to submit jobs, read results, cancel runs, or delete jobs using operator-level credentials. This effectively grants unauthorized users full control over job operations without requiring any credentials. The vulnerability poses significant risk as it allows unauthenticated access to sensitive job management functionality. The fix introduces PRAISONAI_JOBS_API_KEY middleware that enforces authentication via Authorization or X-API-Key headers. The issue has been patched in version 4.6.58 of PraisonAI.
View original advisory →NVIDIA NemoClaw for Linux contains a critical vulnerability in its status and logs plugin commands that allows OS command injection. An attacker exploiting this flaw could achieve arbitrary code execution on the affected system. The vulnerability also enables data tampering, information disclosure, and denial of service attacks. The issue resides specifically in plugin command handling within the NemoClaw application. NVIDIA has published a security advisory referencing this CVE. The vulnerability has been assigned a high criticality rating given the potential for full system compromise.
View original advisory →CVE-2026-55528 affects PraisonAI, a multi-agent teams system, in versions prior to praisonaiagents 1.6.58. The vulnerability exists because AgentServer exposes ServerConfig.auth_token but the _create_app method fails to enforce authentication checks on any route. This allows remote unauthenticated callers to subscribe, publish, and perform other sensitive actions without providing a valid bearer token or X-Auth-Token header, even when authentication is explicitly configured. The flaw represents a complete authentication bypass in the AgentServer component. The issue has been resolved in praisonaiagents version 1.6.58. Users are strongly advised to upgrade immediately to mitigate the risk of unauthorized access to their multi-agent systems.
View original advisory →CVE-2026-16231 affects hbs, an Express view engine wrapping Handlebars, versions 2.1.0 through 4.2.1. The vulnerability exists in the registerAsyncHelper API, which bypasses Handlebars' automatic HTML escaping mechanism. During the first render pass, async helpers return an opaque placeholder that gets escaped, but the actual return value is substituted without escaping after rendering. This flaw affects cached, uncached, and layout render paths. Attackers can inject arbitrary HTML and JavaScript into server-rendered pages if attacker-controlled data is passed into async helper callbacks. The vulnerability enables both stored and reflected cross-site scripting (XSS) attacks. The issue is fixed in version 4.3.0, which properly HTML-escapes async helper output. Applications requiring raw HTML output can use hbs.SafeString to explicitly opt in. Users are strongly advised to upgrade to version 4.3.0 immediately.
View original advisory →NLTK versions before 3.10.3 contain a critical remote code execution vulnerability in their allowlisted pickle loaders. The flaw exists because the loaders trust entire module namespaces rather than restricting access to specific safe callables. Attackers can craft malicious pickle payloads that invoke dangerous functions such as ReppTokenizer._execute and numpy.f2py.crackfortran.myeval via the pickle REDUCE opcode. Exploitation occurs during the loading of model or tokenizer artifacts, making supply chain and model-sharing scenarios particularly risky. The vulnerability allows arbitrary command execution on affected systems. Users are urged to upgrade to NLTK 3.10.3 or later to remediate the issue. Details are available via NVD, the NLTK GitHub security advisory, and VulnCheck.
View original advisory →The Total Donations plugin for WordPress contains a critical privilege escalation vulnerability affecting all versions up to and including 2.0.5. Unauthenticated attackers can exploit this flaw to elevate their privileges to administrator level without any prior authentication. The vulnerability has been assigned CVE-2026-78570 and is documented by both NVD/NIST and security researchers at Patchstack and Wordfence. No patch details are explicitly mentioned, but the affected version ceiling is 2.0.5. The ability for unauthenticated users to gain admin access makes this a high-severity issue for any WordPress site running the affected plugin. Site administrators should immediately assess their exposure and apply any available updates or mitigations.
View original advisory →CVE-2026-55540 affects PraisonAI, a multi-agent teams system, in versions prior to 4.6.51. The vulnerability exists in the is_path_within_directory() function, which uses os.path.abspath() instead of os.path.realpath() when enforcing workspace boundaries. This flaw allows a symlink placed inside the workspace to point to locations outside the workspace while still passing the boundary check. As a result, tools such as read_file can be abused to access arbitrary files on the filesystem outside the configured workspace. The vulnerability represents a path traversal/sandbox escape issue that could lead to unauthorized file disclosure. It is particularly relevant in multi-agent AI system contexts where workspace isolation is a security boundary. The issue was fixed in version 4.6.58 of PraisonAI. A patch commit and security advisory are publicly available on GitHub.
View original advisory →Ech0 versions before 4.7.3 contain a server-side request forgery (SSRF) vulnerability in the fetchPeerConnectInfo function. The function uses unvalidated HTTP requests instead of safe request methods with proper URL validation. Authenticated attackers can supply arbitrary URLs to exploit this vulnerability. The attack vector involves triggering connection health checks or peer connection operations. Exploitation allows access to internal services and cloud metadata endpoints. The vulnerability requires authentication, limiting the attack surface somewhat. Cloud environments are particularly at risk due to metadata endpoint exposure. A fix is available in version 4.7.3 and later. The issue has been documented in both GitHub Security Advisories and VulnCheck. Organizations using Ech0 in cloud or internal network environments should prioritize upgrading immediately.
View original advisory →CVE-2026-16286 describes an unrestricted file upload vulnerability in TRtek Technological Products' Software Repository Management application. The flaw allows attackers to upload files with dangerous types, enabling the deployment of a web shell to the affected web server. Successful exploitation grants an attacker remote code execution capabilities on the server. All versions of Software Repository Management prior to commit 2fb4acee are affected. The vulnerability is classified under CWE for unrestricted upload of files with dangerous types. The advisory was published by the Turkish cybersecurity authority (siberguvenlik.gov.tr). No workarounds are noted; patching to the fixed commit is the recommended remediation. The issue carries a high criticality rating due to the direct risk of server compromise.
View original advisory →Adobe Campaign Classic (ACC) is affected by a critical OS Command Injection vulnerability (CVE-2026-76197) classified as Improper Neutralization of Special Elements used in an OS Command. The vulnerability allows arbitrary code execution in the context of the current user. No user interaction is required for exploitation, making it particularly dangerous. The scope of the vulnerability is changed, indicating impact can extend beyond the vulnerable component. Adobe has published a security advisory (APSB26-134) to address this issue. The vulnerability carries a high criticality rating and poses significant risk to organizations using Adobe Campaign Classic.
View original advisory →CVE-2026-75497 describes a SQL injection vulnerability in Webkul QloApps, a hotel booking and management platform. The vulnerability exists because the application fails to validate request parameters before passing them to a database query. A remote attacker with administrative privileges can exploit this by sending a crafted SQL payload to the 'bo_query' parameter in the 'CustomerMessage.php' file. Successful exploitation could allow unauthorized access to or manipulation of the underlying database. The vulnerability has been patched in commit 123c97c, available via a GitHub pull request. References include the NVD advisory, CVE record, and a CISA CSAF advisory file. The attack requires authentication with administrative-level access, limiting the attack surface but not eliminating risk in compromised or insider-threat scenarios.
View original advisory →CVE-2026-80049 describes a critical authorization bypass vulnerability in Airbyte Platform through version 2.0.0. The flaw exists because the platform resolves workspace authorization decisions based on a caller-supplied field rather than the actual resource's owning workspace. AuthorizationServerHandler extracts identifiers from raw JSON request bodies into X-Airbyte-* headers, and AuthenticationHeaderResolver.resolveWorkspace prioritizes the caller-supplied X-Airbyte-Workspace-Id over resource-derived headers. Endpoints that only expect a resource identifier in the request body can be reached with an injected workspaceId field, causing permission checks to run against the attacker-nominated workspace. Since no post-authorization check compares the resource's owning workspace with the authorized workspace, any authenticated workspace member can read source and destination configurations, trigger or cancel syncs, and delete connections, sources, and destinations belonging to other workspaces. The exploit requires only valid membership in any workspace, making it broadly exploitable across multi-tenant deployments.
View original advisory →NLTK versions up to and including 3.9.4 contain an unsafe pickle deserialization vulnerability in the TransitionParser.parse() method located in nltk/parse/transitionparser.py. The method invokes pickle_load() with the default parameter restricted=False, routing deserialization through WarningUnpickler, which does not override find_class() and thus permits arbitrary class resolution. An attacker can craft a malicious model file containing pickle gadget chains that execute arbitrary Python code with the privileges of the application user upon loading. While NLTK provides a RestrictedUnpickler class designed for safe deserialization, it is not utilized in production code paths, leaving users exposed. The vulnerability enables remote or local code execution depending on how model files are sourced and loaded. The issue has been addressed and fixed in NLTK version 3.10.0. Users are strongly advised to upgrade immediately to mitigate the risk of arbitrary code execution.
View original advisory →CVE-2026-55099 affects the Python icalendar library versions 7.1.0 through 7.1.2, where the Component equality method performs O(2^n) recursive comparisons on nested subcomponents. An attacker can craft a sub-kilobyte .ics file with deeply nested BEGIN:VEVENT blocks to trigger exponential CPU consumption. The vulnerability is exploited when applications perform equality, inequality, membership, deduplication, or normalization comparisons on parsed calendar data. Affected endpoints include calendar sync, import, invite processing, and any comparison paths. Parsing alone does not trigger the issue, but equal nested subtrees cause worst-case behavior. A few hundred bytes are sufficient to pin a CPU core for minutes or indefinitely, resulting in denial of service. The issue has been patched in icalendar version 7.1.3.
View original advisory →CVE-2026-65093 is a high-severity vulnerability in NVIDIA OpenShell for Linux that allows an attacker to perform a sandbox escape. Successful exploitation can lead to arbitrary code execution, escalation of privileges, data tampering, and information disclosure. The vulnerability was published via the NVD (National Vulnerability Database) and tracked by NVIDIA's product security team. No specific exploit details or active exploitation in the wild are mentioned in the article. The vulnerability affects Linux-based deployments of NVIDIA OpenShell. Given the potential for privilege escalation and code execution, this is classified as a high-criticality issue. Users and administrators running NVIDIA OpenShell on Linux systems should monitor NVIDIA's security advisories for patches and mitigations.
View original advisory →A vulnerability was identified in Fdawgs node-poppler versions up to 9.1.2 and 10.0.1 affecting multiple PDF processing functions in src/index.js. The flaw resides in the Argument Injection Handler component, where manipulation of the file_path argument leads to argument injection. Affected functions include pdfInfo, pdfToText, pdfToCairo, pdfToPpm, pdfImages, pdfToHtml, pdfToPs, pdfFonts, pdfDetach, pdfAttach, pdfSeparate, and pdfUnite. The vulnerability can be exploited remotely, increasing its risk surface. A patch has been identified with commit hash db6e3f79d3beb20601be7e59669c39811ae3c330 on the project's GitHub repository. Users are strongly advised to apply the patch immediately to mitigate the risk of exploitation.
View original advisory →CVE-2026-56710 affects Grav Login plugin versions before 1.0.16, where the onApiUserListRowAction unlock handler fails to validate the privilege level of the target account. An attacker holding api.users.write permission can exploit this flaw to clear login lockout counters on admin.super accounts. This effectively strips brute-force protection from the highest-privilege accounts in a Grav CMS installation without requiring equivalent super-admin permissions. The vulnerability represents a privilege escalation/authorization bypass issue that could facilitate subsequent credential-based attacks against administrator accounts. It has been assigned a high criticality rating. Fixes are available in version 1.0.16 of the Grav Login plugin, and advisories have been published on GitHub and VulnCheck.
View original advisory →CVE-2026-63072 is a vulnerability in OpenSSL's CMS decryption logic where the key-unwrap output buffer is sized based on the reported unwrapped key size, but the AES-WRAP-PAD primitive can write 8 bytes beyond the allocation. An attacker can craft a CMS message by changing a single OID byte to trigger a deterministic 8-byte out-of-bounds heap write when the victim calls CMS_decrypt(). This results in heap corruption, typically causing a Denial of Service. The vulnerability is classified as CWE-787 (Out-of-bounds Write), requires no special configuration, and is reachable via the public API. No FIPS modules are affected as the CMS code resides outside the FIPS module boundary. The fix sizes the unwrap output buffer for the worst-case scenario to prevent out-of-bounds writes. Multiple OpenSSL commits have been issued to address the issue.
View original advisory →