# CVE-2025-48060: AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)

> A heap-buffer-overflow in jq's string formatting function can cause crashes or potentially allow code execution when processing malicious JSON input.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 May 2025
- **Updated:** 3 Nov 2025
- **Also known as:** ALPINE-CVE-2025-48060, AZL-61968, AZL-61974, BELL-CVE-2025-48060, CLSA-2025-1752749203, DEBIAN-CVE-2025-48060, DLA-4307-1, ECHO-1a73-323b-ca34, GHSA-p7rr-28xf-3m5w, SUSE-SU-2025:02915-1, SUSE-SU-2025:20655-1, UBUNTU-CVE-2025-48060

## What is CVE-2025-48060?

CVE-2025-48060 is a high-severity memory corruption vulnerability in jqlang jq, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

jq is a command-line JSON processor. In versions up to and including 1.7.1, a heap-buffer-overflow is present in function `jv_string_vfmt` in the jq_fuzz_execute harness from oss-fuzz. This crash happens on file jv.c, line 1456 `void* p = malloc(sz);`. As of time of publication, no patched versions are available.

Weakness: CWE-787 (Out-of-bounds Write), CWE-121 (Stack-based Buffer Overflow)

## Which versions are affected by CVE-2025-48060?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jq` | SUSE:Linux Enterprise Micro 5.1 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Enterprise Module for Basesystem 15 SP6 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.6-150000.3.9.1 |
| `jq` | SUSE:Linux Micro 6.0 | All versions | 1.6-5.1 |
| `jq` | openSUSE:Leap 15.6 | All versions | 1.6-150000.3.9.1 |

Products: Jqlang Jq.

## How do I fix CVE-2025-48060?

No fix published yet.

## Is CVE-2025-48060 being exploited?

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

Public exploit code:

- Backported the upstream fix for CVE-2025-48060 (heap buffer overflow in jv_string_empty) to jq 1.6. (github_poc): https://github.com/leorivass/jq-els-backport-cve-2025-48060

## 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-2024-53427](https://insights.sbomify.com/CVE-2024-53427/): Memory corruption in jq (high 8.1)
- [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-2025-48060 and fix it if it is affected.

What it is: CVE-2025-48060 is a high-severity memory corruption vulnerability in jqlang jq, published on 21 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-48060 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-2025-48060/ (Markdown: https://insights.sbomify.com/CVE-2025-48060/index.md)
```

## Sources

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

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