CVE-2026-22155: A cleartext transmission of sensitive information vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7....
A cleartext transmission of sensitive information vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.3, FortiSOAR PaaS 7.5.0 through 7.5.2, FortiSOAR PaaS 7.4 all versions, FortiSOAR PaaS 7.3 all versions, FortiSOAR on-premise 7.6.0 through 7.6.2, FortiSOAR on-premise 7.5.0 through 7.5.1, FortiSOAR on-premise 7.4 all versions, FortiSOAR on-premise 7.3 all versions may allow attacker to information disclosure via <insert attack vector here>
Security readout for executives and security teams
Plain-English summary
This FortiSOAR issue can expose sensitive information because some data may be transmitted without proper encryption. The main business risk is confidentiality loss from a security orchestration platform, which may hold incident, automation, credential, or integration data. The provided source does not identify the exact attack vector.
Executive priority
Treat as a timely confidentiality-risk fix, not an emergency absent active-exploitation evidence. Prioritize based on FortiSOAR data sensitivity and network exposure.
Technical view
CVE-2026-22155 is a CWE-319 cleartext transmission vulnerability affecting specified FortiSOAR PaaS and on-premise versions. CVSS 3.1 is 6.2: network reachable, low complexity, low privileges, no user interaction, high confidentiality impact, and no integrity or availability impact.
Likely exposure
Organizations running affected FortiSOAR PaaS 7.3, 7.4, 7.5.0-7.5.2, 7.6.0-7.6.3, or on-premise 7.3, 7.4, 7.5.0-7.5.1, 7.6.0-7.6.2 may be exposed.
Exploitation context
The CVE is not listed as KEV in the provided bundle. The CVSS temporal vector marks exploit maturity as proof-of-concept, but the sources provided do not show active exploitation or public weaponization details.
Researcher notes
The public description contains a placeholder attack-vector field, so technical validation is constrained. Focus research on version confirmation, Fortinet advisory details, and safe traffic review without attempting exploitation.
Mitigation direction
Review Fortinet advisory FG-IR-26-106 for official fixed versions and upgrade guidance.
Prioritize FortiSOAR instances handling sensitive incidents, credentials, or third-party integrations.
Restrict FortiSOAR access to trusted administrative networks while remediation is planned.
Review network segmentation and encryption controls around FortiSOAR communications.
Ask Fortinet support for clarification if the advisory lacks deployment-specific guidance.
Validation and detection
Inventory FortiSOAR PaaS and on-premise versions across all environments.
Compare installed versions against the affected ranges in the CVE record.
Confirm whether FortiSOAR is reachable from untrusted or broad internal networks.
Review logs and traffic monitoring for unexpected cleartext sensitive data exposure.
Document remediation status and exceptions for any affected instance.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-319: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.