Fortra Core Privileged Access Manager up to 8.1.0.23/9.0.0.6 Autoregistration Service boks_autoregisterd stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as very critical, has been found in Fortra Core Privileged Access Manager up to 8.1.0.23/9.0.0.6. This impacts the function boks_autoregisterd of the component Autoregistration Service. Performing a manipulation results in stack-based overflow.
This vulnerability is reported as CVE-2026-12627. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability, which was classified as very critical, was found in Fortra Core Privileged Access Manager up to 8.1.0.23/9.0.0.6. This affects the function boks_autoregisterd of the component Autoregistration Service. The manipulation with an unknown input leads to a stack-based overflow vulnerability. CWE is classifying the issue as CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at fortra.com. This vulnerability is uniquely identified as CVE-2026-12627 since 06/18/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/01/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
- 8.1.0.0
- 8.1.0.1
- 8.1.0.2
- 8.1.0.3
- 8.1.0.4
- 8.1.0.5
- 8.1.0.6
- 8.1.0.7
- 8.1.0.8
- 8.1.0.9
- 8.1.0.10
- 8.1.0.11
- 8.1.0.12
- 8.1.0.13
- 8.1.0.14
- 8.1.0.15
- 8.1.0.16
- 8.1.0.17
- 8.1.0.18
- 8.1.0.19
- 8.1.0.20
- 8.1.0.21
- 8.1.0.22
- 8.1.0.23
- 9.0.0.0
- 9.0.0.1
- 9.0.0.2
- 9.0.0.3
- 9.0.0.4
- 9.0.0.5
- 9.0.0.6
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.9VulDB Meta Temp Score: 9.9
VulDB Base Score: 10.0
VulDB Temp Score: 10.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 9.8
CNA Vector (Fortra): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
06/18/2026 CVE reserved10/01/2026 Advisory disclosed
10/01/2026 VulDB entry created
10/01/2026 VulDB entry last update
Sources
Advisory: fortra.comStatus: Confirmed
CVE: CVE-2026-12627 (🔒)
GCVE (CVE): GCVE-0-2026-12627
GCVE (VulDB): GCVE-100-412707
Entry
Created: 10/01/2026 17:49Changes: 10/01/2026 17:49 (63)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.