GHSA-m5qg-jc75-4jp6
MEDIUMGHSA-m5qg-jc75-4jp6 is a medium-severity (CVSS 4.9) CWE-284 vulnerability in october/rain. O3 Security confirms whether GHSA-m5qg-jc75-4jp6 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
October Rain has a Twig Sandbox Bypass via Collection Methods
Blast Radius
october/rain🐘october/rainReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
A sandbox bypass vulnerability was identified in the optional Twig safe mode feature (CMS_SAFE_MODE). 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
CMS_SAFE_MODEenabled (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
CMS_SAFE_MODEif untrusted template editing is not required - Restrict CMS template editing permissions to fully trusted administrators only
References
- Reported by Łukasz Rybak
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | october/rain | ≥ 4.0.0&&< 4.1.5 | 4.1.5 |
| 🐘Packagist | october/rain | all versions | 3.7.13 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for october/rain. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update october/rain to 4.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-m5qg-jc75-4jp6 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-m5qg-jc75-4jp6 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-m5qg-jc75-4jp6. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-m5qg-jc75-4jp6 in your dependencies?
O3 detects GHSA-m5qg-jc75-4jp6 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.