# CVE-2026-110674: Cpanel::JSON::XS versions from 4.33 before 4.80 for Perl miss duplicate non-ASCII bare keys, allowing type confusion under dupkeys_as_arrayref in decode_hv.


- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-109836, DEBIAN-CVE-2026-110674, GHSA-c92x-ph36-v6p2, UBUNTU-CVE-2026-110674

## What is CVE-2026-110674?

CVE-2026-110674 is a medium-severity vulnerability, published on 19 Oct 2026. 

### Official description

Cpanel::JSON::XS versions from 4.33 before 4.80 for Perl miss duplicate non-ASCII bare keys, allowing type confusion under dupkeys_as_arrayref in decode_hv.

With allow_barekey, which relaxed enables, a bare key containing a non-ASCII byte is stored as UTF-8 but looked up as raw bytes, so a repeated key escapes the duplicate-key check and replaces the earlier value.

From 4.41, under dupkeys_as_arrayref, a bare repeat replaces the array that collects a key's values with a plain value, and the next quoted repeat pushes onto that value as if it were an array. A JSON integer there is dereferenced as a pointer.

Untrusted JSON decoded with relaxed and dupkeys_as_arrayref can crash the process or dereference an address chosen by a JSON number.

Weakness: CWE-843 (Access of Resource Using Incompatible Type), CWE-176 (Improper Handling of Unicode Encoding)

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


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

Upgrade to a fixed version.

## Is CVE-2026-110674 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110674 is a medium-severity vulnerability, published on 19 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-110674 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-110674/ (Markdown: https://insights.sbomify.com/CVE-2026-110674/index.md)
```

## Sources

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

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