Skip to main content
Menu
CVEs

HanLP unsafe deserialization in RNNLanguageModel model loading

CVE-2026-133836Published , updated

5.3MediumCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

hankcs HanLP has a deserialization flaw in its RNNLanguageModel.load_language_model function, where manipulating the model_file argument leads to deserialization. An attacker can reach it remotely over the network with a low-privilege login and no user action.

Written by a model

Original description

A vulnerability has been found in hankcs HanLP up to 2.1.6. The affected element is the function RNNLanguageModel.load_language_model of the file hanlp/layers/embeddings/contextual_string_embedding.py. Such manipulation of the argument model_file leads to deserialization. The attack may be performed from remote. The exploit has been disclosed to the public and may be used. Upgrading to version 2.1.7 is sufficient to fix this issue. The name of the patch is 6962907e37dfa467fa6dee164b5b1d0a904b24db. The affected component should be upgraded.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133836 (hankcs HanLP contextual_string_embedding.py RNNLanguageModel.load_language_model deserialization), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133836 (entry last updated 2026-11-20):
Affected:
- hankcs HanLP: versions 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4, 2.1.5, 2.1.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133836 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133836 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/hankcs/HanLP/commit/6962907e37dfa467fa6dee164b5b1d0a904b24db
- https://vuldb.com/vuln/441459
- https://vuldb.com/vuln/441459/cti
- https://vuldb.com/cve/CVE-2026-133836
- https://vuldb.com/submit/1051822
- https://github.com/hankcs/HanLP/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133836
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133836"}.

Affected versions

cve.now Index

8Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity5.3/10CVSS 5.3
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 27 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now

Evidence 9

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133836
RecordNVD · CVE-2026-133836
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
Exploitgist.github.com · zewolkt3939/8f665b80c0878e5efde324c255d1abcd
Other links 6
AdvisoryVulDB · Advisory #441459
AdvisoryVulDB · Threat intelligence #441459
AdvisoryVulDB · CVE-2026-133836 record
AdvisoryVulDB · Submission #1051822
PatchGitHub · hankcs/HanLP · Commit 6962907e
RepositoryGitHub · hankcs/HanLP · Repository

Questions about CVE-2026-133836

Is CVE-2026-133836 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133836?

HanLP: versions 2.1.0, 2.1.1, 2.1.2, 2.1.3, 2.1.4 and 2 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.