Advisory record · GHSA-mm6v-68qp-f9fw

Crayfish allows Remote Code Execution via Homarus Authorization header

CVSS 9.8 CriticalCriticalEPSS 0.010 · 63rd percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 15 Jan 2025, 22:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
islandora/crayfishPackagist<4.1.04.1.0
Identifiers
GHSA-mm6v-68qp-f9fw · CVE-2025-25286 · PKSA-y8f8-ggcf-nysv
Weakness (CWE)
CWE-150 · CWE-157
Published
15 Jan 2025
Updated
13 Feb 2025

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Crayfish (islandora/crayfish) versions before 4.1.0 are vulnerable to remote code execution in web-accessible installations of Homarus in certain configurations. An attacker who can send requests to Homarus's /convert endpoint, which is reachable over the network, may be able to run code on the server through the Authorization header. Upgrade islandora/crayfish to 4.1.0 or later. Until then, block general Internet access to Homarus and configure Crayfish to reject requests with invalid Authorization headers before they reach the vulnerable processing step.

Written 4 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.010, the 63rd percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:27 UTC First seen by agentprime
  2. 31 Oct 2026, 14:27 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.