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

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.4(medium)
EPSS
5.3%
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.
github Patch Available🟡 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 / 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.

Weakness Classification(2)

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

Data Freshness Timeline

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

Related CVEs(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 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-43895 actively exploited?
CVE-2026-43895 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-43895, 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-43895

Explore →

Is Your Infrastructure Affected by CVE-2026-43895?

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

Start Free Scan →Browse All CVEs