Skip to main content

Fl Nat 2008 CVE-2026-22319

| EUVDEUVD-2026-12788 MEDIUM
Stack-based Buffer Overflow (CWE-121)
2026-03-18 CERTVDE
Buffer Overflow Stack Overflow Fl Nat 2008 Fl Nat 2208 Fl Nat 2304 2gc 2sfp Fl Switch 2005 Fl Switch 2008 Fl Switch 2008f Fl Switch 2016 Fl Switch 2105 Fl Switch 2108 Fl Switch 2116 Fl Switch 2204 2tc 2sfx Fl Switch 2205 Fl Switch 2206 2fx Fl Switch 2206 2fx Sm Fl Switch 2206 2fx Sm St Fl Switch 2206 2fx St Fl Switch 2206 2sfx Fl Switch 2206 2sfx Pn Fl Switch 2206c 2fx Fl Switch 2207 Fx Fl Switch 2207 Fx Sm Fl Switch 2208 Fl Switch 2208 Pn Fl Switch 2208c Fl Switch 2212 2tc 2sfx Fl Switch 2214 2fx Fl Switch 2214 2fx Sm Fl Switch 2214 2sfx Fl Switch 2214 2sfx Pn Fl Switch 2216 Fl Switch 2216 Pn Fl Switch 2303 8sp1 Fl Switch 2304 2gc 2sfp Fl Switch 2306 2sfp Fl Switch 2306 2sfp Pn Fl Switch 2308 Fl Switch 2308 Pn Fl Switch 2312 2gc 2sfp Fl Switch 2314 2sfp Fl Switch 2314 2sfp Pn Fl Switch 2316 Fl Switch 2316 Pn Fl Switch 2404 2tc 2sfx Fl Switch 2406 2sfx Fl Switch 2406 2sfx Pn Fl Switch 2408 Fl Switch 2408 Pn Fl Switch 2412 2tc 2sfx Fl Switch 2414 2sfx Fl Switch 2414 2sfx Pn Fl Switch 2416 Fl Switch 2416 Pn Fl Switch 2504 2gc 2sfp Fl Switch 2506 2sfp Fl Switch 2506 2sfp Pn Fl Switch 2508 Fl Switch 2508 Pn Fl Switch 2512 2gc 2sfp Fl Switch 2514 2sfp Fl Switch 2514 2sfp Pn Fl Switch 2516 Fl Switch 2516 Pn Fl Switch 2608 Fl Switch 2608 Pn Fl Switch 2708 Fl Switch 2708 Pn Fl Switch 5924 4gc Fl Switch 5924sfp 4gc Fl Switch Tsn 2312 2gc 2sfp Fl Switch Tsn 2314 2sfp Fl Switch Tsn 2316 Fl Switch 2316 K1 Fl Switch 2506 2Sfp K1 Fl Switch 2508 K1 Fl Switch 5916 8Gc 4Sfp Fl Switch 5924 4Sfp Fl Switch 5916Sfp 8Gc 4Sfp Phoenix Contact
4.9
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

The CVSS 3.1 vector (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H) presents a nuanced risk profile: while the attack vector is network-accessible (AV:N) with low attack complexity (AC:L), the requirement for high privileges (PR:H) significantly constrains real-world exploitability, limiting the threat actor pool to administrators or highly-trusted internal users. The vulnerability produces only availability impact (DoS) with no confidentiality or integrity compromise, reducing its severity in most threat models. However, in industrial environments where denial of service can cascade into production disruptions, safety incidents, or operational losses, the real-world impact may exceed the numeric CVSS score. The absence of reported EPSS data, KEV designation, or public POC suggests limited active exploitation in the wild. The broad affected product range (60+ firmware versions documented in EUVD-2025-104) and availability of a specific patch version (3.53) indicate this is a managed vulnerability with vendor response. Risk prioritization should be determined by network exposure of affected switches: devices directly internet-facing or accessible from untrusted administrative networks warrant immediate patching, while air-gapped or strictly access-controlled deployments present lower practical risk.

Exploit ScenarioDerived

An authenticated administrator with legitimate management access to an affected FL SWITCH device could craft a malicious HTTP POST request targeting the file installation endpoint with parameter values significantly exceeding expected buffer sizes, triggering a stack overflow that crashes the internal installation process and renders the switch's management interface unresponsive, resulting in denial of service. Alternatively, a compromised administrator account or internal threat actor with device management privileges could deliberately exploit this vulnerability to cause service disruption; while the attack requires elevated privileges and explicit knowledge of the vulnerable endpoint, the ease of crafting oversized POST requests (AC:L) makes this a practical attack vector for insiders. No public proof-of-concept has been identified, indicating the vulnerability remains primarily known to security researchers and patched deployments rather than being actively weaponized in the wild.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 18, 2026

