craftcms/cms security advisory

CVE-2026-72782: Craft CMS: Authenticated leak of secret environment variables

CVE-2026-72782 is a medium-severity security vulnerability in the PHP package craftcms/cms (CVSS 6.5), published 11 August 2026. It is fixed in 4.18.2 and 5.10.6, one per release line; earlier versions on each line are affected. Exploiting it needs a low-privilege user account.

medium 6.5 published 2026-08-11 · updated 2026-10-24

Affected versions: >= 4.0.0-RC1, < 4.18.2
>= 5.0.0-RC1, < 5.10.6
Fixed in: 4.18.2, 5.10.6
Newest release: 5.12.0
Severity: Medium · CVSS 6.5
Type: Security issue
CWE-668
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your craftcms/cms version affected?

Run composer show craftcms/cms in your project, then enter the version. We check it against this and every other known craftcms/cms advisory.

Who can exploit CVE-2026-72782

Access: A normal, low-privilege user account in the app.

CVSS vector (scored by VulnCheck): CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Your app is only exposed if it uses the affected part of craftcms/cms. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-72782 in craftcms/cms

Find the installed version: composer show craftcms/cms. If you never required it yourself, composer why craftcms/cms shows which package pulls it in.
Update it: composer update craftcms/cms --with-all-dependencies. You need the fixed version for your release line (4.18.2 and 5.10.6).
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "craftcms/cms": "^5.10.6" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-72782.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

General hardening for this kind of issue while the upgrade waits. None of it replaces the fix.

If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-72782 advisory

Craft CMS versions >= 5.0.0-RC1 before 5.10.6 and >= 4.0.0-RC1 before 4.18.2 interpolate environment variables and secrets (via ${ENV_VAR} strings in the elementId parameter) into Twig templates before rendering, even when the Twig sandbox is enabled. An authenticated attacker with control panel access can render a malicious sandboxed Twig template and, using a blind error-based technique across many requests, incrementally leak arbitrary environment variables and secrets. These can be abused to forge sessions (via CRAFT_SECURITY_KEY), escalate privileges, and steal database, SMTP, API, or blob storage credentials. Fixed in 5.10.6 and 4.18.2.

Description from the CVE record, published by VulnCheck (the CVE Numbering Authority), via the NVD entry for CVE-2026-72782. Advisory title: “Craft CMS: Authenticated leak of secret environment variables”.

References

GitHub advisory GHSA-596p-6jv8-775v github.com
Vulncheck security advisory www.vulncheck.com

Other craftcms/cms advisories

critical Craft CMS: Passkey login accepts replayed WebAuthn assertions 2026-08-07
medium CVE-2026-72779: Craft CMS: Arbitrary file read via SplFileObject in non-sandboxed template contexts 2026-08-06
medium CVE-2026-72785: Craft CMS: Authorization bypass: view-only Categories user can modify category structure via structures/move-element 2026-08-06
medium CVE-2026-14794: Craft CMS: Missing authorization check allows non-admin control panel users access to user registration metrics 2026-08-06
low CVE-2026-72783: Craft CMS: Incorrect path validation could potentially lead to path traversal 2026-08-06
medium Craft CMS: Stored XSS in the control panel via unescaped draft name 2026-08-06

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.