CVE-2026-45756 in Symfony JSON Path
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. From 7.3.0-BETA1 until 7.4.12 and 8.0.12, the JsonPath component compiles attacker-controlled match() and search() filter patterns directly into preg_match()...
Quick answer
Symfony JSON Path should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- symfony/json-path >=7.3 <7.4.12
- symfony/json-path >=8.0 <8.0.12
Fixed versions
- symfony/json-path 7.4.12 or 8.0.12
How to fix it
Update Symfony JSON Path. The old package can let a bad request slow the app, pass a login check, or run unsafe data.
- Update symfony/json-path to symfony/json-path 7.4.12 or 8.0.12 with Composer.
- Run the app tests.
- Clear Symfony cache and deploy.
- Check the app logs after release.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Run composer show symfony/json-path and confirm the fixed version is installed.
- Scan again and confirm CVE-2026-45756 is gone.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-45756?
Symfony JSON Path versions listed as affected should be reviewed: symfony/json-path >=7.3 <7.4.12, symfony/json-path >=8.0 <8.0.12.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.