FortisoarApplication · Fortinet
CVE-2026-23708
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is an improper authentication vulnerability in Fortinet FortiSOAR where an unauthenticated attacker can bypass 2FA by replaying a captured 2FA authentication request. Successful exploitation requires the attacker to perform a man-in-the-middle attack to intercept and decrypt authentication traffic, then precisely time the replay of the 2FA request before the token expires.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FortisoarApplication
>= 7.5.0, < 7.5.3>= 7.6.0, < 7.6.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if FortiSOAR is deployedCheck for FortiSOAR installation by reviewing installed software on systems or checking for FortiSOAR services running on the network. Common installation paths include /opt/fortisoar/ or check for 'fortisoar' processes via 'ps aux | grep fortisoar' on Linux systems.Affected if FortiSOAR is installed and running in the environment
-
Determine installed FortiSOAR versionLog into the FortiSOAR admin UI and navigate to Settings > System > About, or use the command line: 'cd /opt/fortisoar && ./docker-compose exec -T fsapp cat /opt/fortisoar/version.json' (adjust path based on installation method).Affected if Version is 7.5.0 through 7.5.2, or 7.6.0 through 7.6.3
-
Verify 2FA is enabledIn FortiSOAR admin UI, go to Settings > Users > Authentication Profile, or check configuration files for 2FA/multi-factor authentication settings. Look for TOTP, SMS, or email-based 2FA configurations.Affected if Two-factor authentication is configured and active for any user accounts
-
Assess network exposure to MITM attacksReview network architecture to determine if FortiSOAR login endpoints are accessible over untrusted networks without VPN or TLS inspection protections. Check if SSL/TLS interception is not enforced for authentication traffic.Affected if Users can authenticate to FortiSOAR from networks where an attacker could position themselves to intercept traffic (e.g., public networks, untrusted WiFi, or insufficient network segmentation)
The environment is affected if FortiSOAR version is 7.5.0-7.5.2 or 7.6.0-7.6.3, 2FA is enabled, and users can authenticate from networks where a man-in-the-middle attack is feasible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.5.37.6.4
Upgrade to FortiSOAR versions 7.6.4 or later (or latest available) which contain the patch for this vulnerability. Additionally, enforce network-level protections such as VPN usage and TLS inspection to make man-in-the-middle attacks more difficult.
FortiSOAR 7.5.3 or later; FortiSOAR 7.6.4 or later (depending on your current major version)
- Identify the currently installed FortiSOAR version (7.5.x or 7.6.x)
- For FortiSOAR 7.5.x versions (7.5.0 to 7.5.2): Upgrade to version 7.5.3 or later
- For FortiSOAR 7.6.x versions (7.6.0 to 7.6.3): Upgrade to version 7.6.4 or later
- Before upgrading, take a full backup of the FortiSOAR database and configuration
- Schedule the upgrade during a maintenance window to minimize disruption
- Follow Fortinet's official upgrade documentation for your deployment type (PaaS or on-premise)
- After upgrade, verify the authentication mechanism is working correctly
- Confirm the new version is running: 7.5.3 or higher for 7.5 line; 7.6.4 or higher for 7.6 line
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisoar
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-23708 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-23708 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data