A critical Australian cyber security alert published on 23 October 2026 warns of vulnerabilities affecting Fortinet products. For organisations that rely on perimeter security and remote access, the priority is to identify exposed devices, apply the vendor's applicable fixes and check for signs of compromise rather than assume that patching alone closes the risk.
Confirm exposure
Inventory Fortinet appliances and services, including devices managed by a third party.
Patch from official guidance
Match each product and firmware branch to Fortinet's advisory before applying the correct update.
Review access and logs
Look for unexpected administrator activity, configuration changes and unusual remote access.
Document verification
Record versions, actions, exceptions and evidence that systems are operating as expected.
What does the Fortinet security alert say?
The Australian Cyber Security Centre (ACSC) listed a critical alert for Fortinet product vulnerabilities on 23 October 2026 and advised customers to implement security updates as a priority. The alert is relevant to Australian small and medium businesses, larger organisations, critical infrastructure and government. That makes this a practical asset-management and response issue, not simply a vendor news item.
The public alert summary does not, by itself, establish that every Fortinet product or every deployment is affected in the same way. Organisations should consult the linked vendor advisory for the precise products, versions, conditions, fixed releases and any interim mitigations. Do not infer affected versions from a headline or install a firmware image intended for a different model or branch.
Which Fortinet systems should Australian businesses check first?
Start with devices that protect internet-facing services, remote access, site-to-site connectivity and administrative interfaces. Confirm the exact product family, model, software version and management owner. Include equipment hosted in branch offices, cloud environments, data centres and managed service provider environments. A spreadsheet that is months out of date is not sufficient evidence of current exposure.
Ask your IT provider or managed security partner to confirm whether the organisation uses the affected product families and whether the current release is covered by the advisory. If an asset cannot be identified or its version cannot be confirmed, treat that uncertainty as a task to resolve urgently.
How should you patch Fortinet devices safely?
Use Fortinet's official Product Security Incident Response Team (PSIRT) advisory and the support documentation for the exact device. Confirm the fixed version and upgrade path, check compatibility and configuration requirements, and ensure that a tested backup and recovery plan are available. Schedule the change according to the risk and operational impact, but do not let normal maintenance windows become an excuse for leaving a critically exposed system unaddressed.
For critical internet-facing equipment, decide whether temporary access restrictions or other mitigations are necessary while the change is prepared. Test management access, VPN connectivity, routing, security policies and monitoring after the update. Record the installed version and the person who verified the result.
Practical tip
Do not treat a successful firmware update as proof that a device was never compromised. For internet-facing systems with unexplained changes or suspicious activity, preserve relevant logs and investigate before clearing evidence or rebuilding the device.
How can you check for signs of compromise?
Review administrator logins, authentication failures, new or changed accounts, unexpected configuration edits, unfamiliar VPN sessions and changes to firewall rules. Compare current settings with a known-good baseline where one exists. Check whether monitoring tools recorded unusual outbound connections or activity at times when no authorised change was planned.
Keep evidence in line with your incident response procedures. If you find indicators of compromise, do not assume that patching resolves the incident. Restrict affected access where appropriate, preserve logs and configuration evidence, involve incident responders and assess whether credentials or secrets need to be rotated. Consider legal, contractual and regulatory notification obligations based on the facts of the incident.
What should your team do in the next 24 hours?
- Assign an owner: make one person accountable for confirming exposure and coordinating remediation.
- Identify assets: check inventory, configuration management, network scans and provider records for Fortinet devices.
- Read the vendor advisory: confirm affected products, fixed releases, upgrade paths and mitigations using official guidance.
- Remediate and verify: patch or apply vendor-recommended mitigations, then test critical services and record evidence.
- Investigate anomalies: review logs and configuration changes, escalating suspicious activity to incident response.
Organisations with many appliances should track progress centrally and report any systems that cannot be patched, including the reason, compensating controls and target remediation date. Recheck the vendor advisory for updates as new technical detail becomes available.
How does this fit into your wider security programme?
Critical vulnerabilities highlight the need for an accurate asset inventory, an agreed patching process and clear responsibility for perimeter devices. Intrix's vulnerability management services can support a repeatable process for identifying, prioritising and tracking weaknesses. Organisations reviewing network exposure can also explore network penetration testing and managed detection and response to improve validation and visibility.
For broader planning, read Intrix's practical guide to cybersecurity asset inventories and guide to privileged access management. These topics complement emergency patching by helping teams understand which assets they own, who can administer them and how to monitor sensitive access.
Need help validating your exposure?
Intrix can help your team assess security gaps, prioritise remediation and plan appropriate testing and monitoring. Contact our team to discuss your environment and next steps.
Get in touch →Frequently asked questions
Is the Fortinet alert relevant to Australian businesses?
Which Fortinet versions are vulnerable?
Should we patch immediately?
Is patching enough if a device was exposed?
What if our firewall is managed by a provider?
Sources and further reading
- Australian Cyber Security Centre, Alerts and advisories, including “Critical vulnerabilities in Fortinet products”, published 23 October 2026.
- Fortinet Product Security Incident Response Team (PSIRT), official vendor advisories and remediation details. Check the relevant product-specific advisory before acting.
- Intrix, Cybersecurity Asset Inventory: A Practical Guide for Australian Businesses.
