# CVE-2026-22623: Command injection in HS-AFS-S1H1

> Authenticated users can execute arbitrary commands on HIKSEMI NAS devices due to insufficient input validation.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jan 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-6qp4-m27m-3pjj

## What is CVE-2026-22623?

CVE-2026-22623 is a high-severity command injection vulnerability in HIKSEMI HS-AFS-S1H1, published on 30 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Due to insufficient input parameter validation on the interface, authenticated users of certain HIKSEMI NAS products can execute arbitrary commands on the device by crafting specific messages.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2026-22623?


## How do I fix CVE-2026-22623?

No fix has been published for CVE-2026-22623 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-22623 being exploited?

There is no known exploitation of CVE-2026-22623 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-22623 and fix it if it is affected.

What it is: CVE-2026-22623 is a high-severity command injection vulnerability in HIKSEMI HS-AFS-S1H1, published on 30 Jan 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-22623 in the wild and no public exploit code.

Affected product: HIKSEMI HS-AFS-S1H1. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-22623/ (Markdown: https://insights.sbomify.com/CVE-2026-22623/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-22623
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-22623
- OSV: https://osv.dev/vulnerability/CVE-2026-22623

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-22623/
Summaries are generated and may contain mistakes; the official description above is the record.