Core Privileged Access Manager (BoKS): Heap-based Buffer Overflow
CVE-2026-14316 is a high-severity heap-based buffer overflow vulnerability in Core Privileged Access Manager (BoKS) from Fortra, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists versions 8.1.0.30, 10.1.1.0 as the first without the flaw, so updating Core Privileged Access Manager (BoKS) to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.22% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Core Privileged Access Manager (BoKS) to 8.1.0.30 or 10.1.1.0, whichever matches your release line, or a later version.
- Read the advisory on fortra.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Fortra | Core Privileged Access Manager (BoKS) | 8.1.0.0 up to, but not including, 8.1.0.30; 10.1.0.0 up to, but not including, 10.1.1.0 | 8.1.0.30, 10.1.1.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N. Scored by CNA.
Official description
The revoked-key error path builds a human-readable failure reason using sprintf() into a heap buffer. The allocated buffer is too small for the final formatted message. When sprintf() writes the full message, it can write past the end of the heap allocation.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Heap-based Buffer Overflow
The product writes past the end of a buffer that was allocated on the heap.
How developers prevent this class of flaw
- Pre-design: Use a language or compiler that performs automatic bounds checking.
- Use an abstraction library to abstract away risky APIs. Not a complete solution.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other vulnerabilities in Core Privileged Access Manager (BoKS)
- 8.8 High severity
- 9.8 Critical severity
Recent Heap-based Buffer Overflow vulnerabilities
- 9.2 Critical severity
- 7.1 High severity
- 9.6 Critical severity
- 9.6 Critical severity
- 9.6 Critical severity
- 9.6 Critical severity
Spotted an error? Tell us.