CVE-2025-53899 json
Kiteworks MFT is vulnerable to an Incorrectly Specified Destination in a Communication Channel
published 2025-11-29 11 mo ago modified 2026-10-07 32 d ago also EUVD-2025-199896
- cvss
- 7.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 63%
- public exploits
- 0
- none known
Summary
Kiteworks MFT orchestrates end-to-end file transfer workflows. Prior to version 9.1.0, the back-end of Kiteworks MFT is vulnerable to an incorrectly specified destination in a communication channel which allows an attacker with administrative privileges on the system under certain circumstances to intercept upstream communication which could lead to an escalation of privileges. This issue has been patched in version 9.1.0.
Patch / fix
- accellion kiteworks_managed_file_transfer 9.1.0
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 11 mo ago
Exploit prediction
1.00% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.2 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
Affected products
- kiteworks security-advisories
Classification
- Weakness
-
- CWE-941 Incorrectly Specified Destination in a Communication Channel
References
-
github.com
/kiteworks/security-advisories/security/advisories/GHSA-5gx5-vcpp-8cr5
patch, third-party-advisory
Sources
- CVE List CVE-2025-53899
- NVD CVE-2025-53899
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.