Denial of service in Stack Overflow and Fl networking devices results from a stack-based buffer overflow in the file installation workflow that can be triggered by high-privileged attackers through oversized POST parameters. An authenticated attacker with elevated privileges can crash the affected service by exploiting this memory corruption vulnerability. No patch is currently available for the impacted products.

Earlier versions of this analysis (1)
v1 Mar 18, 2026 - 08:00 CVSS 4.9

A stack-based buffer overflow vulnerability exists in Phoenix Contact FL SWITCH industrial network switches affecting firmware versions prior to 3.53, allowing high-privileged attackers to send oversized POST parameters to the device's file installation workflow that overflow a fixed-size stack buffer, resulting in denial of service. With a CVSS score of 4.9 and high availability impact (CWE-121), the vulnerability requires administrative-level access to exploit but affects a broad range of industrial networking devices across multiple product lines. The vulnerability has been documented by CERTVDE and assigned EUVD-2025-104, with patch availability confirmed through firmware version 3.53 and later.

RemediationAI

Immediately upgrade all affected Phoenix Contact FL SWITCH and FL NAT devices to firmware version 3.53 or later, following the vendor's published firmware update procedures documented in the CERTVDE advisory (https://certvde.com/de/advisories/VDE-2025-104) and EUVD database entry. For devices where immediate patching is not operationally feasible, implement network segmentation to restrict HTTP/HTTPS access to the device management interface to only authorized administrative networks and trusted IP ranges, disable the file installation workflow if not actively required for operations, and monitor for unusual POST requests to the affected endpoints. In industrial environments, coordinate patching through change management processes to minimize production impact, and verify firmware authenticity using Phoenix Contact's provided checksums before deployment. Where applicable, deploy a reverse proxy or web application firewall in front of affected switches to validate POST parameter sizes and block oversized requests before they reach the vulnerable code path.

Affected VersionsENISA

