# CVE-2026-110681: Cpanel::JSON::XS versions before 4.80 for Perl use the parent interpreter's scalars from a parser object cloned into a new ithread.

> A use-after-free vulnerability in Cpanel::JSON::XS allows attackers to cause crashes or potentially execute code via thread cloning issues.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-109869, DEBIAN-CVE-2026-110681, GHSA-rmwh-p89p-h6wq, UBUNTU-CVE-2026-110681

## What is CVE-2026-110681?

CVE-2026-110681 is an use after free vulnerability, published on 19 Oct 2026. 

### Official description

Cpanel::JSON::XS versions before 4.80 for Perl use the parent interpreter's scalars from a parser object cloned into a new ithread.

A parser object holds its callbacks and its incremental parse buffer as raw scalar pointers. When a thread is created, these are copied into the new interpreter unchanged, so the child's parser uses, and later frees, scalars that belong to the parent and may already have been freed there.

A parser created before a thread starts and used inside it can call freed callbacks, corrupt reference counts and crash the process.

Weakness: CWE-416 (Use After Free)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110681 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110681 is an use after free vulnerability, published on 19 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110681 in the wild and no public exploit code.

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-110681/ (Markdown: https://insights.sbomify.com/CVE-2026-110681/index.md)
```

## Sources

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

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