CVE-2025-13590
Admin can upload arbitrary file via REST API, enabling RCE.
Is CVE-2025-13590 being exploited?
Not confirmed. CVE-2025-13590 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.68% probability of exploitation in the next 30 days.
How severe is CVE-2025-13590?
CVE-2025-13590 is rated Critical with a CVSS score of 9.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-13590?
Yes. A fix has been recorded for CVE-2025-13590. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-13590 affect?
CVE-2025-13590 affects Unspecified REST API deployments. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2025-13590?
Plan patch; restrict admin REST API access; rotate admin credentials; monitor.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted payload uploaded to a user-controlled path through REST API.
Patch when possible
- affected>= 9.28.116 and < 9.28.116.391
- affected>= 9.29.120 and < 9.29.120.210
- affected>= 9.30.67 and < 9.30.67.133
- affected>= 9.31.86 and < 9.31.86.100
- affected>= 9.32.147 and < 9.32.147.2
- affected< 4.5.0
- affected>= 4.5.0 and < 4.5.0.39
- affected>= 4.6.0 and < 4.6.0.3
- affected>= 4.2.0 and < 4.2.0.179
- affected>= 4.3.0 and < 4.3.0.91
- affected>= 4.4.0 and < 4.4.0.55
- affected>= 4.5.0 and < 4.5.0.38
- affected>= 4.6.0 and < 4.6.0.3
- affected< 4.5.0
- affected>= 4.5.0 and < 4.5.0.37
- affected>= 4.6.0 and < 4.6.0.3
- affected< 4.5.0
- affected>= 4.5.0 and < 4.5.0.37
- affected>= 4.6.0 and < 4.6.0.3
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.