MongoDB Server Patches 24 Vulnerabilities Including Critical Flaw in mongod Compute Mode
MongoDB Server has received updates that address 24 vulnerabilities, one of which is classified as critical. The fixes were published on July 22, 2026, and target different branches of the NoSQL database.
The most severe flaw, tracked as CVE-2026-13072, received the highest severity rating of Critical. It affects standalone mongod instances when compute mode is enabled. Insufficient validation of external data input can trigger memory corruption, and the vulnerability carries a CVSSv3.1 base score of 9.2.
Among the remaining issues, CVE-2026-13059 allows low-privileged authenticated users to perform unauthorized read and write operations. In total, the update resolves 16 high-severity vulnerabilities, seven medium-severity issues, and one low-severity problem, along with additional bug fixes that improve overall reliability.
The following versions incorporate the corrections: MongoDB 8.3.7, MongoDB 8.2.12, MongoDB 8.0.28, and MongoDB 7.0.39. Administrators are advised to apply the updates promptly to mitigate potential exploitation risks.
Related articles
Weekly Roundup: Critical Vulnerabilities Hit VMware ESX, FortiOS, Chrome, fastjson, Cisco FMC and Ruby on Rails
Security NEXT published its list of the ten most-read articles for the week of July 26 to August 1, 2026. The ranking is dominated by high-severity vulnerabilities affecting widely deployed enterprise platforms. VMware released fixes for serious flaws in ESX and vCenter, while Fortinet confirmed active exploitation of vulnerabilities in FortiOS and VeloCloud Orchestrator. Google patched 370 security issues in Chrome, and a data-conversion library fastjson was found vulnerable with observed attacks. Apple shipped iOS 26.6 and iPadOS 26.6 containing fixes for 87 vulnerabilities, and Cisco warned that its Firewall Management Center is already being exploited. Additional patches addressed OpenAM, Node.js, and a critical flaw dubbed KindaRails2Shell in Ruby on Rails. The list also includes a breach at an ANA Group e-commerce site that may have exposed customer data.
pgAdmin 4 Issues Critical Security Update Addressing Seven Vulnerabilities Including Prior Patch Failures
The pgAdmin 4 development team has released version 9.17 to resolve seven vulnerabilities in the popular PostgreSQL database management tool. The update covers two newly discovered issues rated Critical, one Critical flaw stemming from incomplete remediation in the previous 9.16 release, and four additional vulnerabilities. Among the new flaws is CVE-2026-17566, an OS command injection vulnerability in the query-based data export feature caused by insufficient SQL validation. Another Critical issue, CVE-2026-17349, allows duplication of shared servers to inadvertently copy stored database credentials belonging to other users. The incomplete fix for CVE-2026-12045 led to CVE-2026-17351, which bypasses the read-only restrictions of the AI Assistant due to differing string literal interpretations between the SQL parsing library and PostgreSQL.
Dangerous C++ Traps: Memory Safety Issues, Undefined Behavior, and Code That Betrays Developers
Around 70% of vulnerabilities assigned CVE numbers by Microsoft each year stem from memory safety errors, with Chromium reporting a similar pattern for serious Chrome bugs. The article examines how C++ deliberately permits low-level memory access for performance but demands strict discipline to avoid undefined behavior (UB). It details real-world cases including Heartbleed (CVE-2014-0160) in OpenSSL, use-after-free errors, buffer overflows, and data races. Modern tools such as AddressSanitizer, UndefinedBehaviorSanitizer, and ThreadSanitizer are presented as essential for detection, alongside recommendations for RAII, std::span, and smart pointers. The piece also discusses C++26 changes introducing erroneous behavior for uninitialized variables and advises when to consider memory-safe languages like Rust for new components. Practical migration steps and compiler warning strategies are outlined to reduce risk in existing codebases.
Critical CosmosEscape Flaw Breaks Customer Isolation in Azure Cosmos DB
A critical vulnerability named CosmosEscape allowed attackers to escape the restricted Gremlin API environment and execute arbitrary code on the DB Gateway component of Azure Cosmos DB. The flaw exploited weaknesses in .NET reflection protections, enabling file read/write operations and command execution that ultimately yielded the Cosmos Master Key. With this global signing key, an attacker could retrieve the primary key for any customer account and gain full read/write access. The exploit also exposed the Config Store containing account names, subscription identifiers, tenant details, and network rules. Even network-isolated and private instances remained vulnerable because the DB Gateway itself enforced those restrictions. Internal Microsoft services including Entra ID, Teams, and Copilot rely on Cosmos DB, amplifying the potential impact of the issue.