Vulnerability in Fortra BoKS Manager (CVE-2026-79899)
Summary
Vulnerability in Fortra BoKS Manager (CVE-2026-79899). Confidential information can be exposed externally.
Original description
The description as published by the source.
Fortra BoKS Manager contains an insecure temporary file vulnerability in bccgethostcert. The utility creates predictable temporary files without first setting a restrictive umask. A local user on the BoKS Master who can read files under BOKS_tmp may be able to obtain CA secret or host private-key material while the utility runs, or obtain CA secret material left behind after successful certificate creation.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-79899 has been found in Fortra BoKS Manager.
Confidential information can be exposed externally. CVSS score: 7.9/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Fortra BoKS Manager CVE-2026-79899" on the vendor's site.
CVE-2026-79899 (Fortra BoKS Manager) — CWE-377 / CVSS v3 7.9
Attack vector: local
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-377) exists in Fortra BoKS Manager.
Check the vendor advisory for the affected versions of Fortra BoKS Manager.
Severity: High (CVSS 7.9/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Fortra BoKS Manager を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web fortra.com
- web nvd.nist.gov
- web github.com