CVE-2026-47770

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.5 under NVD CVSS v3. 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, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 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

stack overflow in deep structural equality · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-3pgx-frr7-3jxp

Vendor Advisories for CVE-2026-47770(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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
jq—1.8.2-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
jq—1.8.2-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
jq—1.8.2-r0—
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-6 (7 versions)1.8.1-7—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 39× 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 150 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-47770?
CVE-2026-47770 is a medium vulnerability published on June 25, 2026. 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…
When was CVE-2026-47770 disclosed?
CVE-2026-47770 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-47770 actively exploited?
CVE-2026-47770 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.6% of all scored CVEs.
What is the CVSS score of CVE-2026-47770?
CVE-2026-47770 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-47770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47770, 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-47770

Explore →

Is Your Infrastructure Affected by CVE-2026-47770?

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

Start Free Scan →Browse All CVEs