LiveActive security incident?Get immediate response
CVE Record

CVE-2026-26083: A missing authorization vulnerability in Fortinet FortiSandbox 5.0.0 through 5.0.1, FortiSandbox 4.4.0 thro...

A 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.

CriticalCVSS 9.1Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-26083 is a critical Fortinet FortiSandbox authorization flaw. An unauthenticated network attacker may be able to run unauthorized code or commands through HTTP requests. Systems using affected FortiSandbox, FortiSandbox Cloud, or FortiSandbox PaaS versions should be treated as urgent exposure until verified patched or otherwise addressed by Fortinet guidance.

Executive priority

Prioritize this as an urgent remediation item for any exposed or business-critical FortiSandbox environment. The business risk is unauthorized command or code execution without credentials, which can support data theft, service disruption, or broader compromise. Lack of KEV evidence lowers certainty of active exploitation, not technical severity.

Technical view

The issue is CWE-862 missing authorization with CVSS 9.1. The vector is network reachable, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact. The source bundle names FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS version ranges, but some affected-version details appear inconsistent across the description and CPE list.

Likely exposure

Exposure is most likely where FortiSandbox HTTP management or service endpoints are reachable by untrusted networks. Affected products include FortiSandbox, FortiSandbox Cloud, and FortiSandbox PaaS versions listed in the source bundle. Asset owners should verify exact versions against Fortinet advisory FG-IR-26-136 because the bundle contains version-range inconsistencies.

Exploitation context

The bundle does not show CISA KEV listing and provides no cited evidence of active exploitation. The CVSS temporal vector includes exploit-code maturity as functional, but that is not the same as confirmed exploitation in the wild. Treat this as high-priority due to unauthenticated remote code or command execution potential.

Researcher notes

Do not rely only on the summarized affected table. The description, CPE list, and product-version entries differ for some FortiSandbox Cloud and 4.2 branch details. Use Fortinet FG-IR-26-136 as the authoritative remediation reference and avoid assuming exploitability outside the stated HTTP-request authorization weakness.

Mitigation direction

  • Review Fortinet advisory FG-IR-26-136 for fixed versions and workarounds.
  • Upgrade affected FortiSandbox deployments according to Fortinet guidance.
  • Restrict FortiSandbox HTTP access to trusted administrative networks.
  • Reduce external exposure while patch status is confirmed.
  • Monitor Fortinet PSIRT updates for changed affected-version or remediation details.

Validation and detection

  • Inventory all FortiSandbox, FortiSandbox Cloud, and PaaS deployments.
  • Compare installed versions with Fortinet advisory FG-IR-26-136.
  • Confirm whether HTTP endpoints are reachable from untrusted networks.
  • Review access logs for suspicious unauthenticated HTTP activity.
  • Document remediation status and compensating controls for each instance.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-862: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-26083 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C3.95.9fortinet

Vulnerability scoring details

Base CVSS 3.1 score

9.1Critical
CVSS 3.1 vector shape for CVE-2026-26083Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
FortinetFortiSandbox5.0.0, 4.4.0, 4.2.1unaffected
FortinetFortiSandbox PaaS23.4.4374, 23.4.4350, 23.3.4329, 23.1.4245, 22.2.4151, 22.2.4134, 22.1.4113, 21.4.4072, 21.3.4055, 5.0.0, 4.4.5unaffected
FortinetFortiSandbox Cloud5.0.0, 4.4.5unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-862 · source CWE mapping

Missing Authorization

Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.