CVE-2026-43894

MEDIUMNVD 6.26.2—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.2 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 95% 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 weekElevated
6.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.2Exploit: Elevated riskExposed: 0

A fix is available — apply it.

jq is a command-line JSON processor. In 1.8.1 and earlier, when decNumberFromString is given a number literal of INT_MAX-1 (2147483646) digits, the D2U() macro overflows during signed-int arithmetic. The wrapped negative value bypasses the heap-allocation size check, causes the function to use a 30-byte stack buffer, and then writes ≈715 million 16-bit units (≈1.4 GiB) at an offset 1.43 GiB below the stack frame. The written content is fully attacker-controlled (the parsed decimal digits, packed 3-per-unit).

CVSS v3
6.2
EG Score
6.2(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity62% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

May 11, 2026

Last Modified

May 13, 2026

Advisory Details (1)

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

Wild stack write via signed-integer overflow in decNumber D2U() macro · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-5v7p-2r57-2g4g

Vendor Advisories for CVE-2026-43894(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-5 (6 versions)1.8.1-6—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 54× 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 138 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-43894?
CVE-2026-43894 is a medium vulnerability published on May 11, 2026. jq is a command-line JSON processor. In 1.8.1 and earlier, when decNumberFromString is given a number literal of INT_MAX-1 (2147483646) digits, the D2U() macro overflows during signed-int arithmetic. The wrapped negative value bypasses the heap-allocation size check, causes the function to use a…
When was CVE-2026-43894 disclosed?
CVE-2026-43894 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-43894 actively exploited?
CVE-2026-43894 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 94.8% of all scored CVEs.
What is the CVSS score of CVE-2026-43894?
CVE-2026-43894 has a CVSS v3 base score of 6.2 (NVD).
How do I remediate CVE-2026-43894?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43894, 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-43894

Explore →

Is Your Infrastructure Affected by CVE-2026-43894?

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

Start Free Scan →Browse All CVEs