CVE-2026-33886
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStatamic 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceStatamic CMS versions 5.7.12 through 5.73.15 and prior to 6.7.2 contain an information disclosure vulnerability where authenticated control panel users with access to Antlers-enabled fields can inject config variables into content to read sensitive application configuration values. This is a server-side template injection leading to unauthorized config access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 5.73.12, < 5.73.16>= 6.5.0, < 6.7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Statamic versionCheck the composer.json file in the project root or run `php artisan --version` to determine the exact Statamic version numberAffected if Version is 5.73.12 through 5.73.15, or 6.5.0 through 6.7.1
-
Confirm Antlers template engine is in useSearch for Antlers-enabled fields in the Statamic control panel under Fieldtypes, or inspect the fields directory for field configuration files containing 'type: antlers' or 'antlers: true'Affected if Any content fields are configured with Antlers templating enabled
-
Verify authenticated user access to Antlers fieldsReview user roles and permissions in the Statamic control panel under Users > Roles, checking if any role grants access to create or edit content containing Antlers-enabled fieldsAffected if Non-admin or untrusted users have edit access to Antlers-enabled content fields
User is affected if running a vulnerable version AND Antlers-enabled fields exist AND untrusted authenticated users can access those fields.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped5.73.166.7.2
Upgrade Statamic to version 5.73.16, 6.7.2, or later. Additionally, review user access permissions to Antlers-enabled fields and restrict to only trusted personnel.
Statamic 5.73.16 or 6.7.2
- 1. Back up your Statamic application and database before updating
- 2. Update Statamic to version 5.73.16 or higher if using the v5.x branch
- 3. Update Statamic to version 6.7.2 or higher if using the v6.x branch
- 4. Clear any application caches after upgrading (php artisan cache:clear)
- 5. Verify the upgrade was successful and test that Antlers template rendering no longer exposes configuration values
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33886 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33886 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data