A missing bounds check in the BSON CodeWScope element accessors allows an attacker to trigger an out-of-bounds heap read via a crafted aggregation pipeline. The vulnerability can be exploited by an authenticated user by generating a malformed BSONColumn data containing a CodeWScope element, bypassing wire-level BSON validation. When the forged element is decompressed, the unchecked size value is used in pointer arithmetic, causing either a server crash or disclosure of adjacent heap memory contents.
CVE-2026-13074 is a medium-severity vulnerability in MongoDB Server that allows an unauthenticated remote client to cause excessive CPU consumption. This occurs by sending a specific combination of parameters to the awaitable hello command in exhaust mode, which triggers a response loop bypassing normal throttling. This can degrade server availability with only a small number of connections. No official patch or remediation guidance is currently available.
When compute mode is enabled on a standalone mongod instance, insufficient validation of externally sourced BSON data during aggregation pipeline processing can result in memory corruption, potentially leading to process termination or other unintended behavior. This configuration is non-default and requires explicit enablement at startup.
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Install). Supported versions that are affected are Oracle Java SE: 8u501, 11.0.32, 17.0.20, 21.0.12, 25.0.4, 26.0.2; Oracle GraalVM for JDK: 17.0.20 and 21.0.12; Oracle GraalVM Enterprise Edition: 21.3.19. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition executes to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. CVSS 3.1 Base Score 7.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
An unauthenticated attacker can chain two WordPress Core vulnerabilities, CVE-2026-63030 and CVE-2026-60137, to achieve remote code execution against affected WordPress installations. Multiple security firms have confirmed active in-the-wild exploitation within days of public disclosure, and public proof-of-concept exploits are circulating. Key takeaways: Two WordPress Core vulnerabilities, CVE-2026-63030 and CVE-2026-60137, can be chained together to achieve pre-authentication remote code execution against WordPress 6.9.x and 7.0.x installations. Multiple security firms have confirmed in-the-wild exploitation, with public proof-of-concept exploits appearing within hours of the July 17, 2026 disclosure. Patches are available in WordPress 7.0.2 and 6.9.5; WordPress.org has enabled forced automatic updates across affected supported installations. Background Tenable's Research Special Operations (RSO) team has compiled this blog to answer Frequently Asked Questions (FAQ) regarding wp2shell, two vulnerabilities in WordPress Core that can be chained together to achieve pre-authentication remote code execution. FAQ What is wp2shell? wp2shell is the name given to two vulnerabilities in WordPress Core. When was wp2shell first disclosed? On July 17, 2026, WordPress released security updates addressing the wp2shell vulnerabilities alongside two GitHub Security Advisories. Adam Kues of Searchlight Cyber, who discovered and disclosed CVE-2026-63030, published research on the same day and chose to hold back the technical specifics given the severity of the finding. Searchlight Cyber also launched wp2shell.com , a testing tool that allows administrators to check whether their WordPress installation is vulnerable. On July 20, Searchlight Cyber published a full technical breakdown of the attack chain. What are the vulnerabilities associated with wp2shell? wp2shell is a two-vulnerability exploit chain affecting WordPress Core. CVE Description CVSSv3 CVE-2026-63030 WordPress Core REST API Batch-Route Confusion Remote Code Execution Vulnerability 9.8 CVE-2026-60137 WordPress Core WP_Query author__not_in SQL Injection Vulnerability 5.9 CVE-2026-63030 is a REST API batch-route confusion weakness introduced in WordPress 6.9. CVE-2026-60137 is a SQL injection flaw in the author__not_in parameter of WP_Query , present in WordPress 6.8 and later. When chained on WordPress 6.9.0 through 7.0.1, the two flaws allow an unauthenticated attacker to reach the REST API batch endpoint at /wp-json/batch/v1 and achieve remote code execution. CVE-2026-60137 was discovered and disclosed by security researchers TF1T, dtro, and haongo. CVE-2026-60137 also affects WordPress 6.8.0 through 6.8.5 as a standalone SQL injection issue. Because CVE-2026-63030 was introduced in WordPress 6.9, the full RCE chain is only achievable on 6.9.x and 7.0.x installations. How severe is the wp2shell vulnerability chain? An anonymous, unauthenticated user can execute the chain against a default WordPress installation with no plugins required. No preconditions exist beyond the default WordPress configuration. Cloudflare notes that the vulnerable code path is reached when “a persistent object cache is not in use.” Note: wp2shell targets WordPress Core itself rather than a plugin or theme. All four prior WordPress-related entries in the CISA Known Exploited Vulnerabilities (KEV) catalog involve plugins, not core. Pre-authentication remote code execution in WordPress Core is uncommon. CVE Product Added to KEV Ransomware CVE-2026-41940 WebPros cPanel & WHM and WP2 (WordPress Squared) April 30, 2026 Known CVE-2020-25213 WordPress File Manager Plugin November 3, 2021 Unknown CVE-2020-11738 WordPress Snap Creek Duplicator Plugin November 3, 2021 Unknown CVE-2019-9978 WordPress Social Warfare Plugin November 3, 2021 Unknown How widespread are the attacks exploiting wp2shell? WordPress is the most widely deployed content management system in the world. Some hosted installations will receive patc…
Rclone versions prior to 1.74.4 contain an authorization bypass vulnerability in the 'serve restic --private-repos' command. This flaw allows an authenticated user to use '..' path segments in the URL to access, modify, or delete another user's private repository on backends that normalize path components. The issue is resolved in version 1.74.4.
Rclone versions prior to 1.74.4 contain a vulnerability in the archive extract feature that allows extracted files to be written outside the intended destination prefix. This occurs when extracting crafted archives with parent path components like '../', enabling potential creation or overwrite of sibling objects in the same bucket or path scope. The issue is fixed in version 1.74.4.
Rclone versions prior to 1.74.4 contain a vulnerability when using the -l/--links option to sync symlinks. The software serializes symlinks as .rclonelink text objects and recreates them on a local destination without validating the symlink target. This allows an attacker controlling the remote source to create a symlink that escapes the intended destination directory, causing subsequent file writes to be placed outside the target directory with attacker-chosen content. This issue is fixed in rclone version 1.74.4.
A flaw was found in the group search functionality of the Keycloak server's administrative API. When Fine-Grained Admin Permissions (FGAP) v2 is enabled, a delegated administrator can bypass access restrictions to view parent groups they are not authorized to see. By searching for a child group they have permission to view, the system incorrectly returns the full details of the parent group in the response, leading to the disclosure of sensitive group attributes and configuration.
Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 contain a stored cross-site scripting (XSS) vulnerability in the topic featured link feature. The vulnerability arises because the featured link was not properly normalized and escaped before rendering in the topic list. This allows a user with permission to set a featured link to inject JavaScript code if the default Content Security Policy protections are modified or disabled. The issue has been fixed in the specified versions.
Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 contain a stored cross-site scripting (XSS) vulnerability in the two-factor authentication (2FA) delete confirmation modal. The vulnerability arises because a malicious second factor name on an attacker-controlled account is not properly escaped in the confirmation dialog. This flaw can be triggered when an administrator impersonates the affected account. The issue is fixed in the specified patched versions.
Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 contain insufficient SVG sanitization in upload and user avatar handling. This vulnerability could allow cross-site scripting (XSS) when users visit certain uncommon URLs. The issue has been fixed in the specified later versions.
Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 contain a vulnerability in the AWS SES bounce webhook. The webhook verified that SNS messages were signed by Amazon but failed to restrict them to trusted TopicArn values. This allowed any AWS account holder to send validly signed forged bounce notifications, which could disable a targeted user's email. The issue is fixed in the specified patched versions.
Discourse versions prior to 2026.1.5, 2026.4.2, and 2026.5.1 could leak restricted tag and tag-group names via category and group endpoints to unauthorized and anonymous users. This information disclosure affects tags attached to publicly readable categories. The issue is fixed in versions 2026.1.5, 2026.4.2, and 2026.5.1 and later.
Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 contain a vulnerability where regular users could route direct S3 multipart uploads through the ExternalUploadManager into the admin backup store. This issue has been fixed in the specified versions. The vulnerability is classified as medium severity.
Discourse versions prior to 2026.1.5, 2026.4.2, and 2026.5.1 have a vulnerability where secure uploads could be exposed via the pull_hotlinked_images feature if an attacker knew the secured upload URL and the secure_uploads setting was enabled. This issue allows unauthorized access to uploads intended to be secure. The vulnerability is fixed in versions 2026.1.5, 2026.4.2, and 2026.5.1 and later.
Discourse versions prior to 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 have a vulnerability where private event invitee information is exposed to unauthorized users. Specifically, the EventSerializer component could leak invited group names, sample invitees, and attendance statistics to users who can view the topic but should not see the private event invitee list. This issue has been fixed in the stated versions.
A vulnerability in Discourse prior to versions 2026.6.0, 2026.5.1, 2026.4.2, and 2026.1.5 allows newly registered users during signup to assign themselves a primary_group_id. This improper assignment grants them whisper-group privileges without legitimate membership on sites configured with whispers_allowed_groups. The issue has been fixed in the specified patched versions.
Pillow is a Python imaging library. Prior to 12.3.0, Pillow's public rank-filter API can trigger a native heap out-of-bounds write when given a very large odd filter size because ImageFilter.RankFilter.filter() calls image.expand(size // 2, size // 2) before rank-filter size validation and ImagingExpand() computes output dimensions with unchecked signed int arithmetic. This issue is fixed in version 12.3.0.
Pillow is a Python imaging library. From 5.1.0 until 12.3.0, PdfParser.PdfStream.decode() in PIL/PdfParser.py calls zlib.decompress() with bufsize set to the PDF stream Length field without bounding the decompressed output size, allowing a crafted FlateDecode PDF stream to exhaust memory from a small file. This issue is fixed in version 12.3.0.