CVE-2026-43895

MEDIUMNVD 4.44.4—
EchelonGraph scoreMEDIUM confidence

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

A fix is available — apply it.

jq is a command-line JSON processor. In 1.8.1 and earlier, jq accepts embedded NUL bytes in import paths at the jq-language level, but later resolves those paths through C string operations during module and data-file lookup. This creates a mismatch between the logical import string that policy or audit code may validate and the on-disk path that jq actually opens.

CVSS v3
4.4
EG Score
4.4MEDIUMmedium confidence
EG Risk
36
EG Risk 36/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
Severity44% × 45%
Exploitation40% × 40%
Automatability0% × 15%
EPSS PROB
0.2%
EPSS %ILE
3rd
KEV
Not listed

Published

May 11, 2026

Last Modified

May 13, 2026

Advisory Details (1)

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

Embedded NUL in jq import paths causes local redaction-policy bypass and preserves sensitive fields in published artifacts · Advisory · jqlang/jq · GitHub

https://github.com/jqlang/jq/security/advisories/GHSA-7q7g-mrq3-phxr

Vendor Advisories for CVE-2026-43895(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.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-5 (6 versions)
  • every version up to 1.8.1-6: fixed in 1.8.1-6
—

Weakness Classification(2)

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

Data Freshness Timeline

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

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

Frequently asked(5)

What is CVE-2026-43895?
CVE-2026-43895 is a medium vulnerability published on May 11, 2026. jq is a command-line JSON processor. In 1.8.1 and earlier, jq accepts embedded NUL bytes in import paths at the jq-language level, but later resolves those paths through C string operations during module and data-file lookup. This creates a mismatch between the logical import string that policy or…
When was CVE-2026-43895 disclosed?
CVE-2026-43895 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-43895 actively exploited?
CVE-2026-43895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (3rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-43895?
CVE-2026-43895 has a CVSS v3 base score of 4.4 (NVD).
How do I remediate CVE-2026-43895?
A fix for CVE-2026-43895 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-43895 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-43895

Explore →

Is Your Infrastructure Affected by CVE-2026-43895?

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

Book a Demo →Browse All CVEs