fish (aka fish-shell) 2.0.0 before 2.1.1 does not restrict access to the configuration service (aka fish_config), which allows remote attac…

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

cvss: 9.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.2%; EPSS 3.2% chance of exploitation in 30 days, percentile 88%
public exploits: 0; none known

fish (aka fish-shell) 2.0.0 before 2.1.1 does not restrict access to the configuration service (aka fish_config), which allows remote attackers to execute arbitrary code via unspecified vectors, as demonstrated by set_prompt.

Patch / fix

fixed in 1 distros 2

fishshell fish 2.1.1

debian opensuse

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

debian advisories DEBIAN-CVE-2014-2914

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-1 openSUSE-SU-2019:2188-1 openSUSE-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-2914 updated 2025-11-21 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

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

CVSS scores

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

Classification

Weakness

CWE-20 Improper Input Validation

References

github.com /fish-shell/fish-shell/issues/1438
third-party-advisory
openwall.com /lists/oss-security/2014/04/28/4
mailing-list, third-party-advisory

Sources

CVE List CVE-2014-2914
NVD CVE-2014-2914

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.

Summary