# CVE-2026-27131: craft-sprig — Fixed in 2.15.2

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

# CVE-2026-27131 — craft-sprig

MEDIUM [Fix: putyourlightson/craft-sprig@09c9da2](https://github.com/putyourlightson/craft-sprig/commit/09c9da2ffb45a8857829f3390ae2578e26cfe03b)

CVE-2026-27131 is a medium-severity (CVSS 5.5) Information Exposure vulnerability in putyourlightson/craft-sprig. A fix is available for putyourlightson/craft-sprig — see the affected versions and patch details below.

Sprig Plugin for Craft CMS potentially discloses sensitive information via Sprig Playground

Also known as[GHSA-m59h-42jf-cphr](/vulnerability/GHSA-m59h-42jf-cphr)

Published

Mar 23, 2026

Updated

Oct 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

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

## Exploitation Status

### No confirmed exploitation observed yet

-   CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2026-27131.

## EPSS Exploitation Probability

[via FIRST.org ↗](https://www.first.org/epss/)

0.3%probability of exploitation in next 30 days

Lower Risk+0.01%

Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

0.00%0.31%0.61%0.92%0.0%0.3%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/).

## How urgent is this, really

## Where this sits among everything scored

## Real-World Exposure

2 pkgs affected

🐘`putyourlightson/craft-sprig`🐘`putyourlightson/craft-sprig`

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

The Sprig Plugin for Craft CMS is a reactive Twig component framework for Craft CMS. Starting in version 2.0.0 and prior to versions 2.15.2 and 3.15.2, admin users, and users with explicit permission to access the Sprig Playground, could potentially expose the security key, credentials, and other sensitive configuration data, in addition to running the `hashData()` signing function. This issue was mitigated in versions 3.15.2 and 2.15.2 by disabling access to the Sprig Playground entirely when `devMode` is disabled, by default. It is possible to override this behavior using a new `enablePlaygroundWhenDevModeDisabled` that defaults to `false`.

## Affected Packages

2 total 2 fixed

Ecosystem

Package

Vulnerable range

Fix

🐘Packagist

`putyourlightson/craft-sprig` 

≥ 2.0.0&&< 2.15.2

2.15.2`composer require putyourlightson/craft-sprig:^2.15.2`

🐘Packagist

`putyourlightson/craft-sprig` 

≥ 3.0.0&&< 3.7.2

3.7.2`composer require putyourlightson/craft-sprig:^3.7.2`

## Detection & mitigation playbook

Open-source dependency

1.  ### Detect
    
    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for putyourlightson/craft-sprig, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
    
2.  ### Fix
    
    Update putyourlightson/craft-sprig to 2.15.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-27131 is resolved across your whole dependency graph.
    
3.  ### Workarounds
    
    Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
    

## Frequently Asked Questions

The Sprig Plugin for Craft CMS is a reactive Twig component framework for Craft CMS. Starting in version 2.0.0 and prior to versions 2.15.2 and 3.15.2, admin users, and users with explicit permission to access the Sprig Playground, could potentially expose the security key, credentials, and other sensitive configuration data, in addition to running the \`hashData()\` signing function. This issue was mitigated in versions 3.15.2 and 2.15.2 by disabling access to the Sprig Playground entirely when \`devMode\` is disabled, by default. It is possible to override this behavior using a new \`enablePlaygr

O3 Security · Impact-Aware SCA

### Is CVE-2026-27131 in your dependencies?

Find it across Packagist, including transitive dependencies.

[Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)