FL SWITCH 2204-2TC-2SFX 0.0.0 <3.53
FL SWITCH TSN 2314-2SFP 0.0.0 <3.53
FL SWITCH TSN 2312-2GC-2SFP 0.0.0 <3.53
FL SWITCH 2008 0.0.0 <3.53
FL SWITCH 2212-2TC-2SFX 0.0.0 <3.53
FL SWITCH 2303-8SP1 0.0.0 <3.53
FL SWITCH 2312-2GC-2SFP 0.0.0 <3.53
FL SWITCH 2308 0.0.0 <3.53
FL NAT 2208 0.0.0 <3.53
FL SWITCH 2608 PN 0.0.0 <3.53
FL SWITCH 2414-2SFX PN 0.0.0 <3.53
FL SWITCH TSN 2316 0.0.0 <3.53
FL SWITCH 2206C-2FX 0.0.0 <3.53
FL SWITCH 2508 0.0.0 <3.53
FL SWITCH 2708 PN 0.0.0 <3.53
FL SWITCH 2008F 0.0.0 <3.53
FL SWITCH 2316 PN 0.0.0 <3.53
FL SWITCH 2316 0.0.0 <3.53
FL SWITCH 2016 0.0.0 <3.53
FL SWITCH 2506-2SFP PN 0.0.0 <3.53
FL SWITCH 5924SFP-4GC 0.0.0 <3.53
FL SWITCH 2206-2FX SM ST 0.0.0 <3.53
FL SWITCH 2206-2FX 0.0.0 <3.53
FL SWITCH 2208 PN 0.0.0 <3.53
FL SWITCH 2216 PN 0.0.0 <3.53
FL SWITCH 2508/K1 0.0.0 <3.53
FL SWITCH 5916SFP-8GC-4SFP+ 0.0.0 <3.53
FL SWITCH 2005 0.0.0 <3.53
FL SWITCH 2206-2SFX 0.0.0 <3.53
FL SWITCH 2516 0.0.0 <3.53
FL SWITCH 2608 0.0.0 <3.53
FL SWITCH 2314-2SFP 0.0.0 <3.53
FL SWITCH 2408 0.0.0 <3.53
FL SWITCH 2306-2SFP 0.0.0 <3.53
FL SWITCH 2416 PN 0.0.0 <3.53
FL SWITCH 2406-2SFX PN 0.0.0 <3.53
FL SWITCH 5916-8GC-4SFP+ 0.0.0 <3.53
FL NAT 2304-2GC-2SFP 0.0.0 <3.53
FL SWITCH 2214-2SFX 0.0.0 <3.53
FL SWITCH 2214-2SFX PN 0.0.0 <3.53
FL SWITCH 2504-2GC-2SFP 0.0.0 <3.53
FL SWITCH 2708 0.0.0 <3.53
FL SWITCH 2206-2FX ST 0.0.0 <3.53
FL SWITCH 5924-4SFP+ 0.0.0 <3.53
FL SWITCH 2214-2FX SM 0.0.0 <3.53
FL SWITCH 2306-2SFP PN 0.0.0 <3.53
FL SWITCH 2412-2TC-2SFX 0.0.0 <3.53
FL SWITCH 2105 0.0.0 <3.53
FL SWITCH 2216 0.0.0 <3.53
FL SWITCH 2506-2SFP 0.0.0 <3.53
FL SWITCH 5924-4GC 0.0.0 <3.53
FL SWITCH 2408 PN 0.0.0 <3.53
FL SWITCH 2116 0.0.0 <3.53
FL SWITCH 2404-2TC-2SFX 0.0.0 <3.53
FL NAT 2008 0.0.0 <3.53
FL SWITCH 2316/K1 0.0.0 <3.53
FL SWITCH 2206-2SFX PN 0.0.0 <3.53
FL SWITCH 2508 PN 0.0.0 <3.53
FL SWITCH 2414-2SFX 0.0.0 <3.53
FL SWITCH 2308 PN 0.0.0 <3.53
FL SWITCH 2207-FX 0.0.0 <3.53
FL SWITCH 2207-FX SM 0.0.0 <3.53
FL SWITCH 2208 0.0.0 <3.53
FL SWITCH 2205 0.0.0 <3.53
FL SWITCH 2208C 0.0.0 <3.53
FL SWITCH 2304-2GC-2SFP 0.0.0 <3.53
FL SWITCH 2214-2FX 0.0.0 <3.53
FL SWITCH 2506-2SFP/K1 0.0.0 <3.53
FL SWITCH 2416 0.0.0 <3.53
FL SWITCH 2206-2FX SM 0.0.0 <3.53
FL SWITCH 2512-2GC-2SFP 0.0.0 <3.53
FL SWITCH 2314-2SFP PN 0.0.0 <3.53
FL SWITCH 2516 PN 0.0.0 <3.53
FL SWITCH 2514-2SFP PN 0.0.0 <3.53
FL SWITCH 2406-2SFX 0.0.0 <3.53
FL SWITCH 2108 0.0.0 <3.53
FL SWITCH 2514-2SFP 0.0.0 <3.53

Affected Packages

