CVE Tools
Track your stack

CVE-2026-39979

jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers

No known exploitation. EPSS puts it in the 48th percentile. Fixed versions are out.

CVSS 3.16.5MediumEPSS percentile48th0.6% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix5 products3 fixed builds listed below
Check it yourself

OpenVAS · 37 checks

e.g. OID 1.3.6.1.4.1.25623.1.0.157531

Run the check

Published Updated Sources: CVE.org, NVD, BDU

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Jqlang JqAffected: < 2f09060afab23fe9390cce7cb860b10416e1bf5fUpgrade to: not statedStated by: CVE record
  • Redhat Ai Inference ServerAffected: ≥ 3.2.0, < 3.2.2Upgrade to: 3.2.2Stated by: NVD
  • Redhat Openshift AiAffected: ≥ 3.4, < 3.4.3Upgrade to: 3.4.3Stated by: NVD
  • Redhat Openshift Container PlatformAffected: ≥ 4.12, < 4.12.92Upgrade to: 4.12.92Stated by: NVD
  • Stephen Dolan jqAffected: до 1.8.1 включительноUpgrade to: not statedStated by: BDU

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

jq is a command-line JSON processor. In commits before 2f09060afab23fe9390cce7cb860b10416e1bf5f, the jv_parse_sized() API in libjq accepts a counted buffer with an explicit length parameter, but its error-handling path formats the input buffer using %s in jv_string_fmt(), which reads until a NUL terminator is found rather than respecting the caller-supplied length. This means that when malformed JSON is passed in a non-NUL-terminated buffer, the error construction logic performs an out-of-bounds read past the end of the buffer. The vulnerability is reachable by any libjq consumer calling jv_parse_sized() with untrusted input, and depending on memory layout, can result in memory disclosure or process termination. The issue has been patched in commit 2f09060afab23fe9390cce7cb860b10416e1bf5f.

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS48th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.6% chance of exploitation activity in the next 30 days, which ranks it in the 48th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

14 events over 196 days, from the signal feeds we watch.

  1. Patch availablepatch available, record updated, record updated
  2. Patch availablerecord updated
  3. Patch availablerecord updated
  4. Patch availablerecord updated
  5. OpenVAS check added
  6. Publishedweakness classified, att&ck mapped

Affected products

And 5 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L

Scored 6.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity NoneNo integrity impact
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 30 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Ai Inference Server, not every advisory.