JLSEC-2026-184 | Vulnetix

JLSEC-2026-184 PUBLISHED CVSS 5.5 MEDIUM

Record from OSV · Published April 24, 2026

GNU Tar through 1.34 has a one-byte out-of-bounds read that results in use of uninitialized memory for a conditional jump. Exploitation to change the flow of control has not been demonstrated. The issue occurs in `from_header` in list.c via a V7 archive in which mtime has approximately 11 whitespace characters.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

Package	Ecosystem	Fixed in
Tar_jll	pkg.julialang.org	1.35.0+0
Tar_jll	juliahub.com	1.35.0+0

Risk scores

CVSS 3.1

5.5

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

Affected products

Vendor	Product	Versions
Julia	Tar_jll	0
Julia	Tar_jll	0

Timeline

Apr 24, 2026 CVE Published
Jul 25, 2026 CVE Updated

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln JLSEC-2026-184
vulnetix vdb fixes JLSEC-2026-184

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/JLSEC-2026-184/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →