CVE-2026-41257

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
5.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

jq is a command-line JSON processor. In 1.8.1 and earlier, the jq bytecode VM's data stack tracks its allocation size in a signed int. When the stack grows beyond ≈1 GiB (via deeply nested generator forks), the doubling arithmetic overflows. The wrapped value is passed to realloc and then used for a memmove with attacker-influenced offsets.

CVSS v3
5.5
EG Score
5.5(medium)
EPSS
3.8%
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

Signed-int overflow in `stack_reallocate` (jq VM stack) · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-4jm8-m363-4539

Vendor Advisories for CVE-2026-41257(2)

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

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-41257?
CVE-2026-41257 is a medium vulnerability published on May 11, 2026. jq is a command-line JSON processor. In 1.8.1 and earlier, the jq bytecode VM's data stack tracks its allocation size in a signed int. When the stack grows beyond ≈1 GiB (via deeply nested generator forks), the doubling arithmetic overflows. The wrapped value is passed to realloc and then used for…
When was CVE-2026-41257 disclosed?
CVE-2026-41257 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-41257 actively exploited?
CVE-2026-41257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-41257?
CVE-2026-41257 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-41257?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-41257, 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

Explore the affected products and dependency analysis for CVE-2026-41257

Explore →

Is Your Infrastructure Affected by CVE-2026-41257?

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

Start Free Scan →Browse All CVEs