CVE-2026-102097: Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Remote Code Execution

Q: How do I fix CVE-2026-102097?

kiteworks: upgrade to 9.5.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-102097 being exploited?

CVE-2026-102097 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-102097 affect?

CVE-2026-102097 affects kiteworks. Severity is high (CVSS 7.2). Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Remote Code Execution. Kiteworks Email Protection Gateway allowed an authenticated administrator to import configuration whose contents were not sufficiently validated

This month

HIGH 7.2UPGRADE

CVE-2026-102097 is a high-severity flaw (CVSS 7.2) affecting kiteworks. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Remote Code Execution. Kiteworks Email Protection Gateway allowed an authenticated administrator to import configuration whose contents were not sufficiently validated before being processed. A crafted submission could potentially allow arbitrary commands to be executed on the affected gateway.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	2.2% (top 18%)
CISA exploited list	No
Weakness	CWE-22, CWE-94
Published	2026-09-30
Last modified	2026-10-08

Publisher (CNA): Cybersecurity and Infrastructure Security Agency (CISA) U.S. Civilian Government · Vendor: accellion

Last updated 2026-10-08 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-09-30 21:16 UTCPublished CVE record published
2026-10-08 13:43 UTCUpdated Record last modified

accellion kiteworks UPGRADE

Affected: < 9.5.0

Fixed in: 9.5.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy kiteworks || rpm -q kiteworks || kiteworks --version

2. UPGRADE to 9.5.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade kiteworks

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade kiteworks

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-102097?

kiteworks: upgrade to 9.5.0. Exact commands for each OS are on this page.

Is CVE-2026-102097 being exploited?

CVE-2026-102097 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-102097 affect?

CVE-2026-102097 affects kiteworks. Severity is high (CVSS 7.2). Kiteworks Email Protection Gateway before version 9.5.0 is vulnerable to Remote Code Execution. Kiteworks Email Protection Gateway allowed an authenticated administrator to import configuration whose contents were not sufficiently validated

How urgent is CVE-2026-102097?

Priority 46/100. High severity

Related CVEs

CVE-2026-102110 MEDIUM 5.9 UPGRADE An endpoint used during initial appliance setup did not require authentication and did not correctly enforce i
CVE-2026-102117 HIGH 7.2 UPGRADE On deployments where the remote-support capability is licensed and enabled, an authenticated System Administra
CVE-2026-102119 HIGH 7.2 UPGRADE A path traversal weakness in an optional, non-default administrative feature allowed an authenticated administ
CVE-2026-102136 MEDIUM 6.3 UPGRADE In multi-node deployments, an attacker who had already obtained code execution on one appliance node could sub
CVE-2026-102137 MEDIUM 4.1 UPGRADE An authenticated administrator could bypass the content validation applied to an administrative file upload an

References

← Back to latest CVEs