CVE-2026-32316

HIGHNVD 8.28.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.2 under NVD CVSS v3. EPSS exploit probability: 0.5%, top 60% 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
Elevated
8.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.2Exploit: Elevated riskExposed: 0

A fix is available — apply it.

jq is a command-line JSON processor. An integer overflow vulnerability exists through version 1.8.1 within the jvp_string_append() and jvp_string_copy_replace_bad functions, where concatenating strings with a combined length exceeding 2^31 bytes causes a 32-bit unsigned integer overflow in the buffer allocation size calculation, resulting in a drastically undersized heap buffer. Subsequent memory copy operations then write the full string data into this undersized buffer, causing a heap buffer overflow classified as CWE-190 (Integer Overflow) leading to CWE-122 (Heap-based Buffer Overflow). Any system evaluating untrusted jq queries is affected, as an attacker can crash the process or potentially achieve further exploitation through heap corruption by crafting queries that produce extremely large strings. The root cause is the absence of string size bounds checking, unlike arrays and objects which already have size limits. The issue has been addressed in commit e47e56d226519635768e6aab2f38f0ab037c09e5.

CVSS v3
8.2
EG Score
8.2(medium)
EG Risk
68(Attend)
EG Risk 68/100SSVC: Attend

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
Severity82% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
1%
EPSS %ILE
48%
KEV
Not listed

Published

April 13, 2026

Last Modified

April 22, 2026

Advisory Details (2)

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

Integer overflow in jvp_string_append and jvp_string_copy_replace_bad allows heap buffer overflow · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-q3h9-m34w-h76f
generic

Fix heap buffer overflow in `jvp_string_append` and `jvp_string_copy_… · jqlang/jq@e47e56d · GitHub

https://github.com/jqlang/jq/commit/e47e56d226519635768e6aab2f38f0ab037c09e5

Vendor Advisories for CVE-2026-32316(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibjq1 (1.8.1-4ubuntu2) @ resolute2026-06-14ubuntu
ubuntujq (1.5+dfsg-1ubuntu0.1+esm4) @ xenial2026-06-14ubuntu
redhatjq-main-1.8.1-3.hum12026-04-16redhat

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+deb11u11.6-2.1+deb11u2—
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-1, 1.8.1-2, 1.8.1-3, 1.8.1-41.8.1-5—

Weakness Classification(2)

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

Additional Vendor Advisories

(2)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-32316?
CVE-2026-32316 is a high vulnerability published on April 13, 2026. jq is a command-line JSON processor. An integer overflow vulnerability exists through version 1.8.1 within the jvpstringappend() and jvpstringcopyreplacebad functions, where concatenating strings with a combined length exceeding 2^31 bytes causes a 32-bit unsigned integer overflow in the buffer…
When was CVE-2026-32316 disclosed?
CVE-2026-32316 was first published in the National Vulnerability Database on April 13, 2026, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32316 actively exploited?
CVE-2026-32316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 52.0% of all scored CVEs.
What is the CVSS score of CVE-2026-32316?
CVE-2026-32316 has a CVSS v3 base score of 8.2 (NVD).
How do I remediate CVE-2026-32316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32316, 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-32316

Explore →

Is Your Infrastructure Affected by CVE-2026-32316?

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

Start Free Scan →Browse All CVEs