# CVE-2026-115938: Low privilege condition filter escapes Twig sandbox, recovers "securityKey" and reaches RCE


- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Also known as:** GHSA-gg4p-9c93-5hfp, GHSA-v4q3-2g5g-wjj6

## What is CVE-2026-115938?

CVE-2026-115938 is a high-severity vulnerability in craftcms cms, published on 23 Oct 2026. 

### Official description

Craft CMS allows any authenticated control panel user to submit an element-search condition whose element selector is evaluated as a sandboxed Twig object template. Craft’s allowed column filter delegates property lookup to Yii ArrayHelper, outside Twig’s SecurityPolicy. Repeated single-segment lookups therefore bypass the sandbox’s empty property/method allowlists.

The vulnerable condition value is ultimately cast to an integer. That does not protect the secret: the template can return author ID 1 when a guessed key character is correct and an impossible ID otherwise. The JSON endpoint returns entries for the first case and an empty array for the second, forming a stable remote character oracle.

After recovering GeneralConfig::securityKey, the same user can compute Craft’s generic HMAC wire format offline. Signed parameters such as redirect are then accepted and passed to unsandboxed View::renderObjectTemplate(), where Twig’s string-callable form can invoke native PHP callables. The regression proof uses the harmless substr() callback and observes abcdef becoming cdef; it does not execute an OS command.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

Upgrade to a fixed version.

## Is CVE-2026-115938 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115938 is a high-severity vulnerability in craftcms cms, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115938 in the wild and no public exploit code.

Affected product: craftcms cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-115938/ (Markdown: https://insights.sbomify.com/CVE-2026-115938/index.md)
```

## Sources

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

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