Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.34% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-22319High confidence
Stack-Based Buffer Overflow in File Install Parameter Handling
Phoenix Contact · FL SWITCH 2005
4.9MediumCVSS 3.1
Scheduled
Fix not verifiedMedium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityMedium→Operational priority:Medium, unchanged from published severity.unchanged
Compensating controls
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Phoenix Contact FL SWITCH 2005 and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority.
Fix not verified01
What, why and how
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.
What
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.
Why
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
How
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
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.
Why
A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
How
An attacker operating through a network path may attempt exploitation with elevated privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Stack-based Buffer Overflow → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- High: elevated access is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-121 ↗
CWE-121: Stack-based Buffer Overflow. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRHighPrivileges required: The attacker needs elevated or administrative privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix not verified
- Affected
- FL SWITCH 2005: 0.0.0 < 3.53
- FL SWITCH 2008: 0.0.0 < 3.53
- FL SWITCH 2016: 0.0.0 < 3.53
- FL SWITCH 2105: 0.0.0 < 3.53
- FL SWITCH 2108: 0.0.0 < 3.53
- FL SWITCH 2116: 0.0.0 < 3.53
- FL SWITCH 2204-2TC-2SFX: 0.0.0 < 3.53
- FL SWITCH 2205: 0.0.0 < 3.53
- FL SWITCH 2206-2FX: 0.0.0 < 3.53
- FL SWITCH 2206-2FX SM: 0.0.0 < 3.53
- FL SWITCH 2206-2FX SM ST: 0.0.0 < 3.53
- FL SWITCH 2206-2FX ST: 0.0.0 < 3.53
- FL SWITCH 2206-2SFX: 0.0.0 < 3.53
- FL SWITCH 2206-2SFX PN: 0.0.0 < 3.53
- FL SWITCH 2206C-2FX: 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 2208 PN: 0.0.0 < 3.53
- FL SWITCH 2208C: 0.0.0 < 3.53
- FL SWITCH 2212-2TC-2SFX: 0.0.0 < 3.53
- FL SWITCH 2214-2FX: 0.0.0 < 3.53
- FL SWITCH 2214-2FX SM: 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 2216: 0.0.0 < 3.53
- FL SWITCH 2216 PN: 0.0.0 < 3.53
- FL SWITCH 2304-2GC-2SFP: 0.0.0 < 3.53
- FL SWITCH 2306-2SFP: 0.0.0 < 3.53
- FL SWITCH 2306-2SFP PN: 0.0.0 < 3.53
- FL SWITCH 2308: 0.0.0 < 3.53
- FL SWITCH 2308 PN: 0.0.0 < 3.53
- FL SWITCH 2312-2GC-2SFP: 0.0.0 < 3.53
- FL SWITCH 2314-2SFP: 0.0.0 < 3.53
- FL SWITCH 2314-2SFP PN: 0.0.0 < 3.53
- FL SWITCH 2316: 0.0.0 < 3.53
- FL SWITCH 2316 PN: 0.0.0 < 3.53
- FL SWITCH 2404-2TC-2SFX: 0.0.0 < 3.53
- FL SWITCH 2406-2SFX: 0.0.0 < 3.53
- FL SWITCH 2406-2SFX PN: 0.0.0 < 3.53
- FL SWITCH 2408: 0.0.0 < 3.53
- FL SWITCH 2408 PN: 0.0.0 < 3.53
- FL SWITCH 2412-2TC-2SFX: 0.0.0 < 3.53
- FL SWITCH 2414-2SFX: 0.0.0 < 3.53
- FL SWITCH 2414-2SFX PN: 0.0.0 < 3.53
- FL SWITCH 2416: 0.0.0 < 3.53
- FL SWITCH 2416 PN: 0.0.0 < 3.53
- FL SWITCH 2504-2GC-2SFP: 0.0.0 < 3.53
- FL SWITCH 2506-2SFP: 0.0.0 < 3.53
- FL SWITCH 2506-2SFP PN: 0.0.0 < 3.53
- FL SWITCH 2508: 0.0.0 < 3.53
- FL SWITCH 2508 PN: 0.0.0 < 3.53
- FL SWITCH 2512-2GC-2SFP: 0.0.0 < 3.53
- FL SWITCH 2514-2SFP: 0.0.0 < 3.53
- FL SWITCH 2514-2SFP PN: 0.0.0 < 3.53
- FL SWITCH 2516: 0.0.0 < 3.53
- FL SWITCH 2516 PN: 0.0.0 < 3.53
- FL SWITCH 2608: 0.0.0 < 3.53
- FL SWITCH 2608 PN: 0.0.0 < 3.53
- FL SWITCH 2708: 0.0.0 < 3.53
- FL SWITCH 2708 PN: 0.0.0 < 3.53
- FL SWITCH 2303-8SP1: 0.0.0 < 3.53
- FL NAT 2008: 0.0.0 < 3.53
- FL NAT 2208: 0.0.0 < 3.53
- FL NAT 2304-2GC-2SFP: 0.0.0 < 3.53
- FL SWITCH 2008F: 0.0.0 < 3.53
- FL SWITCH 2316/K1: 0.0.0 < 3.53
- FL SWITCH 2506-2SFP/K1: 0.0.0 < 3.53
- FL SWITCH 2508/K1: 0.0.0 < 3.53
- FL SWITCH TSN 2316: 0.0.0 < 3.53
- FL SWITCH TSN 2312-2GC-2SFP: 0.0.0 < 3.53
- FL SWITCH TSN 2314-2SFP: 0.0.0 < 3.53
- FL SWITCH 5924-4GC: 0.0.0 < 3.53
- FL SWITCH 5916-8GC-4SFP+: 0.0.0 < 3.53
- FL SWITCH 5924SFP-4GC: 0.0.0 < 3.53
- FL SWITCH 5924-4SFP+: 0.0.0 < 3.53
- FL SWITCH 5916SFP-8GC-4SFP+: 0.0.0 < 3.53
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 18 Mar 2026 · Last source change 18 Mar 2026, 13:39 UTC · CWE-121 · Stack-based Buffer Overflow
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-12788
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD awaiting enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.