CVE-2026-33882: Statamic is a Laravel and Git powered content management system (CMS)
CVE-2026-33882 is a medium-severity flaw (CVSS 6.5) affecting statamic. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, the markdown preview endpoint could be manipulated to return augmented data from arbitrary fieldtypes. With the users fieldtype specifically, an authenticated control panel user could retrieve sensitive user data including email addresses, encrypted passkey data, and encrypted two-factor authentication codes. This has been fixed in 5.73.16
Why this priority
- No elevated risk signals yet
A fixed release or distro patch exists.
Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-33882?
statamic: upgrade to 5.73.16, 6.7.2. Exact commands for each OS are on this page.
Is CVE-2026-33882 being exploited?
CVE-2026-33882 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-33882 affect?
CVE-2026-33882 affects statamic. Severity is medium (CVSS 6.5). Statamic is a Laravel and Git powered content management system (CMS). Prior to versions 5.73.16 and 6.7.2, the markdown preview endpoint could be manipulated to return augmented data from arbitrary fieldtypes. With the users fieldtype spec
How urgent is CVE-2026-33882?
Priority 27/100. No elevated risk signals yet.
Software pages
Laravel vulnerabilities · Git vulnerabilities