{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-41257 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-41257 is a medium-severity vulnerability in jqlang jq, published on 11 May 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-41257 and fix it if it is affected.\n\nWhat it is: CVE-2026-41257 is a medium-severity vulnerability in jqlang jq, published on 11 May 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: There is no known exploitation of CVE-2026-41257 in the wild and no public exploit code.\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-41257/ (Markdown: https://insights.sbomify.com/CVE-2026-41257/index.md)","id":"CVE-2026-41257","markdown":"https://insights.sbomify.com/CVE-2026-41257/index.md","name":"CVE-2026-41257","record":{"aliases":["ALPINE-CVE-2026-41257","AZL-86369","BELL-CVE-2026-41257","DEBIAN-CVE-2026-41257","ECHO-5cb6-067b-5460","GHSA-4jm8-m363-4539","UBUNTU-CVE-2026-41257"],"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":"An integer overflow in jq's VM stack allows attackers to trigger memory corruption via deeply nested JSON, potentially leading to code execution or crashes.","user_interaction":"required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"jq","vendor":"jqlang"}],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"jq is a command-line JSON processor. In 1.8.1 and earlier, the jq bytecode VM's data stack tracks its allocation size in a signed int. When the stack grows beyond ≈1 GiB (via deeply nested generator forks), the doubling arithmetic overflows. The wrapped value is passed to realloc and then used for a memmove with attacker-influenced offsets.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"jq: Signed-int overflow in `stack_reallocate` (jq VM stack)","id":"CVE-2026-41257","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"OpenMRS: Stored Velocity SSTI to RCE via ConceptReferenceRange","id":"CVE-2026-41258"},"packages":[],"prev":{"headline":"jq: Embedded NUL truncates top-level jq programs loaded with -f","id":"CVE-2026-41256"},"products":["jq"],"published":"2026-05-11","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"},{"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-11","vendors":["jqlang"]},"summary":"An integer overflow in jq's VM stack allows attackers to trigger memory corruption via deeply nested JSON, potentially leading to code execution or crashes.","url":"https://insights.sbomify.com/CVE-2026-41257/"}