Skip to content
Fencer Intel
high 7.0

CVE-2014-2906 json

The psub function in fish (aka fish-shell) 1.16.0 before 2.1.1 does not properly create temporary files, which allows local users to execut…

published 2020-01-28 6 y ago modified 2026-06-17 4 mo ago also EUVD-2014-2929

cvss
7.0
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 24%
public exploits
0
none known

Summary

The psub function in fish (aka fish-shell) 1.16.0 before 2.1.1 does not properly create temporary files, which allows local users to execute arbitrary commands via a temporary file with a predictable name.

Patch / fix

  • fishshell fish 2.1.1
  • fish Debian 14, Debian 13, Debian 12 2.1.1-1

debian advisories DEBIAN-CVE-2014-2906

  • fish openSUSE Tumbleweed 2.4.0-1.1
  • fish3 openSUSE Leap 15.1 3.0.0-lp151.2.1
  • fish3 openSUSE Leap 15.0 3.0.0-lp150.3.1

opensuse advisories openSUSE-SU-2024:10348-1openSUSE-SU-2019:2188-1openSUSE-SU-2019:2177-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2014-2906 updated cvss 7.2

fish: multiple flaws fixed in upstream 2.1.1

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.0 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.4 AV:L/AC:M/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.