October Rain has a Twig Sandbox Bypass via Collection Methods

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

4.9 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2026-22692: 0.40% estimated exploitation activity in the next 30 days; percentile 33.77 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A sandbox bypass vulnerability was identified in the optional Twig safe mode feature (CMSSAFEMODE). Certain methods on the collect() helper were not properly restricted, allowing authenticated users with template editing permissions to bypass sandbox protections. Impact - Bypass of Twig sandbox restrictions - Only affects installations with CMSSAFEMODE enabled (disabled by default) - Requires authenticated backend access with CMS template editing permissions Patches The vulnerability has been patched in v4.1.5 and v3.7.13. All users who have enabled safe mode are encouraged to upgrade to the latest patched version. Workarounds If upgrading immediately is not possible: - Disable CMSSAFEMODE if untrusted template editing is not required - Restrict CMS template editing permissions to fully trusted administrators only References - Reported by Łukasz Rybak

Published by the source

14 Apr 2026, 20:02 UTC

Last modified by the source

14 Apr 2026, 20:02 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m5qg-jc75-4jp6

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-22692

Advisory: October Rain has a Twig Sandbox Bypass via Collection Methods
IDs: CVE-2026-22692, GHSA-m5qg-jc75-4jp6
Record: https://patchnext.com/advisories/cve-2026-22692 (revision 1, source checked 26 Oct 2026, 14:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: october/rain 4.1.5, 3.7.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist october/rain: affected >= 4.0.0, <= 4.1.4; <= 3.7.12; fixed in 4.1.5, 3.7.13

## Suggested inspection (read-only)
- Packagist october/rain: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on october/rain.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m5qg-jc75-4jp6 (GitHub-reviewed advisory GHSA-m5qg-jc75-4jp6 lists affected ranges: Packagist october/rain >=4.0.0 =0 <=3.7.12)

Commands are suggestions: review each one before running it.