CVE-2026-49839: jq is a command-line JSON processor

Q: How do I fix CVE-2026-49839?

jq: upgrade to 1.8.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-49839 being exploited?

CVE-2026-49839 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-49839 affect?

CVE-2026-49839 affects jq. Severity is high (CVSS 7.1). 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 attac

Q: How urgent is CVE-2026-49839?

Priority 31/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2026-49839 is a high-severity flaw (CVSS 7.1) affecting jq. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Local
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	0.2% (top 94%)
CISA exploited list	No
Weakness	CWE-787
Published	2026-06-25
Last modified	2026-10-25

Publisher (CNA): GitHub, Inc. · Vendor: jqlang

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-06-25 18:16 UTCPublished CVE record published
2026-10-25 22:10 UTCUpdated Record last modified

jqlang jq UPGRADE

Affected: < 1.8.2

Fixed in: 1.8.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jq || rpm -q jq || jq --version

2. UPGRADE to 1.8.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jq

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jq

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-49839?

jq: upgrade to 1.8.2. Exact commands for each OS are on this page.

Is CVE-2026-49839 being exploited?

CVE-2026-49839 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-49839 affect?

CVE-2026-49839 affects jq. Severity is high (CVSS 7.1). 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 attac

How urgent is CVE-2026-49839?

Priority 31/100. High severity; Public exploit reference

Related CVEs

CVE-2026-47770 MEDIUM 5.5 UPGRADE jq is a command-line JSON processor
CVE-2026-54679 MEDIUM 5.5 UPGRADE jq is a command-line JSON processor

References

← Back to latest CVEs