CVE-2026-33886: Statamic's sensitive configuration values are exposed to content editors via Antlers-enabled fields

CVE-2026-33886 · Severity: medium · CVSS 6.5 · Published 2026-03-27

Statamic is a Laravel and Git powered content management system (CMS). Starting in version 5.7.12 and prior to versions 5.73.16 and 6.7.2, a control panel user with access to Antlers-enabled fields could access sensitive application configuration values by inserting config variables into their content. This has been fixed in 5.73.16 and 6.7.2.

Technologies: statamic/cms (Packagist), Statamic. Vendors: Packagist, Statamic.

Quick answers

Is CVE-2026-33886 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-33886 being exploited in the wild.
How severe is CVE-2026-33886?
Medium severity, with a CVSS score of 6.5, published 27 March 2026.
Which products and versions are affected?
statamic/cms (Packagist) ECOSYSTEM:introduced=5.73.12,fixed=5.73.16.
Is there a fix for CVE-2026-33886?
Yes. statamic/cms (Packagist): upgrade to 5.73.16 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33886?
Check whether you run statamic/cms (Packagist) or Statamic at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • statamic/cms (Packagist): upgrade to 5.73.16 or later
    composer require statamic/cms:^5.73.16

Affected products

  • statamic/cms (Packagist) ECOSYSTEM:introduced=5.73.12,fixed=5.73.16
  • Statamic

Identifiers

  • CVE-2026-33886
  • GHSA-gcqf-5x9f-hq7f

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.