dbcve.org
Stack-based Buffer OverflowWeakness · CWE-121

CVE-2026-22320

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 stack-based buffer overflow in the CLI's TFTP file‑transfer command handling allows a low-privileged attacker with Telnet/SSH access to trigger memory corruption by supplying unexpected or oversized filename input. Exploitation results in the corruption of the internal buffer, causing the CLI and web dashboard to become unavailable and leading to a denial of service.

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

A stack-based buffer overflow vulnerability exists in the CLI's TFTP file-transfer command handling. By supplying unexpected or oversized filename input through Telnet/SSH, a low-privileged attacker can corrupt stack memory, causing the CLI and web dashboard to become unavailable.

MitigationImplement strict input length validation and bounds checking on the filename parameter in the TFTP command handler to prevent buffer overflow. Consider applying any available vendor patches for the affected system.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify CLI access method is enabled
    Check if Telnet or SSH access is enabled on the device. This is typically found in device management settings, network services config, or security/access control lists.
    Affected if Telnet or SSH access is enabled and exposes the CLI to network users
  2. Confirm TFTP CLI command exists
    Access the CLI via Telnet or SSH and attempt to invoke the TFTP file-transfer command. Look for TFTP-related commands in the command help (usually accessed by typing '?' or 'help').
    Affected if TFTP command is available in the CLI interface
  3. Check for input length restrictions on TFTP filename
    If TFTP command exists, review any configuration that limits the filename parameter length. Inspect the CLI configuration for TFTP-related settings or input validation rules.
    Affected if No explicit maximum filename length is configured or enforced in the TFTP command handler
  4. Identify installed software version
    Query the device or system for its firmware/software version. This is usually done via CLI command (such as 'show version', 'system info', or similar), web interface, or management console.
    Affected if The installed version falls within an affected range (compare to vendor-advisory version numbers if available) or cannot be determined to be patched
  5. Test for vulnerability presence
    If you have a test environment, attempt to execute the TFTP command with an oversized filename parameter (e.g., a string exceeding typical filename lengths). Monitor for unexpected behavior such as CLI crash, connection drop, or error messages indicating buffer issues.
    Affected if The CLI becomes unresponsive, crashes, or exhibits abnormal behavior when processing long filename input in TFTP commands
  6. Review vendor security advisories
    Check the product vendor's official security advisory or CVE database entry for CVE-2026-22320 to confirm if your specific product model and version are listed as affected.
    Affected if Your product model and version match those listed as vulnerable in official vendor documentation

You are affected if the CLI TFTP command is accessible via Telnet/SSH and lacks proper input length validation on the filename parameter, or if your installed version matches vendor-advisory affected versions.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input length validation and bounds checking on the filename parameter in the TFTP command handler to prevent buffer overflow. Consider applying any available vendor patches for the affected system.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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