# CVE-2026-112079: hankcs HanLP torch_util.py load_word2vec_as_vocab_tensor deserialization

> Remote attackers can execute arbitrary code via unsafe deserialization in HanLP's word2vec loading function, requiring immediate attention from users of this NLP library.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-q7j8-9vmr-j8qv

## What is CVE-2026-112079?

CVE-2026-112079 is a medium-severity unsafe deserialization vulnerability in hankcs HanLP, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been found in hankcs HanLP up to 2.1.0-beta.64. The affected element is the function load_word2vec_as_vocab_tensor of the file hanlp/utils/torch_util.py. The manipulation of the argument vectors.vocab leads to deserialization. The attack is possible to be carried out remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-502 (Deserialization of Untrusted Data), CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2026-112079 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-112079 is a medium-severity unsafe deserialization vulnerability in hankcs HanLP, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112079 exists.

Affected product: hankcs HanLP. 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-112079/ (Markdown: https://insights.sbomify.com/CVE-2026-112079/index.md)
```

## Sources

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

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