SAP Commerce Cloud CVE-2026-58231 Critical Flaw Exploited in the Wild Just Three Days After Patch
SAP Commerce Cloud has been struck by a maximum-severity vulnerability, CVE-2026-58231, rated CVSS 10.0. The flaw permits unauthenticated remote code execution and was actively exploited in the wild only three days after the vendor released patches.
Security researchers first published exploitation traffic on 14 August, catching many organizations still digesting the August patch bulletin. SAP assigned the issue its highest priority rating, HotNews, while firms such as Onapsis placed it at the top of their remediation lists for the month.
Where the flaw resides
The vulnerability affects the Data Hub Adapter component responsible for exchanging and importing data between SAP Commerce Cloud and external systems. Attackers abuse a default authentication client that possesses excessive privileges and lacks proper input validation, effectively granting a universal access token to any reachable endpoint.
No credentials or user interaction are required; a single HTTP request is sufficient to achieve arbitrary code execution and full compromise of the application and its connected components.
Why the platform is a high-value target
SAP Commerce Cloud, formerly known as SAP Hybris, serves as the online storefront and B2B transaction layer for numerous global retailers and manufacturers. It is deeply integrated with ERP, CRM, inventory, payment, and fulfillment systems, meaning a breach can expose an entire business chain.
Scanning data from Shadowserver shows more than 4,200 internet-reachable instances worldwide, concentrated in Europe and North America, underscoring the broad attack surface.
Rapid weaponization driven by automation
Security teams observed the first exploitation attempts on 14 August, three days after the 11 August patch release. Analysts attribute the speed to automated and AI-assisted reverse engineering that quickly identifies patch differences and constructs working exploits.
This compressed timeline renders traditional quarterly patching cycles obsolete and forces organizations to treat such issues as immediate emergency events.
Immediate mitigation steps
- Upgrade to SAP Commerce Cloud 2211.55, 2211-jdk21.17 or later versions listed in security note 3771065.
- Verify that production systems are actually running the updated releases.
- Apply IP Filter Sets to restrict Data Hub Adapter endpoints to trusted sources only.
- Map all backend integrations, service accounts, and data flows to understand potential blast radius before an incident occurs.
Related articles
Gmail Address Variants Bypass String Comparison and Enable Multiple Registrations
A single user created four separate accounts using valid Gmail address formats that all deliver to the same inbox: Ivan.Petrov@gmail.com, ivanpetrov@gmail.com, ivan.petrov+shop@gmail.com, and IVAN.PETROV@gmail.com. Simple string comparison in the registration code treated these as distinct entries, allowing circumvention of new-user promotions, free-tier limits, and one-application-per-person rules. The root cause lies in three Gmail-specific behaviors: case-insensitive local parts, plus-addressing that ignores everything after the + symbol, and dots that carry no semantic meaning in the local part. Additional risks arise from IDNA homograph domains that visually mimic legitimate addresses but encode to different Punycode strings. Proper mitigation requires storing both the original email for delivery and a domain-aware normalized form for uniqueness checks, combined with explicit IDNA validation on registration.
Dangling DNS Records Expose Companies to Subdomain Takeovers Years After Projects Shut Down
A marketing team requested reactivation of a three-year-old promotional landing page, only to discover that its domain now served an unrelated third-party website. The root cause was a forgotten CNAME record in the company's DNS zone that continued pointing to a project name on external hosting after the original service had been decommissioned. Because many hosting providers use wildcard DNS entries, standard availability checks and simple DNS resolution tests fail to detect that the target project no longer exists. Attackers who re-register the freed project name can then serve content under the company's legitimate subdomain, automatically obtaining valid TLS certificates and inheriting domain-wide cookies. The article details how such dangling records accumulate across infrastructure, marketing, and acquired company zones, and explains the concrete risks including cookie theft, bypass of Content-Security-Policy, and unauthorized domain ownership proofs. It concludes with a practical remediation workflow: export the full zone, assign owners to every record, validate external targets by application response rather than DNS resolution, and embed record removal into decommissioning procedures.
Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has released an urgent update for Chrome to address CVE-2026-85046, a high-severity zero-day vulnerability in the V8 JavaScript engine that is being actively exploited in the wild. The flaw is a type confusion issue within the Maglev compiler, specifically tied to optimizations around Array.prototype.sort, which can lead to arbitrary memory read and write primitives inside the JavaScript heap. Attackers can exploit the vulnerability by tricking victims into visiting a specially crafted HTML page, enabling remote code execution within the browser sandbox. The update brings Chrome to version 152.0.7977.82 or higher on Windows, macOS, and Linux, while also addressing a total of 12 vulnerabilities. The issue was reported by researcher Salvatore Gulizia, known as Serotav, who received a $1,000 reward. Other Chromium-based browsers such as Edge, Brave, Opera, and Vivaldi will require corresponding updates from their vendors.
Google Patches Actively Exploited V8 Zero-Day in Chrome (CVE-2026-85046)
Google has released an urgent update for Chrome to address CVE-2026-85046, a high-severity zero-day vulnerability in the V8 JavaScript and WebAssembly engine that is being actively exploited in the wild. The flaw is a type confusion issue tied to the Maglev compiler and optimizations around Array.prototype.sort, which can lead to arbitrary memory read and write primitives inside the JavaScript heap. Successful exploitation allows a remote attacker to execute arbitrary code within the browser sandbox after a victim visits a specially crafted HTML page, a technique commonly seen in malvertising and compromised-site campaigns. The fix is included in Chrome 152.0.7977.82 and later for Windows, macOS, and Linux, and the update also resolves a total of twelve vulnerabilities. The vulnerability was reported on 4 August 2026 by researcher Salvatore Gulizia, known as Serotav, who received a $1,000 reward. Other Chromium-based browsers such as Microsoft Edge, Brave, Opera, and Vivaldi will require corresponding updates from their respective vendors.