# CVE-2025-9403: jqlang jq JSON jq_test.c run_jq_tests assertion

> A local attacker can trigger a reachable assertion failure in the jq JSON parser's test runner, causing a denial of service.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** AZL-66678, AZL-85554, BELL-CVE-2025-9403, DEBIAN-CVE-2025-9403, ECHO-e20f-69f2-003a, GHSA-45r2-rx5v-q5f6, OESA-2026-2780, SUSE-SU-2026:0931-1, UBUNTU-CVE-2025-9403, openSUSE-SU-2026:11789-1

## What is CVE-2025-9403?

CVE-2025-9403 is a medium-severity denial of service vulnerability in jqlang jq, published on 25 Aug 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability was determined in jqlang jq up to 1.6. Impacted is the function run_jq_tests of the file jq_test.c of the component JSON Parser. Executing manipulation can lead to reachable assertion. The attack requires local access. The exploit has been publicly disclosed and may be utilized. Other versions might be affected as well.

Weakness: CWE-617 (Reachable Assertion)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `jq` | SUSE:Linux Enterprise Micro 5.2 | All versions | 1.6-150000.3.12.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.3 | All versions | 1.6-150000.3.12.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.4 | All versions | 1.6-150000.3.12.1 |
| `jq` | SUSE:Linux Enterprise Micro 5.5 | All versions | 1.6-150000.3.12.1 |
| `jq` | SUSE:Linux Enterprise Module for Basesystem 15 SP7 | All versions | 1.6-150000.3.12.1 |
| `jq` | openSUSE:Leap 15.6 | All versions | 1.6-150000.3.12.1 |
| `jq` | openSUSE:Tumbleweed | All versions | 1.8.2-2.1 |

Products: Jqlang Jq.

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

Apply the vendor's patch.

## Is CVE-2025-9403 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9403 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-2024-53427](https://insights.sbomify.com/CVE-2024-53427/): Memory corruption in jq (high 8.1)
- [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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9403 and fix it if it is affected.

What it is: CVE-2025-9403 is a medium-severity denial of service vulnerability in jqlang jq, published on 25 Aug 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-2025-9403 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-9403/ (Markdown: https://insights.sbomify.com/CVE-2025-9403/index.md)
```

## Sources

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

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