Is symfony/ux-live-component vulnerable?

Composer symfony/ux-live-component has 6 known advisories in the phpwarden feed. Feed 2026.10.29.4, updated 2026-10-29.

6advisories
0critical
0on CISA KEV
0no fix recorded
CVETitleSeverityCVSSAffectedFixed in
CVE-2026-49209symfony/ux-live-component: Denial of service via unbounded batch action requestslow0.0>=2.5.0 and <2.36.0 or >=3.0.0 and <3.1.02.36.0, 3.1.0
CVE-2026-49208ux-live-component: Format-less date LiveProps parsed with the permissive DateTime constructormedium0.0>=2.8.0 and <2.36.0 or >=3.0.0 and <3.1.02.36.0, 3.1.0
CVE-2026-49210symfony/ux-live-component: XSS via attacker-controlled child component tagmedium0.0>=2.8.0 and <2.36.0 or >=3.0.0 and <3.1.02.36.0, 3.1.0
CVE-2025-47946Symfony UX allows unsanitized HTML attribute injection via ComponentAttributesmedium6.1<2.25.12.25.1
CVE-2026-49212symfony/ux-live-component: LiveComponentHydrator HMAC checksum lacks component and slot bindinglow0.0>=2.8.0 and <2.36.0 or >=3.0.0 and <3.1.02.36.0, 3.1.0
CVE-2026-49215symfony/ux-live-component: CSRF Protection Bypass — Accept Header is CORS-Safelistedlow0.0>=2.22.0 and <2.36.0 or >=3.0.0 and <3.1.02.36.0, 3.1.0

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.