CVE-2026-59841
Fortinet Fortisiem 7.4.0 – 7.4.2
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2026-59841 is a high-severity Improper Restriction of Communication Channel to Intended Endpoints (CWE-923) vulnerability in Fortinet Fortisiem. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Adversary-in-the-Middle (T1557); ranked at the 4th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-3 (Device Identification and Authentication) and SC-23 (Session Authenticity) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-43713
Vulnerability Data
A improper restriction of communication channel to intended endpoints vulnerability in Fortinet FortiSIEMWindowsAgent 7.4.0 through 7.4.1 may allow attacker to escalation of privilege via <insert attack vector here>
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 5 hardening rules · 3 OS baselines
V8.4.1V10.5.5V12.3.5
Mitigating Controls (NIST 800-53 r5) AI
Requires unique identification and authentication of devices before establishing a communications session.
Enforces authenticity of communication sessions so the system only exchanges data with verified intended endpoints.
Protects transmitted information with cryptographic integrity mechanisms that implicitly verify endpoint identity.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Network segmentation and access controls directly enforce communication only with intended endpoints.
Authenticating services/hardware directly prevents communication with unintended endpoints.
Data-in-transit protections commonly include certificate-based endpoint authentication to ensure correct peers.
Documenting authorized flows helps define intended endpoints but does not enforce channel restrictions at runtime.
Protecting identity assertions supports endpoint verification but is narrower than channel restriction.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Secure authentication mechanisms ensure the product communicates only with intended, authenticated endpoints.
Network security controls directly enforce endpoint validation and channel restrictions.
Security of network services includes authentication of endpoints and service-to-service channel protection.
Network segregation reduces exposure but does not itself validate specific endpoints.
Cryptography can protect channels but does not guarantee correct endpoint identity without additional controls.
Application security requirements may specify endpoint validation but do not implement it.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (2 rules)
- V-248827 OL 8 must not have the rsh-server package installed. prevents CWE-923
- V-248823 OL 8 must not have the telnet-server package installed. prevents CWE-923
RHEL 7 (1 rule)
- V-204442 The Red Hat Enterprise Linux operating system must not have the rsh-server package installed. prevents CWE-923
RHEL 8 (2 rules)
- V-230492 RHEL 8 must not have the rsh-server package installed. prevents CWE-923
- V-230487 RHEL 8 must not have the telnet-server package installed. prevents CWE-923