{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49839 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2026-49839 is a high-severity memory corruption vulnerability in jqlang jq, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49839 and fix it if it is affected.\n\nWhat it is: CVE-2026-49839 is a high-severity memory corruption vulnerability in jqlang jq, published on 25 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-49839 exists.\n\nAffected product: jqlang jq. 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-49839/ (Markdown: https://insights.sbomify.com/CVE-2026-49839/index.md)","id":"CVE-2026-49839","markdown":"https://insights.sbomify.com/CVE-2026-49839/index.md","name":"CVE-2026-49839","record":{"aliases":["ALPINE-CVE-2026-49839","AZL-90267","BELL-CVE-2026-49839","CLSA-2026-1783339505","CLSA-2026-1783340505","DEBIAN-CVE-2026-49839","ECHO-8a1c-e3df-ae5b","GHSA-cfh2-vwfq-qfmm","UBUNTU-CVE-2026-49839"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"JSON processing library","requires_auth":"none","summary":"Attackers can trigger a heap buffer overflow in jq via crafted files, potentially leading to code execution or crashes.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jq","vendor":"jqlang"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"}],"description":"jq is a command-line JSON processor. Prior to 1.8.2,` jq --rawfile` can turn a handled oversized-string error into invalid-state reuse and a real heap out-of-bounds write in assertion-disabled builds. When jv_load_file(raw=1) reads an attacker-controlled file, it repeatedly appends file chunks to the same jv string accumulator. Once jv_string_append_buf() returns jv_invalid_with_msg(\"String too long\"), the raw-file loop does not stop. If the file contains at least one more byte, the next loop iteration appends a new chunk to an object that is already invalid. With assertions enabled this aborts in jvp_string_ptr(). With assertions disabled, the invalid object is interpreted as a string object and ASan reports heap-buffer-overflow. This vulnerability is fixed in 1.8.2.","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 --rawfile invalid-state reuse after String too long causes heap-buffer-overflow","id":"CVE-2026-49839","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"FreeSWITCH: Pre-authentication heap buffer overflow in libesl `Content-Length` parsing","id":"CVE-2026-49840"},"packages":[],"prev":{"headline":"GoBGP confederation validation panics on empty AS_PATH attribute","id":"CVE-2026-49838"},"products":["jq"],"published":"2026-06-25","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":6.9,"headline":"jq: potential integer overflow in jvp_string_append","id":"CVE-2026-54679","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.9,"headline":"jq: Out-of-Bounds Read in jv_parse_sized() Error Formatting for Non-NUL-Terminated Counted Buffers","id":"CVE-2026-39979","kev_date_added":null,"published":"2026-04-13"}],"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-25","vendors":["jqlang"]},"summary":"Attackers can trigger a heap buffer overflow in jq via crafted files, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-49839/"}