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-79896 Overview
CVE-2026-79896 is an out-of-bounds read vulnerability [CWE-125] in Fortra BoKS Manager. The flaw resides in the custom Transport Layer Security (TLS) ClientHello parser used by the boks_portmux daemon. A remote unauthenticated attacker can submit a malformed ClientHello message and terminate the daemon. While boks_portmux typically restarts automatically, repeated malformed requests can sustain a denial-of-service condition against the service.
Critical Impact
Remote unauthenticated attackers can repeatedly crash the boks_portmux daemon, producing sustained denial of service against BoKS Manager access control functions.
Affected Products
- Fortra BoKS Manager (see vendor advisory for affected versions)
- boks_portmux component responsible for TLS session multiplexing
- Deployments exposing the BoKS Manager network listener to untrusted networks
Discovery Timeline
- 2026-10-01 - CVE-2026-79896 published to the National Vulnerability Database (NVD)
- 2026-10-01 - Last updated in NVD database
Technical Details for CVE-2026-79896
Vulnerability Analysis
The vulnerability exists in the custom TLS ClientHello parser implemented in boks_portmux. The parser reads length-prefixed fields from the ClientHello message without correctly validating that declared field lengths remain within the bounds of the received buffer. When a declared length exceeds the actual data available, the parser reads past the end of the buffer and triggers a fatal condition that terminates the daemon.
Because boks_portmux acts as the entry point for TLS-wrapped BoKS traffic, its termination disrupts authentication and access control brokering between BoKS clients and the Manager. Although a supervisory process restarts the daemon, an attacker can send malformed ClientHello messages in a loop to keep the service unavailable.
The issue falls under the out-of-bounds read class and is tracked as [CWE-125]. According to the Exploit Prediction Scoring System (EPSS) data published on 2026-10-08, this issue has a modest probability of exploitation in the near term, consistent with a denial-of-service primitive without confidentiality or integrity impact.
Root Cause
The root cause is insufficient input validation in the handwritten TLS ClientHello parser. Standard TLS libraries validate record and extension lengths before dereferencing them, but the custom parser used by boks_portmux processes attacker-controlled length fields without enforcing bounds against the actual message size.
Attack Vector
The attack vector is network-based and requires no authentication or user interaction. An attacker establishes a TCP connection to the boks_portmux listener and sends a crafted TLS ClientHello containing malformed length fields. The parser performs an out-of-bounds read, the process terminates, and the attacker repeats the request to maintain the outage.
// No verified exploit code is public. The vulnerability manifests when the
// ClientHello parser reads a length field (for example, cipher_suites_length
// or an extension length) that exceeds the remaining buffer, causing an
// out-of-bounds read and daemon termination. See the Fortra advisory for
// vendor-authored technical details.
Detection Methods for CVE-2026-79896
Indicators of Compromise
- Repeated unexpected restarts of the boks_portmux process on BoKS Manager hosts
- TLS handshake failures or truncated ClientHello messages logged by the daemon
- Short-lived TCP connections to the boks_portmux listener from unknown sources immediately preceding daemon crashes
- Supervisory logs showing automatic restart loops of boks_portmux
Detection Strategies
- Alert on process termination and restart events for boks_portmux using endpoint telemetry
- Inspect inbound TLS handshakes to the BoKS Manager listener for malformed ClientHello structures
- Correlate network connection attempts with daemon crash timestamps to identify the source of malformed traffic
Monitoring Recommendations
- Monitor BoKS Manager service availability and alert on repeated restart cycles within short time windows
- Capture packet traces at the BoKS Manager network boundary when crashes occur to preserve evidence of malformed ClientHello messages
- Track source IP addresses connecting to the boks_portmux port and flag high-rate connections from unauthorized hosts
How to Mitigate CVE-2026-79896
Immediate Actions Required
- Apply the fix referenced in Fortra Security Advisory FI-2026-016 as soon as it is available for your deployment
- Restrict network access to the boks_portmux listener to known BoKS client subnets using firewall or network access control lists
- Review supervisory restart thresholds so that repeated crashes trigger operator alerts rather than silent restarts
Patch Information
Fortra has published remediation details in Fortra Security Advisory FI-2026-016. Administrators should consult the advisory for fixed versions and upgrade procedures that apply to their BoKS Manager release.
Workarounds
- Place boks_portmux behind a network segmentation boundary that only permits connections from authenticated BoKS client hosts
- Use upstream TLS termination or a reverse proxy that validates ClientHello messages before forwarding traffic to boks_portmux
- Rate-limit inbound connections to the BoKS Manager listener to slow repeated crash attempts
# Example: restrict boks_portmux access to a trusted client subnet
# Replace the port and subnet with values appropriate to your environment
iptables -A INPUT -p tcp --dport 6500 -s 10.0.10.0/24 -j ACCEPT
iptables -A INPUT -p tcp --dport 6500 -j DROP
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

