CVE-2026-40612

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

jq is a command-line JSON processor. In 1.8.1 and earlier, jv_contains recurses into nested arrays/objects with no depth limit. With a sufficiently nested input structure (built programmatically with reduce, since the JSON parser caps at depth 10000), the C stack is exhausted.

CVSS v3
5.5
EG Score
5.5MEDIUMmedium confidence
EG Risk
41
EG Risk 41/100

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%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

Published

May 11, 2026

Last Modified

May 13, 2026

Advisory Details (1)

Auto-updated Jun 16, 2026
🔬 Proof of concept available. Patch available. Sources: github.
githubMentions a patch (unverified)🟡 PoC Available

Stack overflow via unbounded recursion in jv_contains · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-r7m6-x9c7-h69j

Vendor Advisories for CVE-2026-40612(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 / EcosystemFix (by version range) / 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 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.8.2-1 (22 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
jq1.6-2.1 ... 1.8.2-1 (21 versions)
  • every version on: no fix on record
—
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-5 (6 versions)
  • every version up to 1.8.1-6: fixed in 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 / 24× 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 204 total refreshes for this CVE.

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

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

Frequently asked(5)

What is CVE-2026-40612?
CVE-2026-40612 is a medium vulnerability published on May 11, 2026. jq is a command-line JSON processor. In 1.8.1 and earlier, jv_contains recurses into nested arrays/objects with no depth limit. With a sufficiently nested input structure (built programmatically with reduce, since the JSON parser caps at depth 10000), the C stack is exhausted.
When was CVE-2026-40612 disclosed?
CVE-2026-40612 was first published 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-40612 actively exploited?
CVE-2026-40612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40612?
CVE-2026-40612 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-40612?
A fix for CVE-2026-40612 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40612 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-40612

Explore →

Is Your Infrastructure Affected by CVE-2026-40612?

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

Book a Demo →Browse All CVEs