Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-79899 Overview
CVE-2026-79899 is an insecure temporary file vulnerability in the bccgethostcert utility of Fortra BoKS Manager. The utility creates predictable temporary files in BOKS_tmp without first setting a restrictive umask. A local user with read access to BOKS_tmp on the BoKS Master can obtain Certificate Authority (CA) secrets or host private-key material while the utility runs. Attackers can also recover CA secret material left behind after successful certificate creation. The flaw is tracked under [CWE-377: Insecure Temporary File].
Critical Impact
Exposure of CA secret material and host private keys enables attackers to forge certificates and impersonate hosts across the BoKS-managed identity infrastructure.
Affected Products
- Fortra BoKS Manager (BoKS Master component)
- The bccgethostcert certificate utility
- Deployments where local users have read access to BOKS_tmp
Discovery Timeline
- 2026-10-01 - CVE-2026-79899 published to the National Vulnerability Database (NVD)
- 2026-10-01 - Last updated in NVD database
Technical Details for CVE-2026-79899
Vulnerability Analysis
The bccgethostcert utility handles certificate retrieval operations on the BoKS Master, interacting with sensitive CA material and host private keys. During normal execution, the utility writes intermediate state to temporary files under the BOKS_tmp directory. The utility fails to set a restrictive umask before creating these files, so the resulting file permissions follow the process default and may be world- or group-readable.
The temporary file names are also predictable, removing a layer of obscurity that would otherwise complicate opportunistic reads. A local, authenticated user who can enumerate BOKS_tmp can therefore race the utility to read sensitive key material in-flight. In some code paths, CA secret material remains on disk after a certificate is successfully created, allowing offline recovery long after the operation completes.
Root Cause
The root cause is a failure to apply defensive file-handling primitives when the utility writes privileged data to a shared temporary directory. Specifically, bccgethostcert does not invoke umask(077) prior to creating temporary files, and it does not atomically create files with restrictive mode bits (for example via open() with O_CREAT | O_EXCL and explicit 0600 permissions). The utility also does not clean up CA secret artifacts on successful completion, violating the principle of least retention for sensitive key material.
Attack Vector
Exploitation requires local access to the BoKS Master and read permissions on BOKS_tmp. The attacker monitors the directory while a privileged operator or scheduled job invokes bccgethostcert, then reads the predictable temporary files before the utility finishes. Alternatively, the attacker enumerates residual files left after legitimate certificate creation and extracts CA secret material directly. Successful exploitation yields key material sufficient to impersonate hosts or issue unauthorized certificates. The vulnerability requires user interaction, consistent with the need for a privileged operator to execute the vulnerable utility.
No public proof-of-concept code is available. See the Fortra Security Advisory FI-2026-014 for vendor-specific technical details.
Detection Methods for CVE-2026-79899
Indicators of Compromise
- Unexpected files or stale artifacts in BOKS_tmp persisting after bccgethostcert executions
- Read access attempts to BOKS_tmp by user accounts that are not part of the BoKS administrative group
- Unexplained certificate issuance events or host authentications originating from unexpected systems
Detection Strategies
- Audit filesystem access to BOKS_tmp using Linux auditd rules on open/read syscalls for files in that directory
- Correlate bccgethostcert process executions with concurrent read operations by non-privileged users
- Review BoKS certificate issuance logs for anomalous host identifiers or off-hours activity
Monitoring Recommendations
- Enable continuous file integrity monitoring on BOKS_tmp and the surrounding BoKS working directories
- Alert on any process other than BoKS utilities opening files under BOKS_tmp
- Retain and centralize BoKS Master audit logs for post-incident forensic review
How to Mitigate CVE-2026-79899
Immediate Actions Required
- Restrict access to the BoKS Master host to the minimum set of administrative users required for operation
- Tighten directory permissions on BOKS_tmp so that only the BoKS service account can read its contents
- Review and remove any residual CA secret or private-key material currently present in BOKS_tmp
- Rotate CA keys and reissue host certificates if evidence of unauthorized access is identified
Patch Information
Fortra has published remediation guidance in Fortra Security Advisory FI-2026-014. Administrators should apply the fixed version of BoKS Manager identified in that advisory and validate the patched bccgethostcert binary applies a restrictive umask before writing to BOKS_tmp.
Workarounds
- Limit login access on the BoKS Master to a small, audited set of administrators until the patch is applied
- Apply restrictive permissions (for example chmod 700) to the BOKS_tmp directory to block non-service account reads
- Avoid running bccgethostcert on systems where untrusted local users maintain shell access
# Configuration example: restrict BOKS_tmp to the BoKS service account
chown boks:boks /var/opt/boksm/BOKS_tmp
chmod 700 /var/opt/boksm/BOKS_tmp
# Audit read access to BOKS_tmp
auditctl -w /var/opt/boksm/BOKS_tmp -p r -k boks_tmp_read
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

