Crayfish allows Remote Code Execution via Homarus Authorization header

published 2025-01-15 21 mo ago modified 2026-06-17 4 mo ago also GHSA-mm6v-68qp-f9fw , EUVD-2025-0100

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

Crayfish is a collection of Islandora 8 microservices, one of which, Homarus, provides FFmpeg as a microservice. Prior to Crayfish version 4.1.0, remote code execution may be possible in web-accessible installations of Homarus in certain configurations. The issue has been patched in `islandora/crayfish:4.1.0`. Some workarounds are available. The exploit requires making a request against the Homarus's `/convert` endpoint; therefore, the ability to exploit is much reduced if the microservice is not directly accessible from the Internet, so: Prevent general access from the Internet from hitting Homarus. Alternatively or additionally, configure auth in Crayfish to be more strongly required, such that requests with `Authorization` headers that do not validate are rejected before the problematic CLI interpolation occurs.

Patch / fix

fixed in 1 links 1

packagist islandora/crayfish 4.1.0

github.com/Islandora/Crayfish@64cb4ce commit

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: total
Assessed: 20 mo ago (2025-02-13)

Exploit prediction

1.02% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	9.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
packagist	islandora/crayfish	<4.1.0	4.1.0

Affected products

Islandora Crayfish

Classification

Weakness

CWE-150 Improper Neutralization of Escape, Meta, or Control Sequences
CWE-157 Failure to Sanitize Paired Delimiters

References

Sources

Fencer Vulns 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