Skip to main content

Fortra BoKS CVE-2026-12627

| EUVDEUVD-2026-90882 CRITICAL
Stack-based Buffer Overflow (CWE-121)
2026-10-01 Fortra GHSA-q8pc-64j3-359r
9.8
CVSS 3.1 · Vendor: Fortra
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Reach autoregistration service over network
  2. Delivery
    Initiate client autoregistration handshake
  3. Exploit
    Send malformed client response
  4. Execution
    Overflow stack buffer in boks_autoregisterd
  5. Persist
    Corrupt memory / hijack control flow
  6. Impact
    Execute code or crash privileged daemon

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires network access to the BoKS autoregistration service (boks_autoregisterd) and the ability to participate in or spoof the client autoregistration handshake so that an attacker-controlled 'client response' is parsed by the daemon. Per CVSS PR:N/UI:N no authentication or user interaction is needed, but exploitation is practically limited to networks where this enrollment service is reachable - typically the internal management/agent network rather than the public internet - and reliable code execution (versus a daemon crash/DoS) depends on defeating standard stack-overflow mitigations. No special product configuration is cited beyond the autoregistration service being enabled and listening.

Impact

This is a genuine high-priority issue on the signals available. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H = 9.8) describes remote, unauthenticated, low-complexity memory corruption in boks_autoregisterd, and the description aligns cleanly with that vector - the autoregistration service is network-reachable and processes attacker-influenced 'client response' data, so there is no AV/PR contradiction to flag. CWE-121 (stack-based buffer overflow) is a classic code-execution primitive, and because this daemon is part of a BoKS Master/replica enrollment path it typically runs with high privilege, making the C:H/I:H/A:H rating credible rather than inflated. However, no EPSS probability, no CISA KEV listing, and no public POC are present in the input, so there is currently no evidence of active or automated exploitation - the 9.8 reflects potential impact, not observed in-the-wild activity. Real-world exploitability is tempered by two unknowns the vendor advisory does not resolve: whether modern stack protections (canaries/ASLR/NX) reduce this to a DoS rather than reliable RCE, and how exposed the autoregistration service typically is (it is usually reachable only within the managed enterprise/agent network, not the open internet). Net: treat as a serious patch-now item for BoKS operators, but note this is high-CVSS-with-unproven-exploitation rather than confirmed mass exploitation.

Exploit ScenarioDerived

An attacker with network reach to a BoKS host's autoregistration service connects as (or impersonates) an enrolling client and returns a malformed response during the autoregistration handshake, overflowing a fixed-size stack buffer in boks_autoregisterd. Successful exploitation corrupts memory to crash the daemon (DoS) or, if protections are bypassed, execute code in the privileged BoKS enrollment process. No public exploit is identified at time of analysis, and reliable code execution from a stack overflow would require defeating standard memory protections.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
No patch listed yet 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 01, 2026

Unauthenticated remote attackers who can reach the boks_autoregisterd autoregistration service in Fortra's Core Privileged Access Manager (BoKS) can trigger a stack-based buffer overflow while the daemon processes a client response, potentially corrupting memory and achieving code execution under the daemon's privileges, as reflected by the maximum-severity CVSS 3.1 score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H). Affected deployments are those running the BoKS autoregistration/enrollment daemon on a network segment reachable by the attacker, which in most environments is the internal management or agent network rather than the public internet. No public exploit identified at time of analysis; the issue was reported to the vendor by Fortra, and the only reference provided is Fortra's product security advisory FI-2026-017, with no CISA KEV listing and no EPSS data supplied.

RemediationAI

