Overview of incoming advisories.
2186 results found
Grav CMS versions before 2.0.16 contain an incomplete default denylist in the Twig sandbox configuration. This flaw allows attackers with page-edit permissions to access sensitive system configuration secrets via config.get() or config.toArray() functions in Twig templates. Sensitive values such as Redis passwords can be exposed when config_access is enabled. The vulnerability is classified as an information disclosure issue rooted in improper sandboxing controls. A fix was introduced in Grav version 2.0.16. The issue has been documented in NVD, GitHub Security Advisories, and VulnCheck. Organizations using Grav CMS with config_access enabled and Redis or other sensitive integrations are at elevated risk. Upgrading to version 2.0.16 or later is the recommended remediation.
View original advisory →CVE-2026-75574 affects the Grav Email plugin (getgrav/grav-plugin-email) prior to version 4.2.2. The vulnerability arises because page-editor-controlled Email action parameters are rendered as unsandboxed Twig templates. An authenticated remote attacker with only api.access and api.pages.write permissions can inject a malicious Twig expression into the header.form.process.email.body field of a page. By publishing the page and submitting the associated form, the attacker can trigger execution of arbitrary operating-system commands under the account running PHP. This represents a high-severity remote code execution vulnerability requiring only low-privilege authenticated access. Users are advised to upgrade to version 4.2.2 or later to remediate the issue.
View original advisory →CVE-2026-63076 is a NULL pointer dereference vulnerability (CWE-476) in OpenSSL's Certificate Management Protocol (CMP) implementation. The flaw exists in password-based MAC (PBM) protection verification, where the protectionAlg parameter type is never validated before being cast to a PBMParameter structure. A remote, unauthenticated attacker can send a crafted CMP message with a mismatched parameter type, triggering an invalid pointer dereference. This can crash CMP servers processing PBM-protected messages or CMP clients communicating with a malicious or MITM server, resulting in a Denial of Service. No shared secret knowledge is required to exploit this; the only prerequisite is that PBM verification is reachable. There is no memory disclosure, controlled memory write, or code execution path. FIPS modules are unaffected as CMP code resides outside the FIPS module boundary.
View original advisory →Nokogiri versions before 1.13.9 (CRuby implementation with packaged libraries) bundle libxml2 v2.9.14, which is vulnerable to two critical issues. CVE-2022-40304 involves data corruption and a double-free vulnerability triggered by entity reference cycles when entity content is allocated from a dict. CVE-2022-40303 involves integer overflows when parsing XML with the XML_PARSE_HUGE flag. Nokogiri 1.13.9 addresses these by upgrading the bundled libxml2 to v2.10.3. Processing crafted XML input in affected versions may lead to denial of service or memory corruption. A third CVE (CVE-2022-2309, a NULL pointer dereference) was referenced in the advisory but determined by maintainers to not affect Nokogiri users. The vulnerability affects applications relying on Nokogiri for XML parsing in Ruby environments. Patches are available via commits in the Nokogiri GitHub repository.
View original advisory →A heap out-of-bounds write vulnerability exists in OpenEXR versions before 3.2.11, 3.3.0 through 3.3.12, and 3.4.0 through 3.4.13. The flaw resides in the exrmultiview utility, which can write past a heap allocation when combining two crafted but individually valid scanline EXR files whose union dataWindow is misaligned with one view's channel subsampling. The root cause is incorrect storage allocation using a truncated union_width divided by xSampling, followed by reading through a Slice based on the misaligned union window. The vulnerability can be triggered via normal command-line usage of the exrmultiview tool with attacker-supplied inputs, making it exploitable beyond just API misuse. The motion picture industry widely uses the EXR format, increasing the potential attack surface. Fixed versions are 3.2.11, 3.3.13, and 3.4.14. Multiple commits and a GitHub Security Advisory have been issued to address the issue.
View original advisory →OpenEXR, the reference implementation for the EXR image format widely used in the motion picture industry, is affected by a heap out-of-bounds write vulnerability. The flaw impacts versions 3.3.0 through 3.3.12 and 3.4.0 through 3.4.13. The vulnerability is triggered when the exrmetrics tool reads a specially crafted deep scanline EXR file using pixel conversion options such as --pixelmode float or --bench. The root cause is a size mismatch: DeepSlice requests FLOAT output while the backing sample buffers are allocated using the smaller HALF element size, leading to memory corruption. An attacker could potentially exploit this by supplying a malicious EXR file to a vulnerable application. The issue has been patched in versions 3.3.13 and 3.4.14. Users are strongly advised to upgrade to the fixed versions immediately.
View original advisory →CVE-2026-75498 affects Webkul QloApps, a hotel booking and management platform. The vulnerability stems from insufficient validation of request parameters before database queries are executed. A remote attacker with administrative privileges can exploit this by sending a crafted SQL query through the 'bo_query' parameter in the 'Address.php' file. This constitutes a SQL injection vulnerability that could allow unauthorized data access or manipulation. The attack requires authentication with administrative-level privileges, reducing but not eliminating the risk. A fix has been committed in the QloApps GitHub repository at commit 123c97c. The issue is tracked under CVE-2026-75498 and referenced in a CISA advisory. Organizations using QloApps should apply the patch immediately to mitigate exposure.
View original advisory →CVE-2026-65092 affects NVIDIA OpenShell Sandbox for Linux, where an attacker can exploit a path traversal vulnerability to bypass L7 REST network policy controls. The vulnerability could allow unauthorized access to sensitive information and enable data tampering. The flaw resides in the network policy enforcement layer, specifically the Layer 7 REST policy mechanism. Successful exploitation does not appear to require authentication but likely requires network access. NVIDIA has published a security advisory via their product-security GitHub repository. The vulnerability has been assigned a high criticality rating. Affected users are advised to review NVIDIA's advisory for patches or mitigations.
View original advisory →Alluxio's S3 REST proxy fails to verify AWS Signature Version 4 signatures in its default configuration, creating a critical authentication bypass vulnerability. Unauthenticated attackers can extract usernames from unsigned Authorization headers and impersonate any user, including privileged service accounts. This allows attackers to perform unauthorized read, write, and delete operations on arbitrary data. The vulnerability affects Alluxio through version 2.9.5. The flaw stems from the proxy not enforcing signature verification, meaning any attacker with network access can spoof user identities without valid credentials. This poses a significant risk to data integrity and confidentiality in environments using Alluxio's S3-compatible interface.
View original advisory →CVE-2026-79788 affects Dradis Community Edition versions 5.1.0 through 5.2.0. The ProvidersController and AgentsController incorrectly gate their admin_required authorization check on the constant Dradis::Pro, which is never defined in the CE edition, meaning the check is never enforced. Any authenticated non-admin user can exploit this to create an AI provider pointing to an arbitrary HTTP/HTTPS address, including internal or link-local hosts like http://169.254.169.254. When an AI interaction is triggered, the server makes a request to the attacker-controlled URL, constituting a Server-Side Request Forgery (SSRF). For non-2xx HTTP responses, the target's response body is reflected back to the attacker via ActionCable/Turbo Stream error messages, making the SSRF readable and exploitable for internal network reconnaissance. The vulnerability stems from a broken authorization logic flaw combined with insufficient URL validation.
View original advisory →CVE-2026-79784 describes a critical arbitrary code execution vulnerability in the Vocos Python library, a neural vocoder used in AI/ML workflows. The vulnerability exists in the instantiate_class function within vocos/pretrained.py, which loads a class path from a configuration file without any allowlist or restriction on which class may be named. The function uses Python's __import__ and getattr to dynamically import and instantiate any callable, passing user-controlled arguments. The Vocos.from_pretrained method downloads a remote config.yaml from a Hugging Face repository specified by the caller and passes it directly to from_hparams, meaning loading a model from an untrusted repository results in execution of arbitrary code chosen by the repository owner. This is distinct from the torch.load deserialization risk, which is mitigated in newer PyTorch versions. The attack surface is significant for any user or pipeline that loads Vocos models from third-party or community Hugging Face repositories. No allowlist or sandboxing constrains the class path resolution, making this a straightforward remote code execution vector during model loading.
View original advisory →A stack-based buffer overflow vulnerability has been identified in BlueZ, the Linux Bluetooth protocol stack. An attacker within Bluetooth radio range can exploit this flaw by sending a specially crafted Extended Inquiry Response (EIR) packet during Bluetooth device discovery. The vulnerability triggers a buffer overflow condition that can crash the bluetoothd service, resulting in a Denial of Service (DoS). Beyond DoS, the flaw may also allow for arbitrary code execution on the affected system. The attack requires no authentication and only proximity within Bluetooth range. This affects Linux systems running BlueZ during active Bluetooth discovery operations. The vulnerability has been acknowledged by Red Hat and tracked in their security advisory and Bugzilla systems. A GitHub security advisory has also been published by the BlueZ project maintainers.
View original advisory →A SQL injection vulnerability has been identified in SililaWijesinghe's Food Ordering System, affecting the /search.php file. The vulnerability is triggered by manipulating the 'search_box' argument, allowing remote attackers to perform SQL injection attacks. The affected version spans up to commit ba314e897e3365600461e5ea59432e39ceaa0fa5. The product uses a rolling release model, making specific version identification difficult. The exploit has been publicly disclosed and is available for use. Remote exploitation is possible, increasing the risk of unauthorized database access or data exfiltration. The vendor was notified prior to public disclosure but did not respond. No patch or mitigation has been officially confirmed. The public availability of the exploit elevates the urgency for users of this system to take protective measures.
View original advisory →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 →