CVE-2025-25286
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2025-25286 is a critical-severity Improper Neutralization of Escape, Meta, or Control Sequences (CWE-150) vulnerability. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Command and Scripting Interpreter (T1059); ranked in the top 40% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Crayfish is a collection of Islandora 8 microservices, and the Homarus component exposes FFmpeg functionality via a web endpoint. Prior to version 4.1.0, the service performed insufficient validation of input supplied to the /convert endpoint, allowing command-line argument interpolation that could be abused for remote code execution when the microservice was reachable over the network. The vulnerability is tracked as CVE-2025-25286 with a CVSS 3.1 score of 9.8 and is associated with CWE-150 and CWE-157.
An unauthenticated remote attacker can send a crafted request directly to the Homarus /convert endpoint and achieve arbitrary command execution on the underlying host, resulting in full confidentiality, integrity, and availability impact. Exploitation requires the microservice to be web-accessible and does not depend on user interaction or authentication in the vulnerable configurations.
The issue is fixed in islandora/crayfish:4.1.0. The published advisory recommends either blocking unauthenticated Internet access to Homarus entirely or enforcing stricter authorization checks so that requests containing invalid Authorization headers are rejected before any CLI interpolation occurs. The associated commit and GitHub Security Advisory provide the patch details.
EPSS for the CVE remains low and unchanged at 0.0438 with no observed upward trajectory after disclosure.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-0100
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.2.10V1.3.12
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validation/sanitization of inputs that directly stops escape/meta/control sequences from reaching downstream components.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require input neutralization and escaping to prevent this class of flaw.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect the weakness but does not itself implement neutralization.
Secure development lifecycle mandates input validation and output encoding that directly neutralizes escape/meta sequences.
Application security requirements explicitly call for controls against injection and malformed input sequences.
Secure architecture principles reduce attack surface but do not prescribe specific neutralization techniques.
Secure coding standards require proper escaping and neutralization of control characters before downstream processing.