jq is a command-line JSON processor
Why It Matters
Analysis dossierWhy It Matters
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.
High
Unknown
Unknown
Risk basis: SOC ecosystem technology relevance; HIGH severity; Source severity; no confirmed exploitation signal
Affected Products & Remediation
14 source-backed products- jqlang jq · < 1.8.2 · NVD CPE · Source
- redhat ai inference server · >= 3.2.0 < 3.2.2; >= 3.3.0 < 3.3.5 · NVD CPE · Source
- redhat ansible automation platform · 2.0 · NVD CPE · Source
- redhat ceph storage · 4.0 · NVD CPE · Source
- redhat codeready linux builder · 8.0; 9.0; 10.0; eus 9.4; eus 9.6; eus 10.0 · NVD CPE · Source
- redhat codeready linux builder eus · 9.4; 9.6; 10.0 · NVD CPE · Source
- redhat hardened images · version range not provided by source · NVD CPE · Source
- redhat openshift ai · >= 3.4 < 3.4.3 · NVD CPE · Source
- redhat openshift container platform · >= 4.12 < 4.12.92; >= 4.13 < 4.13.68; >= 4.14 < 4.14.68; >= 4.15 < 4.15.65; >= 4.16 < 4.16.64; >= 4.17 < 4.17.55; >= 4.18 < 4.18.44; >= 4.19 < 4.19.33 · NVD CPE · Source
- redhat enterprise linux · 8.0; 9.0; 10.0; aus 8.4; aus 8.6; eus 8.4; eus 9.4; eus 9.6; eus 10.0; tus 8.6; tus 8.8; update services for sap solutions 8.6; update services for sap solutions 8.8; update services for sap solutions 9.0; update services for sap solutions 9.2 · NVD CPE · Source
- redhat enterprise linux aus · 8.4; 8.6 · NVD CPE · Source
- redhat enterprise linux eus · 8.4; 9.4; 9.6; 10.0 · NVD CPE · Source
- redhat enterprise linux tus · 8.6; 8.8 · NVD CPE · Source
- redhat enterprise linux update services for sap solutions · 8.6; 8.8; 9.0; 9.2 · NVD CPE · Source
Vendor or catalog guidance (source)
Not provided by source
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Unknown
- Exploited (source statement)
- Unknown
- Publicly disclosed (source)
- Unknown
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched network-unauthenticated (CVSS AV:N, CVSS PR:N, CVSS UI:N)
Exposure
- Identify devices reporting this CVE and note which expose the affected service to untrusted networks.Telemetry: DeviceTvmSoftwareVulnerabilities · A network-reachable, no-privilege vector makes internet-facing instances the first exposure question. · Rule network-unauthenticated
Exploitation evidence
- Review inbound connections to the affected service from unexpected sources since the advisory date.Telemetry: DeviceNetworkEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule network-unauthenticated
Response
- Confirm the source-stated update is installed and the CVE is no longer reported.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies remediation. · Rule network-unauthenticated
CISA KEV Record
CISA KEV status was not determined for this record.
Change History & Source Data
— No recorded material change
- CNA / source
- security-advisories@github.com
- Record status · verification
- UPDATED · NVD API
- CPE
- cpe:2.3:a:jqlang:jq:*:*:*:*:*:*:*:*, cpe:2.3:a:redhat:ai_inference_server:*:*:*:*:*:*:*:*, cpe:2.3:a:redhat:ansible_automation_platform:2.0:*:*:*:*:*:*:*, cpe:2.3:a:redhat:ceph_storage:4.0:*:*:*:*:*:*:*, cpe:2.3:a:redhat:codeready_linux_builder:8.0:*:*:*:*:*:*:*, cpe:2.3:a:redhat:codeready_linux_builder:9.0:*:*:*:*:*:*:*, cpe:2.3:a:redhat:codeready_linux_builder:10.0:*:*:*:*:*:*:*, cpe:2.3:a:redhat:codeready_linux_builder_eus:9.4:*:*:*:*:*:*:*, cpe:2.3:a:redhat:codeready_linux_builder_eus:9.6:*:*:*:*:*:*:*, cpe:2.3:a:redhat:codeready_linux_builder_eus:10.0:*:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2026-39979"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel descLooking up related community queries…