Threats Tagged 'cve-2026-49839'
View all threats tagged with 'cve-2026-49839'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-49839'
Click on any threat for detailed analysis and mitigation recommendations
0 Multiple vulnerabilities in jq can cause process crashes due to unbounded or uncontrolled recursion, heap out-of-bounds writes, and buffer overruns on 32-bit systems. These issues include stack exhaustion from recursive object merges and module loading, a heap corruption bug triggered by --rawfile with oversized strings, and an integer overflow leading to buffer overrun. Join the discussion | GCVE Database | 07/13/2026, 10:29:44 UTC Added: 09/17/2026, 01:59:08 UTC |
0 jq is a command-line JSON processor. Prior to 1.8.2, comparing two sufficiently deeply nested arrays with the == operator exhausts the C stack on jq's ordinary command-line surface, resulting in denial of service via stack exhaustion (uncontrolled recursion). The crash occurs in jq's recursive structural comparison code, with the recursion repeating through jvp_array_equal() and jv_equal() in src/jv.c when comparing deeply nested arrays; a nearby sort comparator path through jv_cmp() in src/jv_aux.c overflows the stack at a larger nesting depth from the same missing recursion guard. Anyone running jq comparisons on attacker-controlled deeply nested JSON values, or embedding jq in a context where untrusted data can reach the == comparison path, is affected. This vulnerability is fixed in 1.8.2. Join the discussion | CVE Database V5 | 06/27/2026, 00:00:00 UTC Added: 06/25/2026, 17:31:07 UTC |
0 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. Join the discussion | CVE Database V5 | 06/25/2026, 17:17:46 UTC Added: 06/25/2026, 17:31:07 UTC |
0 This update includes the following RPMs: jq: * jq-1.8.2-0.1.hum1 (aarch64, x86_64) * jq-devel-1.8.2-0.1.hum1 (aarch64, x86_64) * jq-1.8.2-0.1.hum1.src (src) Join the discussion | GCVE Database | 06/25/2026, 15:16:12 UTC Added: 06/30/2026, 23:35:43 UTC |
Showing 1 to 4 of 4 results