dbcve.org
SymfonyFramework / library · Sensiolabs

CVE-2026-45073

HIGH · 7.3 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 5.4.52 / 6.4.40 or later.
See remediation →
82/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. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, PdoAdapter::doClear() builds a DELETE statement using a namespace derived from the caller-supplied $prefix without binding or escaping it, allowing a caller able to influence $prefix to break out of the LIKE literal and alter query semantics or deletion scope. This issue is fixed in versions 5.4.52, 6.4.40, 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

PdoAdapter::doClear() in Symfony builds a DELETE statement using a caller-supplied $prefix parameter without proper binding or escaping. An attacker who can influence the $prefix value can escape the LIKE literal and alter query semantics, potentially causing unauthorized data deletion or scope manipulation. This is a SQL injection vulnerability in the session storage component.

MitigationUpgrade Symfony to version 5.4.52, 6.4.40, 7.4.12, or 8.0.12 or later. If upgrading is not immediately possible, review code that uses PdoAdapter and ensure no user-controlled input can reach the $prefix parameter.

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:< 5.4.52>= 6.0.0, < 6.4.40>= 7.0.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
Low
Integrity
Low
Availability
Low

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

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. Check Symfony version
    Identify the installed Symfony version in your project (commonly found in composer.json or the Symfony version file under vendor/symfony) and compare it against the affected ranges: < 5.4.52, >= 6.0.0 && < 6.4.40, >= 7.0.0 && < 7.4.12, >= 8.0.0 && < 8.0.12
    Affected if Your installed version falls within any of the affected version ranges
  2. Determine if PdoAdapter is used for sessions
    Examine your Symfony session configuration for a handler using PdoAdapter, typically configured in framework.session.handler.id or similar session config setting
    Affected if PdoAdapter is configured as the session handler
  3. Check session handler configuration
    Locate the PdoAdapter service definition and inspect how the $prefix parameter is set, looking for any configuration that could be influenced by user input
    Affected if The $prefix parameter in the session handler configuration can be controlled or influenced by external input

You are affected if running a vulnerable Symfony version AND using PdoAdapter with a $prefix that can be influenced by user-controlled input.

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 5.4.52 / 6.4.40 / 7.4.12 or later
Fixed in 5.4.526.4.407.4.12
Interim mitigation

Upgrade Symfony to version 5.4.52, 6.4.40, 7.4.12, or 8.0.12 or later. If upgrading is not immediately possible, review code that uses PdoAdapter and ensure no user-controlled input can reach the $prefix parameter.

Recommended fix High confidence

Upgrade to Symfony 5.4.52, 6.4.40, 7.4.12, or 8.0.12 (whichever matches your current major version branch)

  1. 1. Identify your current Symfony version by running `composer show symfony/symfony` or checking your composer.json
  2. 2. Determine which upgrade path applies: if on 5.x go to 5.4.52; if on 6.x go to 6.4.40; if on 7.x go to 7.4.12; if on 8.x go to 8.0.12
  3. 3. Update your composer.json: run `composer require symfony/symfony:^5.4.52 --no-interaction` (or appropriate version for your branch)
  4. 4. Run `composer update symfony/symfony --with-all-dependencies` to install the patched version
  5. 5. Clear your application cache: `php bin/console cache:clear` or `php bin/console cache:clear --env=prod`
  6. 6. Run your test suite and verify the application functions correctly
Caveat Check Symfony's UPGRADE notes for your version branch for any breaking changes; minor version upgrades typically have minimal breaking changes

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

Fix this in Symfony Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
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,832.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45073 — 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-45073 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