Heap buffer overflow in boks_sshd revoked-key error handling
Summary
| CVE | CVE-2026-14316 |
|---|---|
| State | PUBLISHED |
| Assigner | Fortra |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2026-10-01 17:17:21 UTC |
| Updated | 2026-10-01 20:34:26 UTC |
| 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. |
Risk And Classification
Primary CVSS: v3.1 8.1 HIGH from df4dee71-de3a-4139-9588-11b62fe6c0ff
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Problem Types: CWE-122 | CWE-122 CWE-122 Heap-based buffer overflow
| Version | Source | Type | Score | Severity | Vector |
|---|---|---|---|---|---|
| 3.1 | df4dee71-de3a-4139-9588-11b62fe6c0ff | Secondary | 8.1 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| 3.1 | CNA | CVSS | 8.1 | HIGH | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
CVSS v3.1 Breakdown
Attack Vector
NetworkAttack Complexity
LowPrivileges Required
NoneUser Interaction
RequiredScope
UnchangedConfidentiality
HighIntegrity
HighAvailability
NoneCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N
Vendor Declared Affected Products
| Source | Vendor | Product | Version | Platforms |
|---|---|---|---|---|
| CNA | Fortra | Core Privileged Access Manager BoKS | affected 8.1.0.0 8.1.0.30 custom | Not specified |
| CNA | Fortra | Core Privileged Access Manager BoKS | affected 10.1.0.0 10.1.1.0 custom | Not specified |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| www.fortra.com/security/advisories/product-security/fi-2026-019 | df4dee71-de3a-4139-9588-11b62fe6c0ff | www.fortra.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
Additional Advisory Data
Solutions
CNA: Upgrade to a patched version.
There are currently no legacy QID mappings associated with this CVE.