CVE-2026-32316

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.8% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 4 sources updated this weekElevated
7.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 7.5Exploit: No code on recordExposed services: Not assessed

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
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 13, 2026

Last Modified

October 16, 2026

Advisory Details (2)

Auto-updated May 4, 2026
Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)

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
Web page

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntulibjq1 (1.8.1-4ubuntu2) @ resolute2026-10-16ubuntu
ubuntulibjq1 (1.6-2.1ubuntu3.2) @ jammy2026-10-16ubuntu
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

(7 across 7 ecosystems)
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
jq—
  • every version up to 1.8.2-r0: fixed in 1.8.2-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
jq—
  • every version up to 1.8.2-r0: fixed in 1.8.2-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
jq—
  • every version up to 1.8.2-r0: fixed in 1.8.2-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.6-2.1, 1.6-2.1+deb11u1
  • every version up to 1.6-2.1+deb11u2: fixed in 1.6-2.1+deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.6-2.1, 1.6-2.1+deb12u1
  • every version up to 1.6-2.1+deb12u2: fixed in 1.6-2.1+deb12u2
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.7.1-6+deb13u1, 1.7.1-6+deb13u2
  • every version up to 1.7.1-6+deb13u3: fixed in 1.7.1-6+deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.8.0-1, 1.8.1-1, 1.8.1-2, 1.8.1-3, 1.8.1-4
  • every version up to 1.8.1-5: fixed in 1.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 13× in last 7d / 36× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 95 of 237 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 5 repeat rows among the latest 100 are merged into the row they repeat. The 142 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32316?
CVE-2026-32316 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-32316 published?
The CVE record for CVE-2026-32316 was published on April 13, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-32316 actively exploited?
CVE-2026-32316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32316?
CVE-2026-32316 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-32316?
A fix for CVE-2026-32316 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-32316 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs