# CVE-2025-25286: Crayfish allows Remote Code Execution via Homarus Authorization header

> Remote attackers can execute arbitrary code on Homarus microservices via the Authorization header if the service is web-accessible and improperly configured.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Feb 2025
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-mm6v-68qp-f9fw

## What is CVE-2025-25286?

CVE-2025-25286 is a critical command injection vulnerability in Islandora Crayfish, published on 13 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

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

## Which versions are affected by CVE-2025-25286?

2 open source packages ship an affected version, including islandora/crayfish.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `islandora/crayfish` | Packagist | All versions | 4.1.0 |
| `islandora/crayfish` | Packagist | All versions | 4.1.0 |

## How do I fix CVE-2025-25286?

Upgrade islandora/crayfish to 4.1.0 or later.

## Is CVE-2025-25286 being exploited?

There is no known exploitation of CVE-2025-25286 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-25286 and fix it if it is affected.

What it is: CVE-2025-25286 is a critical command injection vulnerability in Islandora Crayfish, published on 13 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-25286 in the wild and no public exploit code.

Affected packages and fixed versions:
- islandora/crayfish (Packagist): affected all versions; fixed in 4.1.0
- islandora/crayfish (Packagist): affected all versions; fixed in 4.1.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-25286/ (Markdown: https://insights.sbomify.com/CVE-2025-25286/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-25286
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-25286
- OSV: https://osv.dev/vulnerability/CVE-2025-25286

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-25286/
Summaries are generated and may contain mistakes; the official description above is the record.