Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

GHSA-mm6v-68qp-f9fw islandora/crayfish

CRITICALFix: Islandora/Crayfish@64cb4ce

GHSA-mm6v-68qp-f9fw is a critical-severity (CVSS 9.8) CWE-150 vulnerability in islandora/crayfish. A fix is available for islandora/crayfish — see the affected versions and patch details below.

Crayfish allows Remote Code Execution via Homarus Authorization header

Also known asCVE-2025-25286
Published
Jan 15, 2025
Updated
Feb 13, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mm6v-68qp-f9fw.

EPSS Exploitation Probability

via FIRST.org ↗
1.0%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs62th percentile — riskier than 62% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-mm6v-68qp-f9fw plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

1 pkg affected
🐘islandora/crayfish

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistislandora/crayfishall versions4.1.0composer require islandora/crayfish:^4.1.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for islandora/crayfish, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update islandora/crayfish to 4.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mm6v-68qp-f9fw is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mm6v-68qp-f9fw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mm6v-68qp-f9fw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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
O3 Security · Impact-Aware SCA

Is GHSA-mm6v-68qp-f9fw in your dependencies?

O3 Security finds GHSA-mm6v-68qp-f9fw across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-mm6v-68qp-f9fw: RCE (Critical 9.8) | O3 Security