Fortinet risk is product- and version-specific, especially for Internet-facing firewalls and VPN services. The first step is identifying exactly which FortiOS/FortiProxy/FortiSASE versions and exposed services are in use.
Current watch item
Fortinet's PSIRT catalog currently includes 2026 FortiOS advisories such as CVE-2026-22153, a high-severity authentication-bypass issue affecting certain FortiOS versions and SSL-VPN/FSSO-related functionality. Fortinet's PSIRT catalog is actively maintained and includes product/version-specific upgrade guidance.
What should you check?
- Record FortiGate/FortiOS model, version and build.
- Identify whether SSL-VPN, administrative interfaces or other services are Internet-facing.
- Compare the exact build against current Fortinet PSIRT guidance.
- Use Fortinet's recommended upgrade path rather than jumping between trains without review.
- Review MFA, local admin accounts, trusted hosts and remote-access policy.
- Back up configuration and understand HA/failover behavior before firmware changes.
What not to do
- Do not assume all FortiGate devices are affected by every Fortinet advisory.
- Do not expose administrative interfaces broadly to the Internet.
- Do not delay critical edge-device updates because the firewall is 'working.'
- Do not upgrade a production HA pair without a documented sequence and rollback plan.
How CompFlorida prioritizes the risk
We verify product/version, exposure, vendor guidance, business dependency and recovery path. A severity score alone is not enough.
Official sources CompFlorida reviewed
Fortinet PSIRT advisories and FortiGuard upgrade-path guidance.
What you should know when you're finished
You should know your current version, whether the vendor guidance applies, what service is exposed, and who owns the next action.
Need help verifying your environment?
CompFlorida can help identify the product/version, determine applicability and coordinate remediation.
Request a Technology Risk ReviewLast reviewed: September 22, 2026.

