CVE-2026-26067: October: Safe Mode Bypass via CSS Preprocessor Compilers

Published Apr 21, 2026
·
Updated

A server-side information disclosure vulnerability was identified in the handling of CSS preprocessor files. Backend users with Editor permissions could craft .less, .sass, or .scss files that leverage the compiler's import functionality to read arbitrary files from the server. This worked even with cms.safemode enabled.

Impact - Potential exposure of sensitive server-side files - Requires authenticated backend access with Editor permissions - Only relevant when cms.safemode is enabled (otherwise direct PHP injection is already possible)

Patches The vulnerability has been patched in v3.7.14 and v4.1.10. When cms.safemode is enabled, .less, .sass, and .scss files can no longer be created, uploaded, or edited across the CMS editor, media manager, and file upload interfaces. All users are encouraged to upgrade to the latest patched version.

Workarounds If upgrading immediately is not possible: - Set cms.editableassettypes config to ['css', 'js'] to remove preprocessor file types from the editor - Restrict Editor tool access to fully trusted administrators only

- Reported by Chris Alupului

Other sources

October is a Content Management System (CMS) and web platform. Prior to 3.7.14 and 4.1.10, a server-side information disclosure vulnerability was identified in the handling of CSS preprocessor files. Backend users with Editor permissions could craft .less, .sass, or .scss files that leverage the compiler's import functionality to read arbitrary files from the server. This worked even with cms.safemode enabled. This vulnerability is fixed in 3.7.14 and 4.1.10.

MITRE

Affected Software

3 affected componentsFixes available
October October CMS<3.7.14, <4.1.10
composer/october/system>=4.0.0<4.1.10
4.1.10
composer/october/system<3.7.14
3.7.14

Event History

Apr 21, 2026
CVE Published
via MITRE·04:16 PM
Data Sourced
via MITRE·04:16 PM
DescriptionSeverityWeakness
Advisory Published
via GitHub·04:43 PM
Data Sourced
via GitHub·04:43 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

What is the severity of CVE-2026-26067?

CVE-2026-26067 is categorized as a medium-severity vulnerability due to potential information disclosure risks.

2

How do I fix CVE-2026-26067?

To fix CVE-2026-26067, upgrade your October CMS to version 3.7.14 or 4.1.10 or later.

3

Who is affected by CVE-2026-26067?

Backend users with Editor permissions in versions prior to 3.7.14 and 4.1.10 of October CMS are affected by CVE-2026-26067.

4

What type of vulnerability is CVE-2026-26067?

CVE-2026-26067 is a server-side information disclosure vulnerability related to the handling of CSS preprocessor files.

5

What are the consequences of CVE-2026-26067?

The consequences of CVE-2026-26067 include unauthorized access to sensitive information by users with elevated privileges.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203