euvd fl_nat_2008 fix: 3.53
euvd fl_nat_2208 fix: 3.53
euvd fl_nat_2304_2gc_2sfp fix: 3.53
euvd fl_switch_2005 fix: 3.53
euvd fl_switch_2008 fix: 3.53
euvd fl_switch_2008f fix: 3.53
euvd fl_switch_2016 fix: 3.53
euvd fl_switch_2105 fix: 3.53
euvd fl_switch_2108 fix: 3.53
euvd fl_switch_2116 fix: 3.53
euvd fl_switch_2204_2tc_2sfx fix: 3.53
euvd fl_switch_2205 fix: 3.53
euvd fl_switch_2206_2fx fix: 3.53
euvd fl_switch_2206_2fx_sm fix: 3.53
euvd fl_switch_2206_2fx_sm_st fix: 3.53
euvd fl_switch_2206_2fx_st fix: 3.53
euvd fl_switch_2206_2sfx fix: 3.53
euvd fl_switch_2206_2sfx_pn fix: 3.53
euvd fl_switch_2206c_2fx fix: 3.53
euvd fl_switch_2207_fx fix: 3.53
euvd fl_switch_2207_fx_sm fix: 3.53
euvd fl_switch_2208 fix: 3.53
euvd fl_switch_2208_pn fix: 3.53
euvd fl_switch_2208c fix: 3.53
euvd fl_switch_2212_2tc_2sfx fix: 3.53
euvd fl_switch_2214_2fx fix: 3.53
euvd fl_switch_2214_2fx_sm fix: 3.53
euvd fl_switch_2214_2sfx fix: 3.53
euvd fl_switch_2214_2sfx_pn fix: 3.53
euvd fl_switch_2216 fix: 3.53
euvd fl_switch_2216_pn fix: 3.53
euvd fl_switch_2303_8sp1 fix: 3.53
euvd fl_switch_2304_2gc_2sfp fix: 3.53
euvd fl_switch_2306_2sfp fix: 3.53
euvd fl_switch_2306_2sfp_pn fix: 3.53
euvd fl_switch_2308 fix: 3.53
euvd fl_switch_2308_pn fix: 3.53
euvd fl_switch_2312_2gc_2sfp fix: 3.53
euvd fl_switch_2314_2sfp fix: 3.53
euvd fl_switch_2314_2sfp_pn fix: 3.53
euvd fl_switch_2316 fix: 3.53
euvd fl_switch_2316_k1 fix: 3.53
euvd fl_switch_2316_pn fix: 3.53
euvd fl_switch_2404_2tc_2sfx fix: 3.53
euvd fl_switch_2406_2sfx fix: 3.53
euvd fl_switch_2406_2sfx_pn fix: 3.53
euvd fl_switch_2408 fix: 3.53
euvd fl_switch_2408_pn fix: 3.53
euvd fl_switch_2412_2tc_2sfx fix: 3.53
euvd fl_switch_2414_2sfx fix: 3.53
euvd fl_switch_2414_2sfx_pn fix: 3.53
euvd fl_switch_2416 fix: 3.53
euvd fl_switch_2416_pn fix: 3.53
euvd fl_switch_2504_2gc_2sfp fix: 3.53
euvd fl_switch_2506_2sfp fix: 3.53
euvd fl_switch_2506_2sfp_k1 fix: 3.53
euvd fl_switch_2506_2sfp_pn fix: 3.53
euvd fl_switch_2508 fix: 3.53
euvd fl_switch_2508_k1 fix: 3.53
euvd fl_switch_2508_pn fix: 3.53
euvd fl_switch_2512_2gc_2sfp fix: 3.53
euvd fl_switch_2514_2sfp fix: 3.53
euvd fl_switch_2514_2sfp_pn fix: 3.53
euvd fl_switch_2516 fix: 3.53
euvd fl_switch_2516_pn fix: 3.53
euvd fl_switch_2608 fix: 3.53
euvd fl_switch_2608_pn fix: 3.53
euvd fl_switch_2708 fix: 3.53
euvd fl_switch_2708_pn fix: 3.53
euvd fl_switch_5916_8gc_4sfp fix: 3.53
euvd fl_switch_5916sfp_8gc_4sfp fix: 3.53
euvd fl_switch_5924_4gc fix: 3.53
euvd fl_switch_5924_4sfp fix: 3.53
euvd fl_switch_5924sfp_4gc fix: 3.53
euvd fl_switch_tsn_2312_2gc_2sfp fix: 3.53
euvd fl_switch_tsn_2314_2sfp fix: 3.53
euvd fl_switch_tsn_2316 fix: 3.53

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 77 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability resides in the file installation workflow component of Phoenix Contact FL SWITCH industrial Ethernet switches, which are critical infrastructure networking devices used in industrial automation environments. The root cause is classified as CWE-121 (Stack-based Buffer Overflow), indicating improper input validation on HTTP POST parameters within an internal process handling device file installations. The affected CPE encompasses multiple FL SWITCH product lines including FL SWITCH 2005, 2008, 2016, 2105, 2108, 2116, 2204-2TC-2SFX, 2205, 2206-2FX, and numerous other industrial switch models, as well as FL NAT (Network Address Translation) appliances. The vulnerability is triggered through network-accessible HTTP/HTTPS endpoints that process file upload or configuration installation requests, and exploitation requires sending specially-crafted POST requests with parameter sizes exceeding the fixed stack buffer allocation.

Know when Fl Nat 2008 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 4.9 MEDIUM
AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Apr 16, 2026 - 05:29 EUVD
3.53
CVE Published
Mar 18, 2026 - 07:34 nvd
MEDIUM 4.9

DescriptionCVE.org

A stack-based buffer overflow in the device's file installation workflow allows a high-privileged attacker to send oversized POST parameters that overflow a fixed-size stack buffer within an internal process, resulting in a DoS attack.

Executive ViewAI

Why It Matters

CVE-2026-22319 presents moderate security risk, a stack-based buffer overflow vulnerability rated CVSS 4.9. Exploitation could cause memory corruption or application crashes. Organizations should apply vendor updates when available and monitor for exploitation.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: enable ASLR/DEP, apply network segmentation.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Low

Priority Score

24
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

Related Vulnerabilities in Device Stack-Based Buffer Overflow Vulnerabilities

View all 3

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy