CVE-2026-22905VulnerabilityPublished 9 Feb 2026

CVE-2026-22905: WAGO 0852-1322 · Path Traversal

Affects WAGO 0852-1322Source CVE Database V5

Not known to be exploited · CVSS 7.5 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.5High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
WAGO0852-1322	Affected <=2.64	Fixed in–
WAGO0852-1328	Affected <=2.64	Fixed in–
WAGO0852-1322	Affected =2.64	Fixed in–
WAGO0852-1328	Affected =2.64	Fixed in–

AI-suggested

1. Immediate network-level controls: Isolate WAGO 0852-1322 devices within segmented network zones with strict access controls to limit exposure to untrusted networks. 2. Implement Web Application Firewall (WAF) rules to detect and block path traversal patterns in HTTP requests targeting the device's web interface. 3. Monitor network traffic for unusual requests containing path traversal sequences or attempts to access CGI endpoints. 4. Coordinate with WAGO for official patches or firmware updates addressing CVE-2026-22905; apply updates promptly once available. 5. If patches are unavailable, consider disabling or restricting access to vulnerable web interfaces or CGI endpoints where feasible. 6. Employ strong authentication and VPN access for remote management to reduce attack surface. 7. Conduct regular security assessments and penetration tests focusing on industrial control systems to detect similar vulnerabilities. 8. Maintain an inventory of all WAGO devices and ensure they are included in vulnerability management programs. 9. Educate operational technology (OT) and IT staff about this vulnerability and signs of exploitation attempts. 10. Implement logging and alerting mechanisms to capture unauthorized access attempts to the device.

Description

CVE-2026-22905 is a high-severity path traversal vulnerability in the WAGO 0852-1322 device that allows unauthenticated remote attackers to bypass authentication by exploiting insufficient URI validation. Attackers can use path traversal sequences to access protected CGI endpoints and download sensitive configuration files without authorization. This vulnerability does not require user interaction or privileges and can be exploited remotely over the network. While no known exploits are currently reported in the wild, the impact on confidentiality is significant as attackers can access sensitive data. The vulnerability affects all versions of the product as identified. European organizations using WAGO 0852-1322 devices, especially in critical infrastructure sectors, are at risk. Mitigation requires strict URI validation, patching by the vendor, and network-level protections such as segmentation and access controls. Countries with high industrial automation adoption and critical infrastructure reliance on WAGO products are most likely to be affected.

Impact

For European organizations, especially those in industrial automation, manufacturing, and critical infrastructure sectors that deploy WAGO 0852-1322 devices, this vulnerability presents a serious risk. Unauthorized access to protected CGI endpoints and configuration files can lead to exposure of sensitive operational parameters, network configurations, and potentially credentials. This breach of confidentiality could enable attackers to map the network, plan further intrusions, or disrupt operations indirectly. Given the device's role in automation and control, attackers might leverage the information gained to interfere with industrial processes, causing operational disruptions or safety hazards. The lack of required authentication and ease of remote exploitation increase the likelihood of attacks, particularly in environments with exposed or poorly segmented networks. The vulnerability could also undermine compliance with European data protection and cybersecurity regulations, such as NIS2 and GDPR, if sensitive data is compromised. The absence of known exploits currently provides a window for proactive mitigation, but the high severity score indicates urgent attention is necessary to prevent potential exploitation.

Summary

CVE-2026-22905 is a path traversal vulnerability classified under CWE-22 found in the WAGO 0852-1322 device. The flaw arises from improper limitation of pathname inputs to restricted directories, allowing an unauthenticated remote attacker to bypass authentication mechanisms. Specifically, the device's web interface fails to properly validate Uniform Resource Identifiers (URIs), enabling attackers to craft malicious requests containing path traversal sequences such as '/js/../cgi-bin/post.cgi'. This manipulation tricks the system into accessing protected Common Gateway Interface (CGI) endpoints and configuration files that should be restricted. The vulnerability is remotely exploitable without any authentication or user interaction, increasing its risk profile. The CVSS v3.1 score is 7.5 (high), reflecting the ease of exploitation (network attack vector, no privileges required, no user interaction) and the high confidentiality impact due to unauthorized access to sensitive configuration data. Although no public exploits have been reported yet, the vulnerability poses a significant threat to the confidentiality of device configurations and potentially the broader network if leveraged for further attacks. The affected product version is listed as 0.0.0, indicating all current versions are vulnerable until patched. The vulnerability was published on February 9, 2026, and assigned by CERTVDE. No official patches or mitigations have been linked yet, underscoring the need for immediate defensive measures.

CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

certvde.com/de/advisories/VDE-2026-004 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 16 Feb 2026, 13:29 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats