CVE-2026-9863
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 · uneditedFortra BoKS Manager contains an OS command injection vulnerability in the client upgrade and patch tooling for legacy tar-based client installations. A malicious or compromised legacy tar-installed client selected for upgrade or patching may be able to cause commands to be executed on the BoKS Master during client version handling.
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 confidenceFortra BoKS Manager has an OS command injection vulnerability in the client upgrade and patch tooling for legacy tar-based client installations. A compromised legacy tar-installed client can inject and execute arbitrary OS commands on the BoKS Master server during client version handling operations.
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>= 8.1.0.0, < 8.1.0.23>= 9.0.0.0, < 9.0.0.5CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Identify Fortra Core PAM / BoKS Manager installation and versionLocate the BoKS Manager installation directory and check the version file or use the product's version command (e.g., 'boks -version' or check /opt/boksm/version). Compare your installed version against the affected ranges: 8.1.0.0-8.1.0.22 or 9.0.0.0-9.0.0.4.Affected if Your installed version falls within either 8.1.0.0 through 8.1.0.22 or 9.0.0.0 through 9.0.0.4.
-
Determine if legacy tar-based client deployment is in useExamine your BoKS client configuration to identify how clients are deployed. Check for tar archive-based client installations (legacy mode) versus modern agent-based deployments. Look for tar distribution files or legacy client package structures in the BoKS infrastructure.Affected if You have any clients installed using the legacy tar-based method rather than the modern agent installation approach.
-
Check if client upgrade/patch functionality is enabledReview BoKS Manager configuration files and settings related to client upgrade and patch operations. Look for configuration options that enable or control the upgrade/patch tooling for legacy tar-installed clients.Affected if The legacy tar-client upgrade and patch functionality is enabled or available in your environment.
-
Review recent client upgrade and patch activityExamine BoKS audit logs and system logs for any recent client upgrade or patch operations, particularly those targeting legacy tar-based clients. Look for upgrade requests, patch applications, or client version changes.Affected if Any legacy tar-based client upgrade or patch operations have been performed recently in your environment.
You are affected if your Fortra Core Privileged Access Manager version is 8.1.0.0-8.1.0.22 or 9.0.0.0-9.0.0.4 AND you have legacy tar-based clients that can be selected for upgrade or patching operations.
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 · scoped8.1.0.239.0.0.5
Avoid selecting untrusted or potentially compromised legacy tar-installed clients for upgrade/patching; implement strict input validation and sanitization in the client version handling logic; consider migrating away from legacy tar-based client installations.
Core Privileged Access Manager 8.1.0.23+ or 9.0.0.5+ (latest stable release recommended)
- Identify the currently installed Core Privileged Access Manager version using 'boks -v' or checking the version in the admin console
- If running version 8.1.0.0 through 8.1.0.22, plan upgrade to version 8.1.0.23 or later
- If running version 9.0.0.0 through 9.0.0.4, plan upgrade to version 9.0.0.5 or later
- Before upgrading, review Fortra's upgrade documentation and release notes for any prerequisites
- Backup the current BoKS configuration and database
- Schedule a maintenance window as upgrades may require brief service interruption
- Download the appropriate upgrade package from Fortra's customer portal at www.fortra.com
- Execute the upgrade following Fortra's documented upgrade procedure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9863 — 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-9863 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