Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-49839: jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow

Noroxi assessment

Priority: Monitor (action score 28/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.16% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
  • Fixed version: jqlang jq 1.8.2; azl3 jq 1.7.1-6 on Azure Linux 3.0 1.7.1-7; azl3 jq 1.7.1-8 on Azure Linux 3.0 1.7.1-7.

Low priority for now. Upgrade to jqlang jq 1.8.2; azl3 jq 1.7.1-6 on Azure Linux 3.0 1.7.1-7; azl3 jq 1.7.1-8 on Azure Linux 3.0 1.7.1-7 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

HighCVSS 7.1 · v3.1—No exploit Fix available
Published
Jun 25, 2026
Updated
Oct 25, 2026
EPSS
0.1% · 5th percentile

Report tools

JSON

Action score

28

Monitor

Low priority for now.

CVSS
28 / 40 · 7.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
proof of concept
Automatable
no
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
7.1
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-49839

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for jqlang records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
jqlangjq

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • jqlang jqbefore 1.8.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • jqlang jq

    • < 1.8.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Alpine:v3.22jqbefore 1.8.2-r01.8.2-r0
Debian:12jqbefore 1.6-2.1+deb12u21.6-2.1+deb12u2
Debian:13jqbefore 1.7.1-6+deb13u31.7.1-6+deb13u3
Debian:14jqbefore 1.8.1-81.8.1-8
openSUSE:Leap 16.0jqbefore 1.7.1-160000.4.11.7.1-160000.4.1
openSUSE:Tumbleweedjqbefore 1.8.2-1.11.8.2-1.1
Red Hat:hummingbird:1jqbefore 0:1.8.2-0.1.hum10:1.8.2-0.1.hum1
Red Hat:hummingbird:1jq-develbefore 0:1.8.2-0.1.hum10:1.8.2-0.1.hum1
SUSE:Linux Enterprise Micro 5.3jqbefore 1.7.1-150000.3.25.11.7.1-150000.3.25.1
SUSE:Linux Micro 6.0jqbefore 1.7.1-1.11.7.1-1.1
SUSE:Linux Micro 6.1jqbefore 1.7.1-slfo.1.1_4.11.7.1-slfo.1.1_4.1
SUSE:Linux Micro 6.2jqbefore 1.7.1-160000.4.11.7.1-160000.4.1

Same product

jqlang: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-53427decNumberCopy in decNumber.c in jq through 1.7.1 does not properly consider that NaN is interpreted as numeric, which has a resultant stack-
    32Monitor
  • CVE-2026-40164jq: Algorithmic complexity DoS via hardcoded MurmurHash3 seed
    30Monitor
  • CVE-2026-32316jq: Integer overflow in jvp_string_append() allows Heap-based Buffer Overflow
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2026-44777May 11, 2026 · jq: stack overflow in module loading on mutual `include`
    21Monitor
  • ← EarlierCVE-2026-47770Jun 25, 2026 · jq: stack overflow in deep structural equality
    27Monitor
  • Later →CVE-2026-54679Jun 25, 2026 · jq: potential integer overflow in jvp_string_append
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
jqlang jq1.8.2 · descriptionVendor (CNA)
azl3 jq 1.7.1-6 on Azure Linux 3.01.7.1-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
azl3 jq 1.7.1-8 on Azure Linux 3.01.7.1-7 · CBL-Mariner ReleasesMicrosoft (MSRC)
alpine:jq1.8.2-r0 · Alpine:v3.22Package registry (OSV)
debian:jq1.6-2.1+deb12u2 · Debian:12Package registry (OSV)
opensuse:jq1.8.2-1.1 · openSUSE:TumbleweedPackage registry (OSV)
red hat:jq0:1.8.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:jq-devel0:1.8.2-0.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:jq1.7.1-160000.4.1 · SUSE:Linux Micro 6.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
None
Integrity impact
High
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:H

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

All records