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.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. 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)
EG Risk
25(Track)
EG Risk 25/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%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
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.

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+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-5 (6 versions)1.8.1-6—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 4× in last 7d / 27× 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 184 total refreshes for this CVE.

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

See which npm, PyPI, Go, and Maven packages are affected by 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