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

> Users with editor access but missing specific sub-permissions can modify or view theme assets and blueprint files in October CMS.

- **Severity:** Low 3.3 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Apr 2026
- **Updated:** 21 Apr 2026
- **Also known as:** GHSA-jvwg-phxx-j3rp

## What is CVE-2026-29179?

CVE-2026-29179 is a low-severity missing authorization vulnerability in octobercms october, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

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.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2026-29179?

4 open source packages ship an affected version, including october/system.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `october/system` | Packagist | All versions | 3.7.16 |
| `october/system` | Packagist | All versions | 3.7.16 |
| `october/system` | Packagist | From 4.0.0 | 4.1.16 |
| `october/system` | Packagist | From 4.0.0 | 4.1.16 |

## How do I fix CVE-2026-29179?

Upgrade october/system to a fixed version for your release line: 3.7.16 or 4.1.16.

## Is CVE-2026-29179 being exploited?

There is no known exploitation of CVE-2026-29179 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-29179 and fix it if it is affected.

What it is: CVE-2026-29179 is a low-severity missing authorization vulnerability in octobercms october, published on 21 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-29179 in the wild and no public exploit code.

Affected packages and fixed versions:
- october/system (Packagist): affected all versions; fixed in 3.7.16
- october/system (Packagist): affected all versions; fixed in 3.7.16
- october/system (Packagist): affected from 4.0.0; fixed in 4.1.16
- october/system (Packagist): affected from 4.0.0; fixed in 4.1.16

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-29179/ (Markdown: https://insights.sbomify.com/CVE-2026-29179/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-29179
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-29179
- OSV: https://osv.dev/vulnerability/CVE-2026-29179

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-29179/
Summaries are generated and may contain mistakes; the official description above is the record.