CVE-2026-43895: jq is a command-line JSON processor

Q: How do I fix CVE-2026-43895?

jq: upgrade to newer than 1.8.1. Exact commands for each OS are on this page.

Q: Is CVE-2026-43895 being exploited?

CVE-2026-43895 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-43895 affect?

CVE-2026-43895 affects jq. Severity is medium (CVSS 4.4). 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

Q: How urgent is CVE-2026-43895?

Priority 22/100. Public exploit reference

Routine

MEDIUM 4.4UPGRADE

CVE-2026-43895 is a medium-severity flaw (CVSS 4.4) affecting jq. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.4 (Medium)
Attack vector	Local
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.2% (top 95%)
CISA exploited list	No
Weakness	CWE-20, CWE-158
Published	2026-05-11
Last modified	2026-10-26

Publisher (CNA): GitHub, Inc. · Vendor: jqlang

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-11 18:16 UTCPublished CVE record published
2026-10-26 18:10 UTCUpdated Record last modified

jqlang jq UPGRADE

Affected: <= 1.8.1

Fixed in: newer than 1.8.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy jq || rpm -q jq || jq --version

2. UPGRADE to newer than 1.8.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade jq

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade jq

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-43895?

jq: upgrade to newer than 1.8.1. Exact commands for each OS are on this page.

Is CVE-2026-43895 being exploited?

CVE-2026-43895 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-43895 affect?

CVE-2026-43895 affects jq. Severity is medium (CVSS 4.4). 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

How urgent is CVE-2026-43895?

Priority 22/100. Public exploit reference

Related CVEs

CVE-2026-33947 MEDIUM 6.2 UPGRADE jq is a command-line JSON processor
CVE-2026-39956 MEDIUM 6.1 UPGRADE jq is a command-line JSON processor
CVE-2026-39979 MEDIUM 6.5 UPGRADE UPGRADE jq is a command-line JSON processor
CVE-2026-43894 MEDIUM 6.2 UPGRADE jq is a command-line JSON processor
CVE-2026-43896 MEDIUM 6.2 UPGRADE jq is a command-line JSON processor

References

← Back to latest CVEs