Crayfish allows Remote Code Execution via Homarus Authorization header

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2025-25286: 1.02% estimated exploitation activity in the next 30 days; percentile 63.55 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Remote code execution may be possible in web-accessible installations of Homarus in certain configurations. Patches The issue has been patched in islandora/crayfish:4.1.0 Workarounds 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. 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. References - XBOW-024-071

Published by the source

15 Jan 2025, 22:04 UTC

Last modified by the source

13 Feb 2025, 16:49 UTC

Source last checked

26 Oct 2026, 14:29 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mm6v-68qp-f9fw

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-25286

Advisory: Crayfish allows Remote Code Execution via Homarus Authorization header
IDs: CVE-2025-25286, GHSA-mm6v-68qp-f9fw
Record: https://patchnext.com/advisories/cve-2025-25286 (revision 1, source checked 26 Oct 2026, 14:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: islandora/crayfish 4.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist islandora/crayfish: affected < 4.1.0; fixed in 4.1.0

## Suggested inspection (read-only)
- Packagist islandora/crayfish: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on islandora/crayfish.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-mm6v-68qp-f9fw (GitHub-reviewed advisory GHSA-mm6v-68qp-f9fw lists affected ranges: Packagist islandora/crayfish >=0 <4.1.0)

Commands are suggestions: review each one before running it.