dbcve.org
SymfonyFramework / library · Sensiolabs

CVE-2026-45756

HIGH · 7.5 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 7.4.12 / 8.0.12 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 5 weeks old

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 · unedited
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() without a length cap, i-regexp restriction, or bounded backtracking, allowing catastrophic-backtracking expressions to pin worker CPU and cause denial of service. This issue is fixed in versions 7.4.12 and 8.0.12.

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 confidence

The Symfony JsonPath component allows attacker-controlled regex patterns in match() and search() filter functions to be compiled directly into preg_match() without length limits, regexp restrictions, or backtracking bounds, enabling catastrophic backtracking that exhausts CPU and causes denial of service.

MitigationUpgrade Symfony to version 7.4.12 or 8.0.12 which contains the fix, or implement input validation and regex complexity limits before passing patterns to preg_match.

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
SymfonyFramework / library
Affected:>= 7.3.0, < 7.4.12>= 8.0.0, < 8.0.12

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Symfony version
    Run 'composer show symfony/framework-bundle' or check your composer.lock file for the symfony/framework-bundle or symfony/json-path package version
    Affected if The version is >= 7.3.0 and < 7.4.12, or >= 8.0.0 and < 8.0.12
  2. Confirm JsonPath component is present
    Run 'composer show symfony/json-path' to verify the JsonPath component is installed as a dependency
    Affected if The JsonPath component is installed and its version matches the vulnerable Symfony version range
  3. Identify JsonPath usage in code
    Search codebase for usages of JsonPath methods, particularly 'match()' and 'search()' filter functions. Search for patterns like '$jsonPath->match(' or 'JsonPath::search('
    Affected if Code uses JsonPath match() or search() methods with patterns derived from user input
  4. Determine if regex patterns are user-controlled
    Trace the pattern argument passed to match() or search() calls. Check if it originates from request parameters, user-provided JSON data, or external input sources
    Affected if The regex pattern passed to match() or search() is derived from untrusted user input without validation

You are affected if your Symfony version is within 7.3.0 to 7.4.11 or 8.0.0 to 8.0.11, AND your application passes user-supplied input as regex patterns to JsonPath match() or search() functions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.4.12 / 8.0.12 or later
Fixed in 7.4.128.0.12
Interim mitigation

Upgrade Symfony to version 7.4.12 or 8.0.12 which contains the fix, or implement input validation and regex complexity limits before passing patterns to preg_match.

Recommended fix High confidence

Upgrade to Symfony 7.4.12 (for 7.x line) or 8.0.12 (for 8.x line)

  1. 1. Identify the current Symfony JsonPath component version in your project (check composer.json or composer.lock)
  2. 2. Update the symfony/jsonpath-bridge or symfony/framework-bundle (depending on how JsonPath is integrated) to version 7.4.12 for Symfony 7.x or 8.0.12 for Symfony 8.x
  3. 3. Run 'composer update symfony/jsonpath-bundle' or 'composer update' to apply the changes
  4. 4. Verify the updated version is installed: 'composer show symfony/jsonpath-bundle'
  5. 5. Test that the JsonPath component's match() and search() functions work correctly with your existing test suite
Caveat Minimal risk - this is a security patch; however, test your JsonPath usage to ensure the bounded backtracking does not affect legitimate regex patterns

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Symfony Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45756 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45756 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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