# CVE-2026-19826: alldatacenter alldata xxl-rpc Listener HessianSerializer.java Hessian2Input.readObject deserialization

> Remote attackers can execute arbitrary code via unsafe Hessian deserialization in the alldata xxl-rpc Listener component.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 14 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-fq8p-5fjc-mw7x

## What is CVE-2026-19826?

CVE-2026-19826 is a medium-severity unsafe deserialization vulnerability in alldatacenter alldata, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was detected in alldatacenter alldata up to 0.6.8. This affects the function Hessian2Input.readObject of the file /serialize/impl/HessianSerializer.java of the component xxl-rpc Listener. The manipulation results in deserialization. The attack may be performed from remote. The exploit is now public and may be used. The project closed the issue report as "not planned" without any further explanation.

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

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


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

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

## Is CVE-2026-19826 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19826 is a medium-severity unsafe deserialization vulnerability in alldatacenter alldata, published on 14 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-19826 exists.

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

## Sources

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

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