Skip to main content
CVE-2025-53899VulnerabilityPublished Updated

CVE-2025-53899: kiteworks security-advisories · Incorrectly Specified Destination in a Communication Channel

Affects kiteworks security-advisoriesSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High : upgrade to 9.1.0 soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 60% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 9.1.0
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade kiteworks/security-advisories to 9.1.0.

Affected software

ProductAffectedFixed in
GitHubkiteworks/security-advisoriespkg:github/kiteworks/security-advisoriesOther threatsAffected
  • <9.1.0
Fixed in
  • 9.1.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately verify their Kiteworks MFT version and upgrade to version 9.1.0 or later, where the vulnerability is patched. Restrict and monitor administrative access rigorously to reduce the risk of privilege abuse. Implement strong authentication mechanisms such as multi-factor authentication (MFA) for administrative accounts. Conduct regular audits of system logs and communication channels to detect any anomalous interception or privilege escalation attempts. Employ network segmentation to isolate Kiteworks MFT servers and limit exposure to untrusted networks. Use encryption for all communication channels to reduce the risk of interception even if the destination is incorrectly specified. Establish an incident response plan specifically addressing potential misuse of administrative privileges and communication interception. Finally, maintain up-to-date threat intelligence feeds to monitor for any emerging exploits targeting this vulnerability.

Description

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.

References

Community reviews

Loading reviews…