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
WordPress Patches Race Condition in Core Update Process Enabling Unauthenticated Remote Code Execution
WordPress addressed a critical race condition vulnerability in its core update mechanism on October 28, 2026, that could allow remote code execution without authentication. The flaw affects the automatic update process used by the majority of installations, exposing a temporary installer during file extraction to a predictable folder. Wordfence recorded 60,471 exploitation attempts within the first 24 hours after disclosure. The issue was discovered by researcher Umut Bayram and fixed across multiple branches including version 7.1.4, which bundles 22 security patches. Mitigations include immediate updates, restricting public access to the wp-content update directory, and ensuring application firewall coverage. Versions 4.6 and earlier receive no further security updates.
Google Releases November Android Security Patch Fixing 216 Vulnerabilities Including Critical Zero-Click Flaws
Google has issued its November security update for Android, addressing a total of 216 vulnerabilities with 23 classified as critical. The patch resolves multiple remote code execution flaws that require no additional privileges or user interaction, qualifying as zero-click attacks. Specific fixes include CVE-2026-58868 in the Framework component and CVE-2026-58876 along with CVE-2026-58936 in the System component, all impacting Android versions 14 through 17. Additional patches cover privilege escalation, information disclosure, and denial-of-service issues across the kernel, Bluetooth, virtualization layers, and chipsets from MediaTek and Qualcomm. No evidence of in-the-wild exploitation has been noted in the bulletin, yet the critical nature of the remote code execution bugs warrants immediate attention. Users must verify the 2026-11-05 patch level or newer in device settings, as simply running the latest Android version does not guarantee all fixes are installed. Some updates arrive via Google Play system updates while others depend on device manufacturers.
Backdoor with Password 123456 and Hardcoded Keys: How AI Cracked 'Encrypted' USB Drives
An AI agent rapidly discovered critical cryptographic weaknesses in multiple USB encryption and copy-protection products, including hardcoded backdoor accounts and keys that bypassed user passwords entirely. In the SecZure YutianDun drive, two hidden accounts with passwords 123456 and SECZURE.COM allowed full decryption of files without the administrator password. NetacFileLock used a fixed AES-256 key embedded in the binary, ignoring the user password completely while also logging passwords in plaintext and employing ECB mode. KakaSoft USB Copy Protection relied on a modified MD5 implementation with altered shift constants and a hardcoded internal password derived from an embedded seed, enabling full Blowfish decryption without any user input. Nexcopy stored its Triple DES content key and IV in an encrypted configuration file protected only by a fixed 32-byte certificate inside the viewer application. The AI completed analyses in minutes that previously required hours of manual time-travel debugging and reverse engineering.
CVE-2026-98432: Temporary nftables Filter with Auto-Rollback for Ubuntu Servers
Administrators are deploying a temporary nftables-based mitigation for CVE-2026-98432 on Linux systems while awaiting official kernel patches. The filter drops IPv4 TCP packets with IP header length exceeding five, reducing exposure to the vulnerability. The procedure includes verifying kernel status via Canonical, preparing rollback commands, and using systemd timers to automatically remove the table after five minutes if connectivity is lost. Steps cover syntax validation with nft --check, integration with existing firewall configurations, and post-reboot verification to ensure the temporary table persists without interfering with ufw or Docker rules. Red Hat guidance on discarding packets containing IP options is referenced as a complementary measure. The process is designed for single-server testing before scaling to production fleets, with explicit instructions to avoid flush ruleset operations that could disrupt other tables.