{"answers":{"affected":"It affects 14 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39979 exists.","fix":"Apply the vendor's patch.","what":"CVE-2026-39979 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39979 and fix it if it is affected.\n\nWhat it is: CVE-2026-39979 is a medium-severity vulnerability in Redhat Enterprise Linux, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39979 exists.\n\nAffected product: Redhat Enterprise Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-39979/ (Markdown: https://insights.sbomify.com/CVE-2026-39979/index.md)","id":"CVE-2026-39979","markdown":"https://insights.sbomify.com/CVE-2026-39979/index.md","name":"CVE-2026-39979","record":{"aliases":["ALPINE-CVE-2026-39979","AZL-82931","BELL-CVE-2026-39979","DEBIAN-CVE-2026-39979","ECHO-8163-2cab-0c0f","GHSA-2hhh-px8h-355p"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"jq JSON processor","requires_auth":"none","summary":"An out-of-bounds read in jq's error handling allows attackers to disclose memory or crash the process via malformed JSON input.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jq","vendor":"jqlang"},{"product":"ai_inference_server","vendor":"redhat"},{"product":"ansible_automation_platform","vendor":"redhat"},{"product":"ceph_storage","vendor":"redhat"},{"product":"codeready_linux_builder","vendor":"redhat"},{"product":"codeready_linux_builder_eus","vendor":"redhat"},{"product":"enterprise_linux","vendor":"redhat"},{"product":"enterprise_linux_aus","vendor":"redhat"},{"product":"enterprise_linux_eus","vendor":"redhat"},{"product":"enterprise_linux_tus","vendor":"redhat"},{"product":"enterprise_linux_update_services_for_sap_solutions","vendor":"redhat"},{"product":"hardened_images","vendor":"redhat"},{"product":"openshift_ai","vendor":"redhat"},{"product":"openshift_container_platform","vendor":"redhat"}],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers","id":"CVE-2026-39979","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:enterprise_linux","products":["redhat:enterprise_linux","redhat:enterprise_linux_aus","redhat:enterprise_linux_eus","redhat:hardened_images","redhat:openshift_container_platform"],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"OpenCTI affected by RCE via notifier template","id":"CVE-2026-39980"},"packages":[],"prev":{"headline":"flatpak-builder has a path traversal leading to arbitrary file read on host when installing licence files","id":"CVE-2026-39977"},"products":["jq"],"published":"2026-04-13","related":[{"cvss_score":8.2,"headline":"jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow","id":"CVE-2026-32316","kev_date_added":null,"published":"2026-04-13"},{"cvss_score":8.1,"headline":"Memory corruption in jq","id":"CVE-2024-53427","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":7.7,"headline":"AddressSanitizer: stack-buffer-overflow in jq_fuzz_execute (jv_string_vfmt)","id":"CVE-2025-48060","kev_date_added":null,"published":"2025-05-21"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2023-49355","kev_date_added":null,"published":"2023-12-11"},{"cvss_score":7.1,"headline":"jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow","id":"CVE-2026-49839","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.9,"headline":"jq: potential integer overflow in jvp_string_append","id":"CVE-2026-54679","kev_date_added":null,"published":"2026-06-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-15","vendors":["jqlang"]},"summary":"An out-of-bounds read in jq's error handling allows attackers to disclose memory or crash the process via malformed JSON input.","url":"https://insights.sbomify.com/CVE-2026-39979/"}