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.1%, top 96% 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.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 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)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
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.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
jq1.6-2.1, 1.6-2.1+deb11u1, 1.6-2.1+deb11u21.6-2.1+deb11u3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
jq1.6-2.1, 1.6-2.1+deb12u11.6-2.1+deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
jq1.7.1-6+deb13u1, 1.7.1-6+deb13u21.7.1-6+deb13u3—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
jq1.8.0-1 ... 1.8.1-7 (8 versions)1.8.1-8—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 100× 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.

Showing the most recent 100 of 170 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-25 01:46 UTCEG score recompute
  3. 2026-08-25 01:46 UTCVendor advisory
  4. 2026-08-24 13:09 UTCEG score recompute
  5. 2026-08-24 13:09 UTCVendor advisory
  6. 2026-08-24 00:03 UTCVendor advisory
  7. 2026-08-23 11:27 UTCEG score recompute
  8. 2026-08-23 11:27 UTCVendor advisory
  9. 2026-08-23 00:19 UTCEPSS rescore
  10. 2026-08-22 22:50 UTCVendor advisory
  11. 2026-08-22 10:13 UTCEG score recompute
  12. 2026-08-22 10:13 UTCVendor advisory
  13. 2026-08-21 23:49 UTCEPSS rescore
  14. 2026-08-21 20:49 UTCVendor advisory
  15. 2026-08-21 08:14 UTCEG score recompute
  16. 2026-08-21 08:14 UTCVendor advisory
  17. 2026-08-20 22:55 UTCEPSS rescore
  18. 2026-08-20 19:38 UTCVendor advisory
  19. 2026-08-20 07:03 UTCEG score recompute
  20. 2026-08-20 07:03 UTCVendor advisory
  21. 2026-08-19 17:04 UTCEPSS rescore
  22. 2026-08-19 14:12 UTCVendor advisory
  23. 2026-08-19 01:22 UTCEG score recompute
  24. 2026-08-19 01:22 UTCVendor advisory
  25. 2026-08-18 13:48 UTCEPSS rescore
Show 75 more
  1. 2026-08-17 13:47 UTCEPSS rescore
  2. 2026-08-17 06:56 UTCVendor advisory
  3. 2026-08-16 18:21 UTCEG score recompute
  4. 2026-08-16 18:21 UTCVendor advisory
  5. 2026-08-16 14:56 UTCEPSS rescore
  6. 2026-08-16 05:03 UTCEG score recompute
  7. 2026-08-16 05:03 UTCVendor advisory
  8. 2026-08-16 02:14 UTCEPSS rescore
  9. 2026-08-15 16:28 UTCVendor advisory
  10. 2026-08-15 03:53 UTCEG score recompute
  11. 2026-08-15 03:53 UTCVendor advisory
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 15:18 UTCVendor advisory
  14. 2026-08-14 02:42 UTCEG score recompute
  15. 2026-08-14 02:42 UTCVendor advisory
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-13 14:07 UTCVendor advisory
  18. 2026-08-13 01:22 UTCEG score recompute
  19. 2026-08-13 01:22 UTCVendor advisory
  20. 2026-08-12 13:51 UTCEPSS rescore
  21. 2026-08-12 12:47 UTCVendor advisory
  22. 2026-08-12 00:10 UTCEG score recompute
  23. 2026-08-12 00:10 UTCVendor advisory
  24. 2026-08-11 11:34 UTCEG score recompute
  25. 2026-08-11 11:34 UTCVendor advisory
  26. 2026-08-11 00:00 UTCEPSS rescore
  27. 2026-08-10 22:59 UTCVendor advisory
  28. 2026-08-10 10:23 UTCVendor advisory
  29. 2026-08-09 21:48 UTCEG score recompute
  30. 2026-08-09 21:48 UTCVendor advisory
  31. 2026-08-09 13:46 UTCEPSS rescore
  32. 2026-08-09 09:13 UTCVendor advisory
  33. 2026-08-08 20:38 UTCVendor advisory
  34. 2026-08-08 08:02 UTCVendor advisory
  35. 2026-08-07 19:27 UTCVendor advisory
  36. 2026-08-07 06:52 UTCVendor advisory
  37. 2026-08-06 18:17 UTCEG score recompute
  38. 2026-08-06 18:17 UTCVendor advisory
  39. 2026-08-06 13:47 UTCEPSS rescore
  40. 2026-08-06 05:42 UTCEG score recompute
  41. 2026-08-06 05:42 UTCVendor advisory
  42. 2026-08-05 19:17 UTCEPSS rescore
  43. 2026-08-05 17:07 UTCVendor advisory
  44. 2026-08-04 22:14 UTCEG score recompute
  45. 2026-08-04 22:14 UTCVendor advisory
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 10:39 UTCEPSS rescore
  48. 2026-08-04 09:03 UTCVendor advisory
  49. 2026-08-03 20:26 UTCEG score recompute
  50. 2026-08-03 20:26 UTCVendor advisory
  51. 2026-08-03 10:36 UTCEPSS rescore
  52. 2026-08-03 07:51 UTCVendor advisory
  53. 2026-08-02 18:27 UTCVendor advisory
  54. 2026-08-02 05:51 UTCEG score recompute
  55. 2026-08-02 05:51 UTCVendor advisory
  56. 2026-08-02 02:27 UTCEPSS rescore
  57. 2026-08-01 17:16 UTCVendor advisory
  58. 2026-08-01 04:40 UTCEG score recompute
  59. 2026-08-01 04:40 UTCVendor advisory
  60. 2026-08-01 04:16 UTCEPSS rescore
  61. 2026-07-31 16:03 UTCVendor advisory
  62. 2026-07-31 03:01 UTCEG score recompute
  63. 2026-07-31 03:01 UTCVendor advisory
  64. 2026-07-30 16:28 UTCEPSS rescore
  65. 2026-07-30 14:02 UTCEG score recompute
  66. 2026-07-30 14:02 UTCVendor advisory
  67. 2026-07-30 01:30 UTCEPSS rescore
  68. 2026-07-30 00:47 UTCVendor advisory
  69. 2026-07-29 09:44 UTCVendor advisory
  70. 2026-07-28 21:09 UTCEG score recompute
  71. 2026-07-28 21:09 UTCVendor advisory
  72. 2026-07-28 15:37 UTCEPSS rescore
  73. 2026-07-28 05:53 UTCVendor advisory
  74. 2026-07-27 17:17 UTCEG score recompute
  75. 2026-07-27 17:17 UTCVendor advisory

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 0% probability of exploitation in the next 30 days, which ranks it in the top 95.7% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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