dbcve.org
KiteworksApplication · Accellion

CVE-2026-28271

MEDIUM · 6.5 CVSS v3.1 Published 2026-02-27
Fix available
A fix is available. Upgrade to 9.2.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Kiteworks is a private data network (PDN). Prior to version 9.2.0, a vulnerability in Kiteworks configuration functionality allows bypassing of SSRF protections through DNS rebinding attacks. Malicious administrators could exploit this to access internal services that should be restricted. Version 9.2.0 contains a patch for the issue.

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 confidence

Kiteworks prior to version 9.2.0 contains a vulnerability in its configuration functionality where SSRF (Server-Side Request Forgery) protections can be bypassed using DNS rebinding attacks. This allows a malicious administrator to access internal services that should be restricted from external or privileged access.

MitigationUpgrade Kiteworks to version 9.2.0 or later to apply the patch. Additionally, review internal service access controls and implement DNS rebinding protections at the network level as defense-in-depth.

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
KiteworksApplication
Affected:< 9.2.0

CVSS 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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Kiteworks installation version
    Locate the Kiteworks installation and retrieve its version number from the system configuration, about page, or version file typically found in the installation directory
    Affected if The installed version is below 9.2.0 (e.g., 9.1.x, 9.0.x, earlier versions)
  2. Verify configuration functionality is enabled
    Check whether the Kiteworks configuration interface or API endpoints are accessible and enabled in the current deployment
    Affected if Configuration functionality is exposed and the version is below 9.2.0
  3. Confirm network exposure of configuration features
    Review network access controls to determine if the configuration functionality can be reached from external networks or by untrusted users
    Affected if Configuration features are network-accessible and the version is below 9.2.0
  4. Assess internal service access controls
    Inspect the system's internal service access policies to identify whether internal resources are intended to be protected from configuration-based requests
    Affected if Internal services lack additional network-level protections and the Kiteworks version is below 9.2.0

The environment is affected if the installed Kiteworks version is any release prior to 9.2.0 and the configuration functionality is accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.2.0 or later
Fixed in 9.2.0
Interim mitigation

Upgrade Kiteworks to version 9.2.0 or later to apply the patch. Additionally, review internal service access controls and implement DNS rebinding protections at the network level as defense-in-depth.

Recommended fix High confidence

Kiteworks 9.2.0

  1. 1. Backup the current Kiteworks installation and configuration
  2. 2. Consult Kiteworks upgrade documentation for your current version
  3. 3. Perform the upgrade to version 9.2.0 following standard upgrade procedures
  4. 4. Verify the upgrade was successful
  5. 5. Test that SSRF protections are functioning correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Kiteworks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-28271 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-28271 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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