← Back
CVE-2026-49212
Vulnerability in symfony/ux-live-component (CVE-2026-49212)
Summary
vulnerability in symfony/ux-live-component (CVE-2026-49212). Risk of unauthorized operations or information disclosure. Exploitable via ``propsFromParent``. Mitigation: upgrade to `3.1.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49212** has been found in symfony/ux-live-component.
Attackers can target a specific entry point like ``propsFromParent`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade symfony/ux-live-component to **3.1.0** or later.
If unsure, ask your IT team or search "symfony/ux-live-component CVE-2026-49212" on the vendor's site.
CVE-2026-49212 (symfony/ux-live-component) — CWE-345 /
Attack surface: `propsFromParent` / `props` / `CHECKSUM_SLOT_PROPS` / `CHECKSUM_SLOT_PROPS_FROM_PARENT`
Patched: `3.1.0` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-345) exists in symfony/ux-live-component. Attackers reach the vulnerable code path via ``propsFromParent`` without authentication.
📍 Affected scope
symfony/ux-live-component — . Attack surface: `propsFromParent` / `props` / `CHECKSUM_SLOT_PROPS` / `CHECKSUM_SLOT_PROPS_FROM_PARENT`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.1.0**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'symfony/ux-live-component' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'symfony/ux-live-component' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `symfony/ux-live-component` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade symfony/ux-live-component to 3.1.0ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
composer
symfony/ux-live-component
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]
References
- web https://github.com/symfony/ux/security/advisories/GHSA-34w5-c283-j9fg
- web https://github.com/symfony/ux/commit/a224b5af3e2e33ee14ac71356ae0e0877900a81c
- web https://github.com/FriendsOfPHP/security-advisories/blob/master/symfony/ux-live-component/CVE-2026-49212.yaml
- web https://github.com/advisories/GHSA-34w5-c283-j9fg