VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

jq: vulnerability history, versions and safety

jq is a package in the Debian ecosystem. Vulert records 23 vulnerabilities for it across 21 releases, from May 2016 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
23 vulnerabilities recorded U23
i
18 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
16 in the last 12 months

Most recent disclosure 25 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jq vulnerabilities

Vulert verdict on jq i

Updated on 23 Oct 2026

Careful: 18 of the 23 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 23 vulnerabilities on record across 10 years, 16 in the last year.

What to do: Plan around the 18 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 23 over 10 years · 16 in the last year i
  • Latest disclosure 25 Jun 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 18 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert holds for jq, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

Newest 21 of 21 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2016 3
  • 2025 4
  • 2026 16

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 16 of the 23 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for jq

The 5 most severe of 23 vulnerabilities recorded for this package

Search all 23 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Heap-based Buffer Overflow in jq 9.8 critical 1.5+dfsg-1.1 06 May 2016
Critical Performance Degradation in jq Due to Hash Collision Vulnerability 7.5 high No fix published 14 Apr 2026
Denial of Service Vulnerability in jq Package: Unbounded Recursion Exploit 6.2 medium No fix published 13 Apr 2026
Critical Vulnerability in jq Package: Unchecked String Handling Leading to Potential Exploits 6.1 medium No fix published 13 Apr 2026
Critical Vulnerability in jq Package: Local Access Exploit in JSON Parser N/A unrated No fix published 25 Aug 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About jq

Is jq safe to use?

Vulert records 23 vulnerabilities for jq in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 23 not yet rated. 18 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does jq have?

23 vulnerabilities are recorded for jq in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 23 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new jq vulnerabilities disclosed?

16 vulnerabilities were recorded for jq in the last 12 months, and the oldest entry in this database dates to 06 May 2016. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of jq are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor jq for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the jq version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.