Is symfony/twig-bridge vulnerable?

Composer symfony/twig-bridge has 2 known advisories in the phpwarden feed. Feed 2026.10.29.3, updated 2026-10-29.

2advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2023-46734Symfony potential Cross-site Scripting vulnerabilities in CodeExtension filtersmedium6.1>=2.0.0 and <4.4.51 or >=5.0.0 and <5.4.31 or >=6.0.0 and <6.3.8 or >=2.0.0 and <2.1.0 or >=2.1.0 and <2.2.0 or >=2.2.0 and <2.3.0 or >=2.3.0 and <2.4.0 or >=2.4.0 and <2.5.0 or >=2.5.0 and <2.6.0 or >=2.6.0 and <2.7.0 or >=2.7.0 and <2.8.0 or >=2.8.0 and <3.0.0 or >=3.0.0 and <3.1.0 or >=3.1.0 and <3.2.0 or >=3.2.0 and <3.3.0 or >=3.3.0 and <3.4.0 or >=3.4.0 and <4.0.0 or >=4.0.0 and <4.1.0 or >=4.1.0 and <4.2.0 or >=4.2.0 and <4.3.0 or >=4.3.0 and <4.4.0 or >=4.4.0 and <4.4.51 or >=5.0.0 and <5.1.0 or >=5.1.0 and <5.2.0 or >=5.2.0 and <5.3.0 or >=5.3.0 and <5.4.0 or >=5.4.0 and <5.4.31 or >=6.0.0 and <6.1.0 or >=6.1.0 and <6.2.0 or >=6.2.0 and <6.3.0 or >=6.3.0 and <6.3.84.4.51, 5.4.31, 6.3.8
CVE-2026-45072Symfony Vulnerable to stored XSS in WebProfiler CodeExtension::fileExcerpt() — Unescaped Non-PHP File Renderinglow0.0>=6.4.24 and <6.4.406.4.40

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs   How findings are ranked
A version is vulnerable when it falls inside an affected range and below the fixed version. phpwarden applies these ranges to the exact versions in your lockfile or install, so you only see what applies to you.