Improper Null Termination Affecting rhcos package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.14% (34th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL8-RHCOS-16085963
  • published16 Apr 2026
  • disclosed13 Apr 2026

Introduced: 13 Apr 2026

CVE-2026-33948  (opens in a new tab)
CWE-170  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:8 rhcos.

NVD Description

Note: Versions mentioned in the description apply only to the upstream rhcos package and not the rhcos package as distributed by RHEL. See How to fix? for RHEL:8 relevant fixed versions and status.

jq is a command-line JSON processor. Commits before 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b contain a vulnerability where CLI input parsing allows validation bypass via embedded NUL bytes. When reading JSON from files or stdin, jq uses strlen() to determine buffer length instead of the actual byte count from fgets(), causing it to truncate input at the first NUL byte and parse only the preceding prefix. This enables an attacker to craft input with a benign JSON prefix before a NUL byte followed by malicious trailing data, where jq validates only the prefix as valid JSON while silently discarding the suffix. Workflows relying on jq to validate untrusted JSON before forwarding it to downstream consumers are susceptible to parser differential attacks, as those consumers may process the full input including the malicious trailing bytes. This issue has been patched by commit 6374ae0bcdfe33a18eb0ae6db28493b1f34a0a5b.

CVSS Base Scores

version 3.1