# CVE-2026-120232: Horizon DataSys Reboot Restore Standard Kernel Driver shield.sys sub_23908 memory corruption


- **Severity:** Critical 9.3 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 1 Nov 2026
- **Updated:** 2 Nov 2026
- **Also known as:** GHSA-4wxp-49m2-xx54

## What is CVE-2026-120232?

CVE-2026-120232 is a critical vulnerability in Horizon DataSys Reboot Restore Standard, published on 1 Nov 2026. 

### Official description

A vulnerability was identified in Horizon DataSys Reboot Restore Standard up to 13.2. The impacted element is the function sub_23908 in the library shield.sys of the component Kernel Driver. Such manipulation leads to memory corruption. The attack can only be performed from a local environment. The exploit is publicly available and might be used. A fix is planned for the upcoming release.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

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

## Is CVE-2026-120232 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120232 exists.

Public exploit code:

- https://github.com/Element2023H/CVE-2026-120232 (github_poc): https://github.com/Element2023H/CVE-2026-120232
- https://github.com/Element2023H/CVE-2026-120232-RUST-POC (github_poc): https://github.com/Element2023H/CVE-2026-120232-RUST-POC

## Fix prompt for AI coding agents

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

What it is: CVE-2026-120232 is a critical vulnerability in Horizon DataSys Reboot Restore Standard, published on 1 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120232 exists.

Affected product: Horizon DataSys Reboot Restore Standard. 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-120232/ (Markdown: https://insights.sbomify.com/CVE-2026-120232/index.md)
```

## Sources

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

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