Is bagisto/bagisto affected by CVE-2026-21449?

Packagist bagisto/bagisto is affected in <2.3.10.

Is CVE-2026-21449 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

high

CVE-2026-21449

Q: Is CVE-2026-21449 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.5%.

Packagist · bagisto/bagisto

Summary

Bagisto is vulnerable to SSTI via name parameters provided by non-admin low-privilege users

Severity: high
EPSS: 0.5% (p36)
Also known as: GHSA-mqhg-v22x-pqj8
Published: 2026-01-02

References

Related advisories

CVE-2025-62417 — critical · Packagist/bagisto/bagisto
CVE-2026-21447 — high · Packagist/bagisto/bagisto
CVE-2026-21448 — high · Packagist/bagisto/bagisto
CVE-2026-21450 — high · Packagist/bagisto/bagisto
CVE-2026-21446 — high · Packagist/bagisto/bagisto
CVE-2025-60880 — high · Packagist/bagisto/bagisto
CVE-2026-21451 — medium · Packagist/bagisto/bagisto
CVE-2025-62414 — medium · Packagist/bagisto/bagisto

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.