October System provides the system module for October Content Management System. Versions prior to 3.7.17 and 4.2.21 have a vulnerability 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. The 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_mode is 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; and the site has at least one existing superuser account whose session the lower-privileged user can impersonate. 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. A workaround is available. Restrict CMS markup editing access to fully trusted administrators only - the standard October CMS recommendation for any deployment. 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.
CVE-2026-46696
“—” beside the score: it is equal to the CVSS score beside it.
Score 3.3 from GitHub Security Advisory (severity: LOW) published 2026-09-14. A secondary CVSS source baseline 3.3; sources differ by 0.0.
Also known asEUVD-2026-77673 (ENISA EUVD) · GHSA-xv9m-fm3w-8w5x (GitHub Security Advisories)Source: ENISA EUVD
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 3.3
- EG Score
- 3.3LOWmedium confidence
- EG Risk
- 15EG Risk 15/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity33% × 45%Impact severity (EG Severity): CVSS 3.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.3% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.3%
- EPSS %ILE
- 19th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (3.3): severity, escalated by confirmed exploitation. This CVE's 3.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 3.3 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
September 14, 2026
Last Modified
September 30, 2026
References (1)
- security-advisories@githubhttps://github.com/octobercms/october/security/advisories/GHSA-xv9m-fm3w-8w5x
Vendor Advisories for CVE-2026-46696(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| composer | october/system @ 3.7.17 (fixes < 3.7.17) | — | ghsa |
| composer | october/system @ 4.2.23 (fixes >= 4.0.0, < 4.2.23) | — | ghsa |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(1 across 1 ecosystem)
Packagist(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| october/system | v1.0.319 ... v1.1.9 (169 versions) |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 11× in last 7d / 43× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-11-01 07:48 UTCGHSA enrichmentGHSA-xv9m-fm3w-8w5x · GitHub severity LOW · GitHub CVSS 3.3
- 2026-11-01 07:48 UTCEG score recompute
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-29 17:44 UTCEG score recompute
- 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-27 05:55 UTCOSV refresh
- 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 19th percentile
- 2026-10-25 14:25 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-18 03:36 UTCEG score recompute
- 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-16 16:42 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 39 moreShow fewer
- 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-12 16:02 UTCEG score recompute
- 2026-10-11 19:45 UTCEG score recompute
- 2026-10-11 16:59 UTCEG score recompute
- 2026-10-11 14:24 UTCEG score recompute
- 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-09 08:19 UTCEG score recompute
- 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.3% · 18th percentile
- 2026-10-06 12:13 UTCEG score recompute
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-03 16:07 UTCEG score recompute
- 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-30 20:02 UTCEG score recompute
- 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-28 23:04 UTCEG score recompute
- 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-26 02:58 UTCEG score recompute
- 2026-09-26 00:27 UTCEPSS rescoreEPSS 0.3% · 17th percentile
- 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-09-23 06:49 UTCEG score recompute
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-09-20 10:44 UTCEG score recompute
- 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-09-17 14:39 UTCEG score recompute
- 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 12th percentile
- 2026-09-14 18:33 UTCEG score recompute
- 2026-09-14 17:45 UTCEG score recompute
- 2026-09-14 16:24 UTCEG score recomputeFirst assessed: 3.3 LOW
Related CVEs(same product + same CWE)
Same product
10 shownPackagist:october/system
Frequently asked(5)
What is CVE-2026-46696?
When was the CVE record for CVE-2026-46696 published?
Is CVE-2026-46696 actively exploited?
What is the CVSS score of CVE-2026-46696?
How do I remediate CVE-2026-46696?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-46696
Is Your Infrastructure Affected by CVE-2026-46696?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.