FortisandboxApplication · Fortinet
CVE-2026-26083
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 missing authorization vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 through 4.4.8, FortiSandbox Cloud 5.0.2 through 5.0.5, FortiSandbox PaaS 23.4 all versions, FortiSandbox PaaS 23.3 all versions, FortiSandbox PaaS 23.1 all versions, FortiSandbox PaaS 22.2 all versions, FortiSandbox PaaS 22.1 all versions, FortiSandbox PaaS 21.4 all versions, FortiSandbox PaaS 21.3 all versions, FortiSandbox PaaS 5.0.0 through 5.0.1, FortiSandbox PaaS 4.4.5 through 4.4.8 may allow an unauthenticated attacker to execute unauthorized code or commands via HTTP requests.
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 confidenceA missing authorization vulnerability in FortiSandbox allows unauthenticated attackers to execute arbitrary code or commands via specially crafted HTTP requests. This authentication bypass affects multiple versions across FortiSandbox 5.0.x, 4.4.x, and various Cloud/PaaS offerings, enabling complete system compromise without credentials.
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
FortisandboxApplication
>= 4.4.0, < 4.4.9>= 5.0.0, < 5.0.2
Fortisandbox CloudApplication
>= 5.0.2, < 5.0.6>= 23.1.4245, <= 23.4.4374= 24.1.4436
Fortisandbox PaasApplication
>= 4.4.5, < 4.4.9>= 5.0.0, < 5.0.2>= 21.3.4055, <= 23.4.4374CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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 FortiSandbox product variant and versionAccess the FortiSandbox CLI and run 'get system status' or 'diagnose system version' to retrieve the exact product version and model. Alternatively, check the web UI login page or dashboard footer which typically displays the firmware version.Affected if The displayed version falls within any of these ranges: 4.4.0 through 4.4.8, 5.0.0 through 5.0.1, 5.0.2 through 5.0.5 (Cloud), 23.1.4245 through 23.4.4374 (Cloud/PaaS), 24.1.4436 (Cloud), or 21.3.4055 through 23.4.4374 (PaaS).
-
Verify HTTP management interface accessibilityFrom an untrusted network host, attempt to reach the FortiSandbox web UI via HTTP/HTTPS on the management port (typically 443 or 8443). Use curl or a browser to test if the login page loads without authentication.Affected if The management interface is reachable from untrusted networks without requiring VPN or internal network access.
-
Check interface configuration for management exposureIn FortiSandbox CLI, run 'show system interface' to list network interfaces and their roles. Look for 'mgmt' interface configuration and verify which IP addresses or networks are permitted to access it.Affected if The mgmt interface is bound to an IP address accessible from non-local networks or 'set allowaccess' includes HTTP/HTTPS from untrusted sources.
-
Confirm remote management is enabledRun 'get system global' or 'show system global' in CLI to check if remote management protocols are enabled. Specifically check for HTTP/HTTPS in the management access list.Affected if HTTP or HTTPS management access is enabled and the interface is externally reachable.
A user is affected if they run FortiSandbox version 4.4.0-4.4.8, 5.0.0-5.0.1, or the specific Cloud/PaaS version ranges AND the management interface is accessible from untrusted networks.
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 · scoped4.4.95.0.25.0.6
Upgrade to Fortinet's patched version as specified in the FortiSandbox security advisory. If immediate patching is not possible, restrict HTTP access to FortiSandbox management interfaces to trusted networks or disable remote management access.
FortiSandbox: 4.4.9 or 5.0.2+ | FortiSandbox Cloud: 5.0.6+ | FortiSandbox PaaS: 4.4.9, 5.0.2+, or 23.4.4375+
- 1. Identify the FortiSandbox product variant (FortiSandbox, FortiSandbox Cloud, or FortiSandbox PaaS) currently deployed
- 2. Determine the currently installed version from the FortiSandbox web UI or CLI using 'get system status'
- 3. For FortiSandbox appliance: upgrade to version 4.4.9 or later, or version 5.0.2 or later
- 4. For FortiSandbox Cloud: upgrade to version 5.0.6 or later
- 5. For FortiSandbox PaaS: upgrade to version 4.4.9 or later, version 5.0.2 or later, or version 23.4.4375 or later
- 6. Download the firmware from Fortinet Customer Support portal or FortiGuard
- 7. Upload the firmware via FortiSandbox web UI (System > Firmware > Upload) or CLI using 'execute firmware upload'
- 8. After upgrade, verify the version using 'get system status' and confirm the vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Fortisandbox
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26083 — 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-26083 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