CVE-2026-22692 is a sandbox bypass vulnerability in October CMS / October Rain affecting versions prior to 3.7.13 and versions 4.0.0 through 4.1.4. The flaw exists in the optional Twig safe mode feature controlled by CMS_SAFE_MODE. Certain methods exposed through the collect() helper were not properly restricted by the sandbox policy, allowing an authenticated backend user with CMS template editing permissions to escape intended Twig sandbox limitations. As a result, a user who is expected to be constrained by safe mode can perform template operations outside the intended sandbox protections.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
CMS_SAFE_MODE is enabled. This undermines the security boundary intended to safely permit untrusted or less-trusted template editing. The practical impact is unauthorized capability within the templating context, which may enable execution of otherwise restricted template logic and compromise of application integrity within the CMS rendering environment.If you can’t patch tonight, do this now.
CMS_SAFE_MODE where untrusted template editing is not required. Additionally, restrict backend CMS template editing permissions to fully trusted administrators only, since exploitation requires authenticated access and template editing capability.Patch, then assume compromise.
collect() helper methods in Twig safe mode.No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.