CVE-2026-49839

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 94% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
6.1%
KEV
Not listed

Published

June 25, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

jq --rawfile invalid-state reuse after String too long causes heap-buffer-overflow · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-cfh2-vwfq-qfmm

Vendor Advisories for CVE-2026-49839(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjq-main-1.8.2-0.1.hum12026-06-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 31× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-06 23:02 UTCEG score recompute
  2. 2026-07-06 23:02 UTCVendor advisory
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 10:25 UTCEG score recompute
  5. 2026-07-06 10:25 UTCVendor advisory
  6. 2026-07-05 21:48 UTCEG score recompute
  7. 2026-07-05 21:48 UTCVendor advisory
  8. 2026-07-05 09:13 UTCEG score recompute
  9. 2026-07-05 09:13 UTCVendor advisory
  10. 2026-07-05 02:30 UTCEPSS rescore
  11. 2026-07-04 20:27 UTCEG score recompute
  12. 2026-07-04 20:27 UTCVendor advisory
  13. 2026-07-04 07:51 UTCEG score recompute
  14. 2026-07-04 07:51 UTCVendor advisory
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-03 19:15 UTCEG score recompute
  17. 2026-07-03 19:15 UTCVendor advisory
  18. 2026-07-03 06:40 UTCEG score recompute
  19. 2026-07-03 06:40 UTCVendor advisory
  20. 2026-07-02 18:04 UTCEG score recompute
  21. 2026-07-02 18:04 UTCVendor advisory
  22. 2026-07-02 05:27 UTCEG score recompute
  23. 2026-07-02 05:27 UTCVendor advisory
  24. 2026-07-01 16:52 UTCEG score recompute
  25. 2026-07-01 16:52 UTCVendor advisory
Show 23 more
  1. 2026-07-01 15:07 UTCEPSS rescore
  2. 2026-07-01 04:17 UTCEG score recompute
  3. 2026-07-01 04:17 UTCVendor advisory
  4. 2026-06-30 23:22 UTCEPSS rescore
  5. 2026-06-30 15:42 UTCEG score recompute
  6. 2026-06-30 15:42 UTCVendor advisory
  7. 2026-06-30 03:06 UTCEG score recompute
  8. 2026-06-30 03:06 UTCVendor advisory
  9. 2026-06-29 14:31 UTCEG score recompute
  10. 2026-06-29 14:06 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 01:56 UTCEG score recompute
  13. 2026-06-28 14:07 UTCEPSS rescore
  14. 2026-06-28 13:20 UTCEG score recompute
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 00:45 UTCEG score recompute
  18. 2026-06-27 12:10 UTCEG score recompute
  19. 2026-06-27 03:08 UTCEPSS rescore
  20. 2026-06-26 23:32 UTCEG score recompute
  21. 2026-06-26 10:57 UTCEG score recompute
  22. 2026-06-25 19:50 UTCEG score recompute
  23. 2026-06-25 19:49 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-49839?
CVE-2026-49839 is a high vulnerability published on June 25, 2026. 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 jvloadfile(raw=1) reads an attacker-controlled file, it repeatedly appends file chunks to the…
When was CVE-2026-49839 disclosed?
CVE-2026-49839 was first published in the National Vulnerability Database on June 25, 2026, with the most recent update on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49839 actively exploited?
CVE-2026-49839 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49839?
CVE-2026-49839 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-49839?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49839, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-49839

Explore →

Is Your Infrastructure Affected by CVE-2026-49839?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs