# CVE-2026-110675: Cpanel::JSON::XS versions from 4.33 before 4.80 for Perl accept malformed UTF-8 in bare hash keys under allow_barekey in decode_hv.

> Attackers can cause application crashes by sending malformed UTF-8 in bare JSON keys when specific decoding options are enabled.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-109839, DEBIAN-CVE-2026-110675, GHSA-9hvc-g7pw-p4j7, UBUNTU-CVE-2026-110675

## What is CVE-2026-110675?

CVE-2026-110675 is a high-severity denial of service vulnerability, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cpanel::JSON::XS versions from 4.33 before 4.80 for Perl accept malformed UTF-8 in bare hash keys under allow_barekey in decode_hv.

With utf8 and allow_barekey, which relaxed enables, a quoted key is validated as UTF-8 but a bare key's bytes are stored as a UTF-8 flagged string without any check. Malformed UTF-8, control bytes and backslashes reach the decoded hash, while malformed UTF-8 and control bytes in a quoted key or a value are rejected.

Later operations on the key, including lc, uc or encoding the hash again, die with a malformed UTF-8 error.

Weakness: CWE-1286 (Improper Validation of Syntactic Correctness of Input)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110675 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110675 is a high-severity denial of service vulnerability, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-110675 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-110675/ (Markdown: https://insights.sbomify.com/CVE-2026-110675/index.md)
```

## Sources

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

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