A vulnerability in LXD allows a specially crafted container image to read and write arbitrary files on the host system by exploiting a symlink named 'templates' in the image. This can lead to arbitrary command execution on the host. The flaw arises because the tar extraction process does not reject a top-level 'templates' symlink, enabling access to host directories such as /etc/cron.d. A proof of concept demonstrates creating a cron job on the host via this method. The vulnerability is critical with a CVSS score of 9.9 and has been fixed in version 0.0.0-20260203144152-d1c8ba15d160.
LXD contains a vulnerability where the 'exec-output' directory can be a symlink, allowing files to be written to arbitrary locations on the host. This can be exploited to create files such as cron jobs, enabling arbitrary command execution on the host system. The issue arises because top-level symlinks in unpacked images are preserved, and the code follows the symlink when writing output files. A proof-of-concept demonstrates placing a malicious file in /etc/cron.d to achieve code execution.
A heap-based buffer overflow in the TDS prelogin parser in the Babelfish for PostgreSQL extension versions 1.0-1.5, 2.1-2.15, 3.1-3.12, 4.0-4.8, 5.1-5.4 and in Amazon Aurora PostgreSQL with Babelfish might allow remote attackers to execute arbitrary OS commands as the database process user via a specially crafted malformed TDS prelogin packet to the TDS port. This record consolidates a related NULL-pointer-dereference finding in the same prelogin parser.
To remediate this issue, we recommend users upgrade to Babelfish for PostgreSQL extension versions 4.10, 5.6, 6.1 or later. As a workaround, restrict network access to the TDS port (default 1433). Customers using Amazon Aurora PostgreSQL with Babelfish should upgrade their cluster to Aurora PostgreSQL 13.9.16 (1.5.5), 13.23.3 (1.17.2), 14.6.16 (2.3.5), 14.17.8 (2.12.4), 14.18.6 (2.13.3), 14.19.5 (2.14.2), 14.20.5 (2.15.2), 14.22.3 (2.16.1), 14.23.1 (2.17.0), 15.10.8 (3.8.4), 15.12.8 (3.9.4), 15.13.6 (3.10.3), 15.14.5 (3.11.2), 15.15.5 (3.12.2), 15.17.3 (3.13.1), 15.18.1 (3.14.0), 16.8.8 (4.5.5), 16.9.6 (4.6.3), 16.10.5 (4.7.2), 16.11.5 (4.8.2), 16.13.3 (4.9.1), 16.14.1 (4.10.0), 17.4.8 (5.1.4), 17.5.6 (5.2.3), 17.6.5 (5.3.2), 17.7.5 (5.4.2), 17.9.3 (5.5.1), 17.10.1 (5.6.0), 18.3.4 (6.0.2), 18.4.1 (6.1.0) or later, and apply any pending maintenance to ensure they are on the latest patch.
Red Hat OpenShift Container Platform 4.22.22 includes multiple security fixes addressing critical vulnerabilities in components such as the kernel, libcurl, qemu-kvm, OpenSSL, BIND, cryptography libraries, and others. These fixes resolve issues including privilege escalation, denial of service, information disclosure, use-after-free, memory corruption, and arbitrary code execution. Users of OpenShift Container Platform 4.22 are advised to upgrade to this release to mitigate these risks.
CVE-2026-71495 is a critical server-side request forgery (SSRF) vulnerability in open-wanderer wanderer versions prior to 0.20.0. When the configuration PUBLIC_PRIVATE_INSTANCE is not set to true, unauthenticated attackers can exploit the POST /api/v1/trail/download endpoint by supplying a malicious JSON url field. This causes the server to fetch arbitrary internal network resources, potentially exposing sensitive data or enabling denial of service. The vulnerability is fixed in version 0.20.0.
OS command injection in the example SSM document provisioning script in Trusted Remote Execution (REX) before 2026-07-28 might allow an authenticated remote user who is permitted to invoke the Rex-RO or Rex-RW SSM document to execute arbitrary commands as root on the managed instance, bypassing Cedar policy enforcement.
To remediate this issue, users should delete any Rex-RO and Rex-RW SSM documents created from the example script, in each account and Region where it was run.
Craft CMS versions 4.0.0 before 4.18.9 and 5.0.0 before 5.11.2 have an unauthenticated SQL injection vulnerability in the element search endpoint. The vulnerability arises because the attribute parameter is concatenated into the SQL query without proper sanitization, and emulated PDO prepares allow stacked statements. This flaw allows remote attackers to read and write the database, including setting the admin flag or overwriting password hashes in the users table to gain administrator access.
Jumis (formerly Tildes Jumis) creates and uses a Microsoft SQL Server login named ##Tilde_JumisAdmin## whose password is derived deterministically from a single non-secret input - the SQL Server name (@@servername). The derivation algorithm is hard-coded in the client application and is identical across every installation; it contains a hard-coded secret key for entropy. Because the only input (the server name) is not secret - the instance suffix is hard-coded and the host name is discoverable via the SQL Server Browser service (UDP 1434), the TDS pre-login response, or DNS/NetBIOS - any party able to reach a Jumis SQL Server can compute the password offline and authenticate. The ##Tilde_JumisAdmin## login is a member of the sysadmin server role. Successful authentication therefore grants full administrative control of the SQL Server instance and read/write access to every customer's accounting database hosted on it. The on-premise server installation also programmatically enables xp_cmdshell during routine operation, so sysadmin access escalates to operating-system command execution on the database server.
OpenAI has released GPT-6 Cyber, an advanced AI model designed for cybersecurity tasks, which significantly improves on its predecessor GPT-5.6 Cyber in vulnerability exploitation capabilities while maintaining strict adherence to authorized testing boundaries. The model demonstrated the ability to reproduce thousands of Linux kernel vulnerabilities and generate functional privilege escalation exploits, and it identified numerous high-severity flaws in Firefox, some of which are being patched by Mozilla. OpenAI has implemented safeguards to prevent misuse, including monitoring and restrictions to avoid unauthorized exploitation of critical systems. Access to GPT-6 Cyber is currently limited to approved customers for authorized security testing.
The ELEX WordPress HelpDesk & Customer Ticketing System plugin up to version 3.3.8 contains a critical vulnerability allowing unauthenticated attackers to delete arbitrary files on the server. This occurs due to insufficient file path validation in the factory_reset function. Exploitation involves a two-step process where an attacker first submits a ticket to set a malicious file path, then triggers the factory reset functionality, which lacks proper capability checks. Deleting sensitive files like wp-config.php can lead to remote code execution.
A critical privilege escalation vulnerability exists in JetBrains Hub versions prior to 2026.2.52556. The flaw allows an attacker with limited privileges to escalate their access by manipulating email authentication details during the verification process.
A critical vulnerability in JetBrains Datalore versions before 2026.4 allows view-only collaborators to execute code within a notebook's computation environment. This flaw could lead to complete compromise of confidentiality, integrity, and availability of the affected system.
The BuddyForms plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.10.5 via a form-type confusion attack through the `bf_post_type` parameter. This is due to the public frontend submission handler `buddyforms_form_response_no_ajax()` authorizing logged-out submissions based solely on the target form's `public_submit` flag while independently trusting the attacker-supplied `$_POST['bf_post_type']` to determine the post type of the newly created object — a cross-check introduced in 2.10.2 applies only to existing posts (`post_id != 0`) and is completely bypassed for new-object creation — combined with the `save_post` listener `buddyforms_edit_form_save_meta_box_data()` lacking both a `current_user_can()` capability check and a form-builder nonce, causing it to unconditionally persist attacker-supplied `$_POST['buddyforms_options']` for any newly inserted `buddyforms` CPT post. This makes it possible for unauthenticated attackers to insert a rogue BuddyForms form configuration with an attacker-controlled `new_user_role` value into the live global form registry, then submit a registration through that form to create a new WordPress account with administrator-level privileges and achieve full site takeover. Exploitation requires the WordPress site to have "Anyone can register" enabled and at least one public BuddyForms form attached to a page, both of which are standard BuddyForms deployment configurations.