CVE-2026-28269
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedKiteworks is a private data network (PDN). Prior to version 9.2.0, avulnerability in Kiteworks command execution functionality allows authenticated users to redirect command output to arbitrary file locations. This could be exploited to overwrite critical system files and gain elevated access. Version 9.2.0 contains a patch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceKiteworks prior to version 9.2.0 contains a command execution vulnerability where authenticated users can redirect command output to arbitrary file locations. This path traversal in command handling allows overwriting critical system files, leading to privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 9.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Kiteworks installationIdentify if Accellion Kiteworks is deployed in your environment by reviewing installed applications, service listings, or documentation of enterprise softwareAffected if Kiteworks is installed and the version is below 9.2.0
-
Determine installed Kiteworks versionAccess the Kiteworks admin interface or check system documentation to locate the currently installed version numberAffected if The installed version is lower than 9.2.0 (for example, 9.1.x, 9.0.x, or earlier)
-
Identify command execution functionalityLocate the command execution feature within Kiteworks by reviewing admin panels, feature documentation, or available modulesAffected if The command execution functionality exists and is accessible to authenticated users
-
Check for path traversal indicatorsReview command execution logs, audit trails, or shell history for redirection operators (such as >, >>, 2>) being used with user-supplied paths pointing outside expected directoriesAffected if Logs show command redirection to unexpected file paths, especially system directories or configuration files
-
Inspect critical system files for unauthorized modificationsCompare current versions of system files, configuration files, and startup scripts against known-good baselines or integrity checking toolsAffected if Critical system files have been modified or created without documented change approval
You are affected if Kiteworks version is below 9.2.0 and the command execution feature is accessible to authenticated users in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.2.0
Upgrade to Kiteworks version 9.2.0 or later. Until then, restrict command execution permissions and monitor for unauthorized file modifications.
Kiteworks version 9.2.0
- Upgrade Kiteworks to version 9.2.0 or later to remediate the command injection vulnerability
- Verify the upgrade was successful by checking the Kiteworks version after installation
- Test that the command execution functionality works correctly post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-28269 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-28269 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data