SymfonyFramework / library · Sensiolabs
CVE-2026-45064
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 · uneditedSymfony is a PHP framework for web and console applications and a set of reusable PHP components. From 6.1.0-BETA1 until 6.4.40, 7.4.12, and 8.0.12, UrlSanitizer::parse() passes Unicode explicit-direction BiDi formatting characters through into sanitized href and src attributes, allowing sanitized content to display a link destination that visually differs from the actual destination and enabling phishing-style visual spoofing. This issue is fixed in versions 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 confidenceSymfony's UrlSanitizer::parse() method fails to filter Unicode explicit-direction BiDi formatting characters from href and src attributes, allowing attackers to craft URLs that display differently than their actual destination, enabling phishing through visual spoofing.
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
>= 6.1.0, < 6.4.40>= 7.0.0, < 7.4.12>= 8.0.0, < 8.0.12CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Symfony is in useCheck your project's composer.json for 'symfony/symfony' or look for the Symfony framework in your vendor directory by searching for the vendor/symfony folderAffected if Symfony framework is not present in the project
-
Determine installed Symfony versionRun 'composer show symfony/symfony' or check the version field in composer.lock under the symfony/symfony package entryAffected if Version is >= 6.1.0 and < 6.4.40, OR >= 7.0.0 and < 7.4.12, OR >= 8.0.0 and < 8.0.12
-
Check if UrlSanitizer is being usedSearch your codebase for usage of UrlSanitizer::parse() method, typically in files that process URLs from untrusted input such as user-submitted href or src attributes in HTML contentAffected if The UrlSanitizer::parse() method is being called on URLs extracted from href or src attributes from potentially untrusted sources
If your Symfony version falls within any of the affected ranges AND your application uses UrlSanitizer::parse() to process URLs from untrusted input in href or src attributes, your environment is vulnerable to BiDi character injection.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.4.407.4.128.0.12
Upgrade Symfony to versions 6.4.40, 7.4.12, 8.0.12 or later to receive the BiDi character filtering fix.
Upgrade to Symfony 6.4.40, 7.4.12, or 8.0.12 depending on your current branch
- 1. Identify the currently installed Symfony version using `composer show symfony/symfony` or checking your composer.lock file
- 2. Determine which version branch you are on (6.x, 7.x, or 8.x)
- 3. Run `composer require symfony/symfony:6.4.40 --no-interaction` if on 6.x branch
- 4. Run `composer require symfony/symfony:7.4.12 --no-interaction` if on 7.x branch
- 5. Run `composer require symfony/symfony:8.0.12 --no-interaction` if on 8.x branch
- 6. Run `composer update symfony/symfony --with-all-dependencies` to update and resolve dependencies
- 7. Run your test suite to verify the application functions correctly after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Symfony
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45064 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-45064 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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