october/system security advisory

CVE-2026-29179: October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations

CVE-2026-29179 is a low-severity missing authorization vulnerability in the PHP package october/system (CVSS 3.3), published 21 April 2026. No fixed release exists yet: the newest version, 1.1.12, is affected. Exploiting it needs an admin-level account.

low 3.3 affects newest 1.1.12 published 2026-04-21 · updated 2026-10-26

Affected versions: < 3.7.16
>= 4.0.0, < 4.1.16
Fixed in: no fix yet
Newest release: 1.1.12
Severity: Low · CVSS 3.3
Type: Missing authorization check
CWE-863
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your october/system version affected?

Run composer show october/system in your project, then enter the version. We check it against this and every other known october/system advisory.

Who can exploit CVE-2026-29179

Access: A high-privilege account in the app, such as an admin.
Conditions: It only works under specific conditions the attacker does not fully control (CVSS rates the attack as high complexity).

CVSS vector (scored by GitHub): CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N

Your app is only exposed if it uses the affected part of october/system. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-29179 in october/system

Find the installed version: composer show october/system. If you never required it yourself, composer why october/system shows which package pulls it in.
There is no fixed release yet. Read the advisory below for a workaround, and avoid or switch off the affected feature until a fix ships.
Check back on the october/system page. It updates daily from Packagist.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-29179.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for missing authorization issues while the upgrade waits. None of it replaces the fix.

Remove accounts you do not need and review what each role can do.
Put the admin area behind a VPN, IP allow-list or extra login until you upgrade.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-29179 advisory

October is a Content Management System (CMS) and web platform. Prior to 3.7.16 and 4.1.16, fine-grained sub-permission checks for asset and blueprint file operations were not enforced in the CMS and Tailor editor extensions. This only affects backend users who were explicitly granted editor access but had editor.cms_assets or editor.tailor_blueprints specifically withheld, an uncommon permission configuration. In this edge case, such users could perform file operations (create, delete, rename, move, upload) on theme assets or blueprint files despite lacking the required sub-permission. A related operator precedence error in the Tailor navigation also disclosed the theme blueprint directory tree under the same conditions. This vulnerability is fixed in 3.7.16 and 4.1.16.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-29179. Advisory title: “October CMS: Editor Sub-Permission Bypass for Asset and Blueprint File Operations”.

References

GitHub advisory GHSA-jvwg-phxx-j3rp github.com

Other october/system advisories

low CVE-2026-49400: October CMS: PHP Object Injection via Backend Widget Session Storage 2026-09-14
low CVE-2026-46696: October CMS: Safe Mode Sandbox Bypass via Session Store and Forwarded Builder Calls 2026-09-14
low CVE-2026-27937: October CMS: Reflected XSS via DataTable Form Widget 2026-04-21
medium CVE-2026-26067: October CMS has Safe Mode Bypass via CSS Preprocessor Compilers 2026-04-21
medium CVE-2026-24907: October CMS has Stored XSS in Event Log Mail Preview 2026-04-14
medium CVE-2026-24906: October CMS has Stored XSS in Backend Editor Markup Classes 2026-04-14

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.