CVE-2026-22625VulnerabilityPublished 30 Jan 2026Updated 27 Feb 2026

CVE-2026-22625: HIKSEMI HS-AFS-S1H1 · Path Traversal

Affects HIKSEMI HS-AFS-S1H1Source CVE Database V5

Not known to be exploited · CVSS 4.6 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

4.6Medium

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

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

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

Attack Vector: Physical
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: Physical: The attack requires the attacker to physically touch or manipulate the vulnerable component. Physical interaction may be brief or persistent.
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 30 Jan 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-25.

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
HIKSEMIHS-AFS-S1H1	Affected =V5.10.10_Build_251126	Fixed in–

AI-suggested

1. Restrict network access to the HIKSEMI HS-AFS-S1H1 NAS device by implementing strict firewall rules and network segmentation to limit exposure to trusted management networks only. 2. Monitor network traffic for unusual or unauthorized access attempts targeting the NAS device, especially requests involving suspicious filename patterns indicative of path traversal attempts. 3. Regularly audit and review access logs on the NAS device to detect potential reconnaissance or exploitation attempts. 4. Engage with the vendor to obtain and apply security patches or firmware updates as soon as they become available to address this vulnerability. 5. If patching is delayed, consider deploying virtual patching techniques such as web application firewalls (WAFs) or intrusion prevention systems (IPS) with custom rules to detect and block path traversal patterns. 6. Educate network administrators and security teams about this vulnerability to ensure timely response and monitoring. 7. Implement strong authentication and access controls on the NAS device to reduce risk from insider threats, even though the vulnerability does not require authentication.

Description

Improper handling of filenames in certain HIKSEMI NAS products may lead to the exposure of sensitive system files.

Impact

The primary impact of this vulnerability is unauthorized disclosure of sensitive system files, which can include configuration files, credentials, or other critical data stored on the NAS device. Exposure of such information can facilitate further attacks such as privilege escalation, lateral movement, or targeted exploitation of other vulnerabilities. Organizations relying on HIKSEMI HS-AFS-S1H1 devices for critical data storage or backup could face confidentiality breaches, potentially leading to data leaks or compliance violations. Since the vulnerability does not affect integrity or availability, direct disruption or data manipulation is unlikely. However, the information gained could indirectly compromise system security. The requirement for network access reduces the risk from remote attackers but does not eliminate threats from insider attackers or attackers who gain network access through other means. The absence of known exploits limits immediate risk but does not preclude future exploitation.

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

hiksemitech.com/en/hiksemi/support/security-advisory.html (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Feb 2026, 23:05 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats