Privilege Escalation in october/system (CVE-2026-46696)
Summary
Vulnerability in october/system (CVE-2026-46696). Risk of unauthorized operations or information disclosure. Exploitable via cms.safe_mode. Mitigation: upgrade to 3.7.17 or later.
Original description
The description as published by the source.
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…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-46696 has been found in october/system.
Attackers can target a specific entry point like cms.safe_mode over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.3/10.
What to do: upgrade october/system to 3.7.17 or later.
If unsure, ask your IT team or search "october/system CVE-2026-46696" on the vendor's site.
CVE-2026-46696 (october/system) — CWE-269 / CVSS v3 3.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: cms.safe_mode / __call / backend_users / admin_auth
Patched: 3.7.17 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-269) exists in october/system. Attackers reach the vulnerable code path via cms.safe_mode.
Check the vendor advisory for the affected versions of october/system. Attack surface: cms.safe_mode / __call / backend_users / admin_auth.
Severity: Low (CVSS 3.3/10). Risk of unauthorized operations or information disclosure.
Update to 3.7.17.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'october/system' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'october/system' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
october/systemを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade october/system to 3.7.17ステージング環境で 3.7.17 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com