The input data does not state an exact fixed version, so patch status is not independently confirmed from the available sources; the primary action is to consult Fortra's product security advisory FI-2026-017 (https://www.fortra.com/security/advisories/product-security/fi-2026-017) for the specific patched build and apply it as soon as a fixed release is identified, then verify the boks_autoregisterd binary version on every host. Until a fix is applied, restrict network access to the autoregistration service with host- and network-level access control lists so that only known agent or management subnets can reach the boks_autoregisterd port, accepting that changes to agent subnets will require coordinated firewall updates or new enrollment will break; place BoKS management interfaces behind a dedicated, isolated management VLAN and remove any exposure to the public internet or user-facing networks, which may require re-architecting existing flat internal networks; if autoregistration is not actively needed, stop or disable the service, with the trade-off that new clients and agents can no longer self-enroll and must be provisioned manually; and enable monitoring and alerting on unexpected crashes or restarts of boks_autoregisterd, since a failed exploit attempt is likely to surface as a daemon fault rather than a clean security event.

Affected VersionsENISA

Fortra's Core Privileged Access Manager (BoKS) 9.0.0.0 ≤9.0.0.6
Fortra's Core Privileged Access Manager (BoKS) 8.1.0.0 ≤8.1.0.23

Affected Packages

euvd fortra_s_core_privileged_access_manager_boks no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-121 stack-based buffer overflow in boks_autoregisterd, the component of Fortra's Core Privileged Access Manager (formerly BoKS) that handles autoregistration/enrollment of clients and agents into the privileged-access domain. During the autoregistration handshake the daemon parses a client-supplied response structure; because the input is copied into a fixed-size stack buffer without adequate bounds validation, an oversized or malformed response overwrites adjacent stack memory such as saved registers and the return address. The CPE entry cpe:2.3:a:fortra:fortra's_core_privileged_access_manager_(boks):*:*:*:*:*:*:*: uses a wildcard version, so the vendor has not published a discrete version range in the supplied data; the advisory at https://www.fortra.com/security/advisories/product-security/fi-2026-017 is the authoritative source for the exact affected builds. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no credentials or user interaction are required to reach the vulnerable parsing path, but practical exploitation depends on the service being exposed and on an attacker's ability to participate in or spoof the enrollment handshake and to defeat standard stack protections (stack canaries, ASLR, non-executable stack) if code execution rather than a daemon crash is the objective.

Know when Fortra S Core Privileged Access Manager Boks gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Fortra) PRIMARY 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 9.8 CRITICAL

Autoregistration service is network-reachable and parses attacker-controlled client data pre-enrollment (AV:N/AC:L/PR:N/UI:N); stack overflow in a privileged daemon credibly yields full C/I/A impact.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Fortra).

CVSS VectorVendor: Fortra

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Fortra's Core Privileged Access Manager (BoKS) contains a stack-based buffer overflow vulnerability in boks_autoregisterd. A remote attacker with network access to the autoregistration service may be able to trigger memory corruption during client response processing.

Executive ViewAI

Why It Matters

Fortra's Core Privileged Access Manager (BoKS) contains a maximum-severity, unauthenticated stack buffer overflow in its autoregistration service (boks_autoregisterd) that can yield code execution with the daemon's privileges, and no vendor patch is available. Because BoKS governs the privileged credentials used to administer critical systems, a compromise could expose the highest-value accounts in the environment and enable lateral movement across the estate. Any organization running the affected daemon on a network segment reachable by an attacker - typically the internal management or agent network rather than the public internet - should treat this as a priority exposure requiring immediate containment.

Business Impact: Severe
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: restrict network access to the boks_autoregisterd service to a tightly scoped allowlist of trusted agent hosts via firewall, ACL, or microsegmentation; disable the autoregistration daemon on hosts where it is not required; isolate affected BoKS management/agent segments from general user and endpoint networks; monitor for daemon crashes, abnormal termination, or unexpected process execution on affected hosts; and track Fortra advisory FI-2026-017 for patch release and version-specific workarounds.

Threat Intelligence Overview

EPSS Score
0.4%
Top 64% exploitable
Prevalence
Low
niche enterprise privileged-access-management product, limited deployment footprint
Data Quality
4 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available No
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

49
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy