Skip to main content

Fortisoar Paas CVE-2026-23708

| EUVDEUVD-2026-22329 HIGH
Improper Authentication (CWE-287)
2026-04-14 fortinet GHSA-6p3p-h3vc-6rh5
8.1
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Position on network path (MITM)
  2. Delivery
    Intercept authentication traffic
  3. Exploit
    Decrypt TLS session
  4. Install
    Capture 2FA token
  5. C2
    Replay request before expiration
  6. Execute
    Bypass authentication
  7. Impact
    Gain administrative access

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires FortiSOAR (PaaS or on-premise) versions 7.5.0–7.5.2 or 7.6.0–7.6.3 with 2FA enabled. Attacker must intercept and decrypt captured 2FA authentication traffic, then replay the request before token expiration with precise timing. Victim interaction: user must initiate authentication attempt.

Impact

Real-world exploitation risk is moderate despite the 7.5 CVSS score, constrained by high attack complexity (AC:H) requirements. Attackers must achieve three sequential conditions: network positioning to intercept authentication traffic, capability to decrypt TLS-protected communications (requiring certificate compromise, cryptographic weaknesses, or active MITM), and precise timing to replay tokens before expiration. The PR:N (no privileges required) and AV:N (network attack vector) indicate external threat actors can attempt exploitation, but UI:R (user interaction required) means attacks must coincide with legitimate user authentication attempts. No CISA KEV listing suggests this is not confirmed as actively exploited in the wild. No public exploit code identified at time of analysis, reducing immediate weaponization risk. The SSVC framework would likely classify this as 'Attend' rather than 'Act' priority: exploitation status is PoC (not active), automatable is 'No' due to complex preconditions, and technical impact is 'Total' (authentication bypass grants full access). Organizations using FortiSOAR should prioritize patching based on their threat model-those in high-risk sectors or with exposed authentication endpoints face elevated risk compared to air-gapped or heavily network-segmented deployments.

Exploit ScenarioDerived

An attacker positions themselves as a man-in-the-middle on the network path between a FortiSOAR user and the authentication server, potentially through ARP spoofing, rogue Wi-Fi access points, or compromised network infrastructure. When a legitimate administrator authenticates to FortiSOAR using 2FA, the attacker captures the encrypted authentication traffic and decrypts it using previously compromised TLS certificates or cryptographic vulnerabilities. Within the 2FA token's validity window (typically seconds to minutes), the attacker replays the captured authentication request to the FortiSOAR server, successfully bypassing both password and two-factor authentication to gain full administrative access to the SOAR platform. No public exploit code identified at time of analysis, though the attack methodology follows established replay attack patterns.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.1% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 14, 2026

Authentication bypass in Fortinet FortiSOAR allows unauthenticated remote attackers to circumvent two-factor authentication (2FA) protections via replay attacks against intercepted authentication tokens. Affects both PaaS and on-premise deployments of FortiSOAR versions 7.5.0-7.5.2 and 7.6.0-7.6.3. Successful exploitation requires network positioning to intercept and decrypt authentication traffic, then replay captured 2FA requests before token expiration (CVSS:3.1/AV:N/AC:H/PR:N/UI:R). EPSS data not available; no public exploit code or CISA KEV listing identified at time of analysis, though the precise attack requirements (traffic interception, decryption, timing) increase complexity beyond simple network access.

RemediationAI

Apply vendor-released security updates per Fortinet advisory FG-IR-26-101 available at https://fortiguard.fortinet.com/psirt/FG-IR-26-101. Organizations should upgrade affected FortiSOAR PaaS and on-premise installations to patched versions beyond 7.5.2 and 7.6.3 as specified in the advisory. Until patching is complete, implement compensating controls including network segmentation to restrict authentication endpoint exposure, certificate pinning to prevent TLS interception, monitoring for anomalous authentication patterns (multiple rapid login attempts from different network locations), and enforcing shorter 2FA token validity windows if configuration permits. Review authentication logs for replay attempt indicators such as duplicate token usage or sessions established from unexpected geographic locations immediately following legitimate user logins.

Affected VersionsENISA

FortiSOAR PaaS 7.6.0 ≤7.6.3
FortiSOAR on-premise 7.6.0 ≤7.6.3
FortiSOAR PaaS 7.5.0 ≤7.5.2
FortiSOAR on-premise 7.5.0 ≤7.5.2

Affected Packages

euvd fortisoar_on_premise no fix
euvd fortisoar_paas no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 2 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

FortiSOAR (Security Orchestration, Automation and Response) is Fortinet's SOAR platform for security operations workflow management. This vulnerability stems from CWE-287 (Improper Authentication), specifically a failure to adequately protect two-factor authentication tokens from replay attacks. The authentication mechanism does not implement sufficient anti-replay controls such as nonce validation, strict token binding, or challenge-response freshness checks. When 2FA tokens are transmitted during authentication, an attacker positioned to intercept the encrypted channel (requiring TLS compromise or man-in-the-middle capabilities) can capture and later replay these tokens within their validity window. Both PaaS (cloud-hosted) and on-premise deployment models share the vulnerable authentication implementation across FortiSOAR 7.5.x and 7.6.x release branches, as indicated by dual CPE entries for fortinet:fortisoar_paas and fortinet:fortisoar_on-premise.

Know when Fortisoar Paas gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
CVSS changed
Oct 26, 2026 - 21:23 NVD
7.5 (HIGH) 8.1 (HIGH)
Severity Changed
Apr 14, 2026 - 16:22 NVD
MEDIUM HIGH
CVSS changed
Apr 14, 2026 - 16:22 NVD
6.7 (MEDIUM) 7.5 (HIGH)
CVE Published
Apr 14, 2026 - 15:38 nvd
HIGH 7.5

DescriptionNVD

A improper authentication vulnerability in Fortinet FortiSOAR PaaS 7.6.0 through 7.6.3, FortiSOAR PaaS 7.5.0 through 7.5.2, FortiSOAR on-premise 7.6.0 through 7.6.3, FortiSOAR on-premise 7.5.0 through 7.5.2 may allow an unauthenticated attacker to bypass authentication via replaying captured 2FA request. The attack requires being able to intercept and decrypt authentication traffic and precise timing to replay the request before token expiration, which raises the attack complexity.

Executive ViewAI

Why It Matters

FortiSOAR versions 7.5.0-7.5.2 and 7.6.0-7.6.3 contain an authentication bypass vulnerability that allows attackers on the network to replay intercepted two-factor authentication tokens, potentially gaining unauthorized access to security orchestration and incident response systems. This directly threatens the integrity of security operations and incident response workflows across both cloud and on-premise deployments, requiring immediate isolation and upgrade planning.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) enforce TLS 1.3 with perfect forward secrecy on all FortiSOAR network connections to raise decryption complexity; (2) implement network intrusion detection/prevention to detect token replay patterns; (3) reduce authentication token lifetime to minutes rather than hours; (4) require VPN or zero-trust access controls with additional authentication factors (smartcard, FIDO2) before reaching FortiSOAR; (5) monitor and alert on multiple failed authentication attempts or unusual geographic login origins; (6) disable remote access to management interfaces if operationally feasible and use bastion/jump hosts for all administrative connections.

Threat Intelligence Overview

EPSS Score
0.1%
Top 81% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.1%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy