Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1amended

Craft CMS: Authenticated leak of secret environment variables

CVE-2026-72782GHSA-596p-6jv8-775v

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (craftcms/cms 5.10.6, 4.18.2), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist craftcms/cms

    Affected
    >= 5.0.0-RC1, < 5.10.6>= 4.0.0-RC1, < 4.18.2
    Fixed in
    4.18.2, 5.10.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-72782: 0.39% estimated exploitation activity in the next 30 days; percentile 32.69 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Environment variables and secrets are interpolated into a Twig template even when the Twig sandbox is enabled, allowing them to be leaked by an authenticated attacker. The Craft vulnerability CVE-2026-31857 was only patched by applying sandboxed Twig templating. This theoretically protects Craft CMS against RCE attacks, provided the sandbox is enabled and secure, with no known bypasses. However, the same request parameter elementId, which allows for sandboxed Twig templates to be rendered, also includes functionality that interpolates referenced environment variables. If the parameter includes a string of the form ${ENVVAR} then the string is replaced with the environment variable or secret from a secrets file with that name. Afterward, the string is rendered as a Twig template. If the sandbox is disabled, Twig templates can already gain RCE or access environment variables using the getenv function. Sandboxed Twig templates should not have this access, but now do thanks to this…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-596p-6jv8-775v

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-596p-6jv8-775v

Agent brief

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

# Patch Next advisory brief: CVE-2026-72782

Advisory: Craft CMS: Authenticated leak of secret environment variables
IDs: CVE-2026-72782, GHSA-596p-6jv8-775v
Record: https://patchnext.com/advisories/cve-2026-72782 (revision 3, source checked 26 Oct 2026, 14:51 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: craftcms/cms 5.10.6, 4.18.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist craftcms/cms: affected >= 5.0.0-RC1, < 5.10.6; >= 4.0.0-RC1, < 4.18.2; fixed in 4.18.2, 5.10.6

## Suggested inspection (read-only)
- Packagist craftcms/cms: 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 craftcms/cms.
- 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://osv.dev/vulnerability/GHSA-596p-6jv8-775v (OSV record GHSA-596p-6jv8-775v lists affected ranges: Packagist craftcms/cms >=5.0.0-RC1 =4.0.0-RC1 <4.18.2 (fixed))
- Verified: https://github.com/advisories/GHSA-596p-6jv8-775v (GitHub-reviewed advisory GHSA-596p-6jv8-775v lists affected ranges: Packagist craftcms/cms >=5.0.0-RC1 =4.0.0-RC1 <4.18.2)

Commands are suggestions: review each one before running it.

Loading voting…