dbcve.org
FortiswitchaxfixedApplication · Fortinet

CVE-2026-22627

HIGH · 8.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 1.0.2 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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
A buffer copy without checking size of input ('classic buffer overflow') vulnerability in Fortinet FortiSwitchAXFixed 1.0.0 through 1.0.1 may allow an unauthenticated attacker within the same adjacent network to execute unauthorized code or commands on the device via sending a crafted LLDP packet.

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 confidence

Classic buffer overflow vulnerability in FortiSwitchAXFixed versions 1.0.0-1.0.1 where the device fails to validate the size of incoming LLDP packets before copying into a fixed-size buffer. An unauthenticated attacker on the adjacent network can send a crafted LLDP packet to overflow the buffer and achieve arbitrary code/command execution.

MitigationApply the vendor-provided patch/upgrade to a fixed version of FortiSwitchAXFixed firmware. If immediate patching is not feasible, implement network segmentation to restrict LLDP traffic to trusted sources only.

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

CVSS:3.1/AV:A/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 checks

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

  1. Identify FortiSwitchAXFixed model
    Access the FortiSwitch CLI or GUI and run 'get system status' or check the device model information to confirm the device is FortiSwitchAXFixed
    Affected if Device model is FortiSwitchAXFixed and firmware version is 1.0.0, 1.0.1, or any version below 1.0.2
  2. Check installed firmware version
    In FortiSwitch CLI, run 'get system status' or 'fwm -d status' to display the current firmware version
    Affected if Firmware version is 1.0.0, 1.0.1, or between 1.0.0 and 1.0.1 inclusive (the affected range)
  3. Verify LLDP is enabled
    In FortiSwitch CLI, run 'get switch lldp status' or check the GUI under Switch > LLDP to see if Link Layer Discovery Protocol is enabled on any interface
    Affected if LLDP is enabled on any interface - this is required for the vulnerability to be exploitable
  4. Check LLDP configuration on all interfaces
    Run 'show switch lldp' to review the global LLDP settings and verify which interfaces have LLDP transmit/receive enabled
    Affected if LLDP receive or transmit is enabled on any interface, exposing the device to the crafted packet attack

The device is affected if it is a FortiSwitchAXFixed running firmware version 1.0.0 or 1.0.1 (or any version below 1.0.2) AND LLDP is enabled on one or more interfaces.

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

Apply the vendor-provided patch/upgrade to a fixed version of FortiSwitchAXFixed firmware. If immediate patching is not feasible, implement network segmentation to restrict LLDP traffic to trusted sources only.

Recommended fix High confidence

FortiSwitchAXFixed 1.0.2

  1. Backup the current FortiSwitchAXFixed configuration before initiating any upgrade
  2. Upgrade FortiSwitchAXFixed from version 1.0.0 or 1.0.1 to version 1.0.2 or later
  3. After upgrade, verify the device is running version 1.0.2 or higher using the CLI command 'get system status' or via FortiManager/FortiCloud
  4. Restore the configuration if needed and validate network services are functioning normally
Caveat Review Fortinet release notes for FortiSwitchAXFixed 1.0.2 for any configuration or behavior changes before upgrading; test in a non-production environment first

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

Fix this in Fortiswitchaxfixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22627 — 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-22627 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