# CVE-2024-53427: Memory corruption in jq

> A stack-based buffer overflow in jq allows attackers to execute arbitrary code or cause denial of service via crafted input.

- **Severity:** High 8.1 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Feb 2025
- **Updated:** 28 Mar 2025
- **Also known as:** ALPINE-CVE-2024-53427, AZL-57376, BELL-CVE-2024-53427, CVE-2024-23338, CVE-2025-25726, DEBIAN-CVE-2024-53427, ECHO-9e32-4170-f69d, GHSA-8mxc-vqrq-gcm8, GHSA-x6c3-qv5r-7q22, UBUNTU-CVE-2024-53427, openSUSE-SU-2025:15161-1

## What is CVE-2024-53427?

CVE-2024-53427 is a high-severity memory corruption vulnerability in jqlang jq, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

decNumberCopy in decNumber.c in jq through 1.7.1 does not properly consider that NaN is interpreted as numeric, which has a resultant stack-based buffer overflow and out-of-bounds write, as demonstrated by use of --slurp with subtraction, such as a filter of .-. when the input has a certain form of digit string with NaN (e.g., "1 NaN123" immediately followed by many more digits).

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2024-53427?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jq` | openSUSE:Tumbleweed | All versions | 1.7.1-3.1 |

Products: Jqlang Jq.

## How do I fix CVE-2024-53427?

Upgrade to a fixed version.

## Is CVE-2024-53427 being exploited?

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

## Other vulnerabilities in jqlang jq

- [CVE-2026-32316](https://insights.sbomify.com/CVE-2026-32316/): jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow (high 8.2)
- [CVE-2025-48060](https://insights.sbomify.com/CVE-2025-48060/): AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt) (high 7.7)
- [CVE-2023-49355](https://insights.sbomify.com/CVE-2023-49355/): Memory corruption in n/a (high 7.5)
- [CVE-2026-49839](https://insights.sbomify.com/CVE-2026-49839/): jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow (high 7.1)
- [CVE-2026-54679](https://insights.sbomify.com/CVE-2026-54679/): jq: potential integer overflow in jvp_string_append (medium 6.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-53427 and fix it if it is affected.

What it is: CVE-2024-53427 is a high-severity memory corruption vulnerability in jqlang jq, published on 26 Feb 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-53427 exists.

Affected product: jqlang jq. 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-2024-53427/ (Markdown: https://insights.sbomify.com/CVE-2024-53427/index.md)
```

## Sources

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

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