CVE-2026-46696
LOWCVE-2026-46696 is a low-severity (CVSS 3.3) Improper Privilege Management vulnerability in october/system. O3 Security confirms whether CVE-2026-46696 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls
Real-World Exposure
october/system🐘october/systemReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A vulnerability was identified in the Twig sandbox security policy that allowed a chained bypass when cms.safe_mode is enabled. The Laravel session store was exposed to Twig with unrestricted method access, and raw SQL methods reachable through Eloquent's __call forwarding were not blocked across the full builder chain. When combined, a backend user with CMS markup editing access could read arbitrary database values via raw SQL expressions and write to the backend authentication session key, forging a backend session as another existing user.
Scope of impact is narrow. Safe Mode is a niche feature, primarily used for demo installations and multi-tenant or shared-editor scenarios where untrusted users are deliberately granted access to the CMS markup editor. Standard production deployments do not enable Safe Mode, because under normal October CMS guidance backend access - including markup editing - is restricted to trusted administrators, and direct PHP injection through markup is already possible without Safe Mode in that configuration.
This issue only affects sites that meet all of the following conditions:
cms.safe_modeis enabled (a deliberate opt-in for demos or untrusted-editor scenarios)- The site has at least one backend user with CMS markup editing access who is not intended to be trusted as a full administrator
- The site has at least one existing superuser account whose session the lower-privileged user can impersonate
Impact
- Arbitrary read access to database tables, including superuser persistence codes from
backend_users, via raw SQL expressions reachable throughEloquent\Model,Eloquent\Builder, or any allowlisted class that__call-forwards to a query builder - Forgery of a backend authentication session by writing to the
admin_authsession key from a Twig template, allowing a markup editor to impersonate an existing superuser - Requires authenticated backend access with CMS markup editing permission AND
cms.safe_modeenabled - Not exploitable when Safe Mode is disabled (direct PHP injection through markup is already possible in that configuration, so Safe Mode is the boundary this issue affects)
Patches
The vulnerability has been patched in v3.7.17 and v4.2.21. The Laravel session store is now wrapped in a proxy that exposes only an explicit subset of read/write methods and rejects writes to reserved session key prefixes (admin_auth, october_auth, login_*, _token, and other framework internals). Raw SQL and subquery methods (selectRaw, whereRaw, orderByRaw, joinSub, and related) are now blocked on Query\Builder, Eloquent\Builder, and Eloquent\Model so the blocklist is consistent across the __call forwarding chain. All sites that enable cms.safe_mode are encouraged to upgrade to the latest patched version.
Workarounds
If upgrading immediately is not possible:
- Restrict CMS markup editing access to fully trusted administrators only - the standard October CMS recommendation for any deployment
- Note that disabling
cms.safe_modeis not a workaround; Safe Mode is the boundary this issue affects, and disabling it removes the only sandbox between markup editors and the server
References
- Reported by r00tn0b0dy
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | october/system | all versions | 3.7.17 |
| 🐘Packagist | october/system | ≥ 4.0.0&&< 4.2.23 | 4.2.23 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/system. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update october/system to 3.7.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46696 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-46696 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-46696. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-46696 in your dependencies?
O3 detects CVE-2026-46696 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.