# CVE-2026-14803: Mojo::JSON versions before 9.47 for Perl allow memory exhaustion via unbounded recursion in the pure-Perl decoder

> Attackers can cause denial of service via memory exhaustion in the pure-Perl JSON decoder when the XS module is disabled or missing.

- **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
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Jul 2026
- **Updated:** 6 Jul 2026
- **Also known as:** AZL-92078, CVE-2026-68914, DEBIAN-CVE-2026-14803, GHSA-fp7f-j7qv-4qww, MGASA-2026-0269, OESA-2026-3159, UBUNTU-CVE-2026-14803

## What is CVE-2026-14803?

CVE-2026-14803 is a medium-severity denial of service vulnerability in SRI Mojo::JSON, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Mojo::JSON versions before 9.47 for Perl allow memory exhaustion via unbounded recursion in the pure-Perl decoder.

The pure-Perl decode path (`_decode_value` dispatching to `_decode_array` and `_decode_object`) recurses with no depth limit, so a small deeply nested JSON document can consume excessive memory.

This path is the default when Cpanel::JSON::XS is not installed or `MOJO_NO_JSON_XS=1` is set; the Cpanel::JSON::XS fast path is not affected.

Any caller that decodes an untrusted JSON body, for example `Mojo::Message::json` reached through `$c->req->json`, can exhaust process memory and cause denial of service.

Weakness: CWE-674 (Uncontrolled Recursion)

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


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

Upgrade to a fixed version.

## Is CVE-2026-14803 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-14803 is a medium-severity denial of service vulnerability in SRI Mojo::JSON, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-14803 in the wild and no public exploit code.

Affected product: SRI Mojo::JSON. 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-14803/ (Markdown: https://insights.sbomify.com/CVE-2026-14803/index.md)
```

## Sources

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

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