Skip to content
Honeypot Daily
Tech and security news that matters
Is your FortiSandbox vulnerable to authenticated denial-of-service?
Vulnerabilities

Is your FortiSandbox vulnerable to authenticated denial-of-service?

Fortinet has released a patch for a flaw that allows remote attackers to crash the system after logging in.

Key points

  • Fortinet issued an update to fix CVE-2026-106170 in FortiSandbox.
  • The flaw allows authenticated remote attackers to cause denial-of-service.
  • Zero Day Initiative rated the vulnerability CVSS 4.9.

The short version

  • Fortinet FortiSandbox installations are affected by a denial-of-service flaw.
  • Attackers must have valid credentials to exploit the issue.
  • A vendor update is now available to resolve the problem.

The details

Fortinet has published a security update to address a vulnerability in its FortiSandbox product, according to the Zero Day Initiative. The flaw, tracked as CVE-2026-106170, allows remote attackers to create a denial-of-service condition on affected systems. Exploitation of this issue requires the attacker to have valid authentication credentials. The specific defect exists within the handling of the users field.

It results from a lack of proper handling of error conditions, which can be leveraged to disrupt service. The Zero Day Initiative assigned a CVSS rating of 4.9 to this vulnerability. The advisory notes a coordinated public release of the advisory. The vulnerability was reported to the vendor on 19 June 2026. The coordinated public disclosure occurred on 15 October 2026.

The context

The vulnerability impacts FortiSandbox installations. Because authentication is required, the attack surface is limited to those with access to valid accounts. The flaw allows for a denial-of-service condition. Fortinet has confirmed that an update corrects this vulnerability. Users are directed to the FortiGuard PSIRT page for further details. The advisory highlights the issue in the handling of the users field. This type of flaw can be triggered by improper error handling.

Next steps

Administrators should verify their FortiSandbox versions against the vendor's advisory. Apply the released update as soon as possible to mitigate the risk. Review access logs for any suspicious activity prior to patching. Ensure that accounts use strong authentication methods. Monitor system stability after applying the patch to confirm resolution.

What defenders should look for

Teams usually monitor for sudden drops in service availability or increased latency on management interfaces. Check whether sessions are terminating unexpectedly or failing to load user profiles. Look for error spikes in application logs related to user field processing. If a denial-of-service is suspected, isolate the affected instance from the network to prevent further exploitation. Review authentication logs for unusual login patterns or failed attempts from known IPs. Contain the issue by restricting access to the interface until the patch is applied.

What to do and how to stay safe: Fortinet

  • Apply the vendor-provided update to your FortiSandbox installations immediately.
  • Audit account access and enforce multi-factor authentication where possible.
  • Monitor system logs for unusual error patterns or service interruptions.
  • Verify that all instances are running the patched version before reconnecting to production traffic.

Step-by-step guide: How Virtual Patching Works: The Mechanics Behind Inline Protection

General security guidance from the Honeypot Daily newsroom. It is not confirmed advice from the organisations named in this story.

Frequently asked questions

What is the CVSS score for CVE-2026-106170?

The Zero Day Initiative assigned a CVSS rating of 4.9 to this vulnerability.

Is authentication required to exploit this flaw?

Yes, the vulnerability requires valid authentication credentials to exploit.

Has Fortinet released a fix for this issue?

Yes, Fortinet has issued an update to correct this vulnerability.

Sources

  1. Zero Day Initiative
FortinetFortiSandboxCVE-2026-106170ZDIDenial-of-Service

Related stories