CVE-2026-29179

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.

Workarounds

• Restrict the editor permission to fully trusted administrators only
• Remove the editor permission from any user who should not have asset or blueprint management access

• Only exploitable by authenticated backend users with editor access who have been specifically denied the editor.cms_assets or editor.tailor_blueprints sub-permissions
• Does not affect default permission configurations where editor users typically have all sub-permissions granted
• Users without editor.cms_assets could manipulate theme asset files (delete, rename, move, upload, create directories)
• Users without editor.tailor_blueprints could manipulate blueprint files (delete, rename, move, upload, create directories)
• Users without editor.tailor_blueprints could view the theme blueprint navigation tree, disclosing file paths and directory structure

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-29179 has a CVSS score of 3.3 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.1.16, 3.7.16); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been patched in v3.7.16 and v4.1.16. Fine-grained document type permission checks are now enforced on all asset and blueprint file operation commands, and the navigation node condition logic has been corrected. All users are encouraged to upgrade to the latest patched version.

1. What is CVE-2026-29179? CVE-2026-29179 is a low-severity incorrect authorization vulnerability in october/system (composer), affecting versions >= 4.0.0, < 4.1.16. It is fixed in 4.1.16, 3.7.16. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-29179? CVE-2026-29179 has a CVSS score of 3.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of october/system are affected by CVE-2026-29179? october/system (composer) versions >= 4.0.0, < 4.1.16 is affected.
4. Is there a fix for CVE-2026-29179? Yes. CVE-2026-29179 is fixed in 4.1.16, 3.7.16. Upgrade to this version or later.
5. Is CVE-2026-29179 exploitable, and should I be worried? Whether CVE-2026-29179 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-29179 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-29179?
   • Upgrade october/system to 4.1.16 or later
   • Upgrade october/system to 3.7.16 or later