Skip to main content
VulnerabilityPublished

CVE-2026-55878: symfony ux · Path Traversal

Affects symfony uxSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.8 High : upgrade to 3.2.0 or 2.36.1 soon.

Data as of 20 Nov 2026, 17:35 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.2.0, 2.36.1
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 8 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Upgrade symfony ux to 3.2.0 or 2.36.1.

Affected software

ProductAffectedFixed in
symfonyuxAffected
  • >=3.0.0 <3.2.0
Fixed in
  • 3.2.0
symfonyuxAffected
  • >=2.32.0 <2.36.1
Fixed in
  • 2.36.1
GitHubsymfony/uxpkg:github/symfony/uxOther threatsAffected
  • 2.32.0 – 3.2.0
4 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Symfony UX to version 2.36.1 or later if using the 2.x branch, or to version 3.2.0 or later if using the 3.x branch. These versions contain the official fix for this path traversal vulnerability. No other mitigations are indicated by the vendor advisory.

Description

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.

References

Community reviews

Loading reviews…