CVE-2026-46696: October CMS Safe Mode Sandbox Bypass Vulnerability
LOWCVE-2026-46696 is a LOW (CVSS 3.3) safe mode sandbox bypass vulnerability (CWE-284: Improper Access Control) affecting October CMS libraries in the Packagist ecosystem. The issue involves safe mode sandbox bypass via session store and forwarded builder calls. Remediation is available by upgrading affected packages to version 3.7.17, 4.2.23.
CVE-2026-46696 at a Glance
Security Impact
CVSS: 3.3
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N).
How to Fix CVE-2026-46696
To remediate this vulnerability, upgrade all affected October CMS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade october/system to 3.7.17
Upgrade october/system to 4.2.23
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for october/system
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-46696, inspect your project dependencies for October CMS:
inspect dependencies for october/system
Analyze the terminal output to locate any version of October CMS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.7.17), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-284: Improper Access Control, where the product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. In October CMS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-46696 Affected October CMS Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
october/system
|
Packagist |
< 3.7.17
|
3.7.17
|
|
october/system
|
Packagist |
≥ 4.0.0
< 4.2.23
|
4.2.23
|
References
Frequently Asked Questions
What is CVE-2026-46696?
Which October CMS versions are affected?
What version fixes CVE-2026-46696?
Is october/system affected?
What is the CVSS score of CVE-2026-46696?
What CWE is associated with CVE-2026-46696?
How can I check Packagist dependencies for CVE-2026-46696?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-xv9m-fm3w-8w5x",
"modified" : "2026-09-14T16:02:35Z",
"published" : "2026-09-14T16:02:35Z",
"aliases" : [ "CVE-2026-46696" ],
"summary" : "October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls",
"details" : "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.\n\n**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.\n\n**This issue only affects sites that meet all of the following conditions:**\n- `cms.safe_mode` is enabled (a deliberate opt-in for demos or untrusted-editor scenarios)\n- The site has at least one backend user with CMS markup editing access who is not intended to be trusted as a full administrator\n- The site has at least one existing superuser account whose session the lower-privileged user can impersonate\n\n### Impact\n- Arbitrary read access to database tables, including superuser persistence codes from `backend_users`, via raw SQL expressions reachable through `Eloquent\\Model`, `Eloquent\\Builder`, or any allowlisted class that `__call`-forwards to a query builder\n- Forgery of a backend authentication session by writing to the `admin_auth` session key from a Twig template, allowing a markup editor to impersonate an existing superuser\n- Requires authenticated backend access with CMS markup editing permission AND `cms.safe_mode` enabled\n- 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)\n\n### Patches\nThe 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.\n\n### Workarounds\nIf upgrading immediately is not possible:\n- Restrict CMS markup editing access to fully trusted administrators only - the standard October CMS recommendation for any deployment\n- Note that disabling `cms.safe_mode` is **not** a workaround; Safe Mode is the boundary this issue affects, and disabling it removes the only sandbox between markup editors and the server\n\n### References\n- Reported by r00tn0b0dy",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Packagist",
"name" : "october/system"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.7.17"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Packagist",
"name" : "october/system"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.2.23"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/octobercms/october/security/advisories/GHSA-xv9m-fm3w-8w5x"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/octobercms/october"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-269", "CWE-284" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-14T16:02:35Z",
"nvd_published_at" : null
}
}