dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-55878

HIGH · 7.8 CVSS v3.1 Published 2026-07-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
81/100
Remediation priority · High
No privileges Patch available 6 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 UX is a JavaScript ecosystem for Symfony. From 2.32.0 before 2.36.1 and from 3.0.0 before 3.2.0, the ux:install console command installs files from a recipe kit by copying paths listed in a copy-files map, and because Path::isRelative() accepts paths like ../../../etc, a crafted or compromised kit can write attacker-controlled content to arbitrary locations or read local files outside the recipe directory. This issue is fixed in versions 2.36.1 and 3.2.0.

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

This is a path traversal vulnerability in Symfony UX's ux:install console command. The command installs files from a recipe kit using a copy-files map, but Path::isRelative() incorrectly accepts paths containing ../ sequences (e.g., ../../../etc), allowing a crafted or compromised kit to write attacker-controlled content to arbitrary locations or read sensitive files outside the recipe directory.

MitigationUpgrade Symfony UX to version 2.36.1 or 3.2.0 or later to patch the path traversal vulnerability in the ux:install command. Review any third-party or community recipe kits for malicious path entries.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify Symfony UX installation
    Run 'composer show symfony/ux-*' or check your composer.json for symfony/ux dependencies
    Affected if No Symfony UX packages are installed, so the ux:install command does not exist in your environment
  2. Check Symfony UX version
    Run 'composer show symfony/ux' or inspect the installed version in your vendor directory
    Affected if The installed version is below 2.36.1 or below 3.2.0 (compare your version to the affected ranges)
  3. Verify ux:install command availability
    Run 'php bin/console list' and look for 'ux:install' in the command list, or run 'php bin/console ux:install --help'
    Affected if The ux:install command is not available in your console, meaning Symfony UX is not installed or does not include this command
  4. Check for third-party recipe kits
    Inspect your project's recipes directory (typically config/recipes or vendor/symfony/recipes) for any custom or community-contributed recipe kits
    Affected if You have installed or are using third-party or community recipe kits that could contain malicious path entries in their copy-files maps

You are affected if you have Symfony UX installed with a version below 2.36.1 or below 3.2.0 AND use the ux:install command with third-party recipe kits containing ../ sequences in their copy-files maps.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade Symfony UX to version 2.36.1 or 3.2.0 or later to patch the path traversal vulnerability in the ux:install command. Review any third-party or community recipe kits for malicious path entries.

Recommended fix High confidence

2.36.1 for 2.x branch, 3.2.0 for 3.x branch

  1. Identify the currently installed Symfony UX version using composer show symfony/ux or checking your composer.json
  2. For Symfony UX 2.x versions (from 2.32.0 to 2.36.0): Run composer require symfony/ux:^2.36.1 to upgrade to the fixed version
  3. For Symfony UX 3.x versions (from 3.0.0 to 3.2.0): Run composer require symfony/ux:^3.2.0 to upgrade to the fixed version
  4. After upgrading, clear the Symfony cache with php bin/console cache:clear
  5. Verify the upgrade was successful by checking composer show symfony/ux
Caveat Minor version upgrade should be safe; ensure your Symfony core version is compatible with the UX version

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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