dbcve.org
FortiswitchaxfixedApplication · Fortinet

CVE-2026-22628

MEDIUM · 6.7 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.0.2 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

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 · unedited
An improper access control vulnerability in Fortinet FortiSwitchAXFixed 1.0.0 through 1.0.1 may allow an authenticated admin to execute system commands via a specifically crafted SSH config file.

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 · moderate confidence

Fortinet FortiSwitchAXFixed versions 1.0.0 through 1.0.1 contain an improper access control vulnerability where an authenticated administrator can execute arbitrary system commands by uploading a specially crafted SSH configuration file. The vulnerability stems from insufficient validation of SSH config file content, allowing command injection through the configuration mechanism.

MitigationUpgrade FortiSwitchAXFixed to version 1.0.2 or later to obtain the security patch. Until patches can be applied, enforce strict admin access controls and monitor for suspicious SSH config uploads.

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
FortiswitchaxfixedApplication
Affected:>= 1.0.0, < 1.0.2

CVSS 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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify FortiSwitchAXFixed version
    Log into the FortiSwitch management interface or CLI and run the command to display the system firmware version (typically via 'get system status' or 'diagnose sys version' in FortiSwitch CLI). Compare the displayed version number against the affected range 1.0.0 to 1.0.1.
    Affected if The installed version is 1.0.0 or 1.0.1 (any version >= 1.0.0 and < 1.0.2 is affected).
  2. Confirm SSH configuration upload feature access
    Locate the SSH configuration upload functionality in the FortiSwitch web UI under System > Settings or SSH management sections, or via CLI commands related to SSH configuration import.
    Affected if The SSH config upload feature is available and accessible to administrator accounts.
  3. Review administrator account privileges
    Check the list of configured administrator accounts and their privilege levels in the FortiSwitch management interface under System > Administrators or via 'show system admin' command in CLI.
    Affected if There are administrator accounts configured with permissions to upload or import SSH configuration files.
  4. Audit system logs for SSH config upload events
    Review FortiSwitch logs (via Log & Report > Event Log or 'execute log filter' and 'execute log display' commands) for entries related to SSH configuration file uploads, imports, or modifications.
    Affected if logs show recent SSH configuration file upload or import activity from administrator sessions, especially if the source or content appears unusual.

A user is affected if their FortiSwitchAXFixed version is 1.0.0 or 1.0.1 and they have administrator accounts with access to the SSH configuration upload feature.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.0.2 or later
Fixed in 1.0.2
Interim mitigation

Upgrade FortiSwitchAXFixed to version 1.0.2 or later to obtain the security patch. Until patches can be applied, enforce strict admin access controls and monitor for suspicious SSH config uploads.

Recommended fix High confidence

FortiSwitchAXFixed 1.0.2

  1. Identify the current FortiSwitchAXFixed version by logging into the admin interface or running: get system status
  2. Review current configuration and back up the configuration file before upgrading
  3. Download FortiSwitchAXFixed version 1.0.2 or later from the Fortinet support portal at https://support.fortinet.com/
  4. Upload the firmware file through the FortiSwitch management interface or via SCP/FTP
  5. Apply the firmware upgrade following FortiSwitch upgrade procedures: execute firmware upgrade <filename>
  6. After upgrade completes, verify the new version: get system status
  7. Confirm the version shows 1.0.2 or later to verify the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fortiswitchaxfixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22628 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22628 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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