How severe is GHSA-gcqf-5x9f-hq7f?

GHSA-gcqf-5x9f-hq7f has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-gcqf-5x9f-hq7f?

GHSA-gcqf-5x9f-hq7f affects the following packages: statamic/cms (Packagist), statamic/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-gcqf-5x9f-hq7f?

Update statamic/cms to 5.73.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gcqf-5x9f-hq7f is resolved across your whole dependency graph.

How do I detect GHSA-gcqf-5x9f-hq7f in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-gcqf-5x9f-hq7f if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-gcqf-5x9f-hq7f?

O3 pinpoints whether GHSA-gcqf-5x9f-hq7f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-gcqf-5x9f-hq7f actively exploited in the wild?

No public exploit code has been indexed for GHSA-gcqf-5x9f-hq7f yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-gcqf-5x9f-hq7f?

GHSA-gcqf-5x9f-hq7f is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gcqf-5x9f-hq7f published, and has it been updated?

GHSA-gcqf-5x9f-hq7f was published on March 26, 2026 and was last updated on March 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

GHSA-gcqf-5x9f-hq7f

MEDIUM

GHSA-gcqf-5x9f-hq7f is a medium-severity (CVSS 6.5) Information Exposure vulnerability in statamic/cms. O3 Security confirms whether GHSA-gcqf-5x9f-hq7f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-33886

Published

Mar 26, 2026

Updated

Mar 27, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Mar 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘statamic/cms🐘statamic/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Impact

A control panel user with access to Antlers-enabled fields could access sensitive application configuration values by inserting config variables into their content.

Patches

This has been fixed in 5.73.16 and 6.7.2.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`statamic/cms`	≥ 5.73.12&&< 5.73.16	5.73.16
🐘Packagist	`statamic/cms`	≥ 6.5.0&&< 6.7.2	6.7.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for statamic/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update statamic/cms to 5.73.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gcqf-5x9f-hq7f is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-gcqf-5x9f-hq7f is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-gcqf-5x9f-hq7f. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A control panel user with access to Antlers-enabled fields could access sensitive application configuration values by inserting config variables into their content. ### Patches This has been fixed in 5.73.16 and 6.7.2.

O3 Security · Impact-Aware SCA

Is GHSA-gcqf-5x9f-hq7f in your dependencies?

O3 detects GHSA-gcqf-5x9f-hq7f across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works