CVE-2026-22318
Last modified
CVE-2026-22318 is a medium-severity vulnerability rated 4.9/10 on the CVSS scale. A stack-based buffer overflow vulnerability in the device's file transfer parameter workflow allows a high-privileged attacker to send oversized POST parameters, causing memory corruption in an internal process, resulting in a DoS attack.. EPSS estimates a 0.34% chance of exploitation in the next 30 days.
Description
A stack-based buffer overflow vulnerability in the device's file transfer parameter workflow allows a high-privileged attacker to send oversized POST parameters, causing memory corruption in an internal process, resulting in a DoS attack.
Metrics
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Phoenix Contact | FL SWITCH 2005 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2008 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2016 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2105 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2108 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2116 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2204-2TC-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2205 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206-2FX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206-2FX SM | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206-2FX SM ST | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206-2FX ST | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206-2SFX PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2206C-2FX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2207-FX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2207-FX SM | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2208 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2208 PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2208C | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2212-2TC-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2214-2FX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2214-2FX SM | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2214-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2214-2SFX PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2216 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2216 PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2304-2GC-2SFP | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2306-2SFP | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2306-2SFP PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2308 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2308 PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2312-2GC-2SFP | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2314-2SFP | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2314-2SFP PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2316 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2316 PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2404-2TC-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2406-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2406-2SFX PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2408 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2408 PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2412-2TC-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2414-2SFX | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2414-2SFX PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2416 | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2416 PN | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2504-2GC-2SFP | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2506-2SFP | >= 0.0.0, < 3.53 |
| Phoenix Contact | FL SWITCH 2506-2SFP PN | >= 0.0.0, < 3.53 |
Showing 50 of 77 affected configurations. See the CNA advisory for the full list.
References
Timeline
- Published
- Last Modified
- Status
- Awaiting Analysis
Frequently Asked Questions
What is CVE-2026-22318?
How severe is CVE-2026-22318?
How do I fix CVE-2026-22318?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-22312The device has a webserver that exposes a REST API authentic…8.6
- CVE-2026-22313The device has a webserver that exposes a REST API authentic…9.1
- CVE-2026-22314Improper Control of Generation of Code ('Code Injection') vu…9
- CVE-2026-22315Incorrect Privilege Assignment vulnerability in Mesalvo Meon…7.2
- CVE-2026-22316A remote attacker with user privileges for the webUI can use…6.5
- CVE-2026-22317A command injection vulnerability in the device’s Root CA ce…7.2
- CVE-2026-22319A stack-based buffer overflow in the device's file installat…4.9
- CVE-2026-2232The Product Table and List Builder for WooCommerce Lite plug…7.5
- CVE-2026-22320A stack-based buffer overflow in the CLI's TFTP file‑transfe…6.5
- CVE-2026-22321A stack-based buffer overflow in the device's Telnet/SSH CLI…5.3
- CVE-2026-22322A stored cross‑site scripting (XSS) vulnerability in the Lin…7.1
- CVE-2026-22323A CSRF vulnerability in the Link Aggregation configuration i…7.1
Are you affected by CVE-2026-22318?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
