GluonTS arbitrary file write during archive extraction
Affects GluonTS versions before 0.17.0 when its archive extraction utility handles a crafted tar archive containing symbolic or hard links. Fixed in 0.17.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.17.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. GluonTS version before 0.17.0 (archive extraction utility) Extraction of a crafted tar archive containing symbolic or hard links
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
The GluonTS software, a Python toolkit for time-series modeling, has a path traversal flaw in its archive extraction utility that lets an attacker write arbitrary files outside the intended folder, using the privileges of the extracting process. An attacker must reach the system locally and get a user to extract a crafted tar archive that contains malicious symbolic or hard links, requiring no login but user interaction.
Read the original description
Path traversal in the archive extraction utility in GluonTS before 0.17.0 might allow an actor who supplies a crafted tar archive to write arbitrary files outside the intended extraction directory with the privileges of the extracting process via symbolic or hard links contained in the archive.
To remediate this issue, users should upgrade to version 0.17.0 or later.
cve.now Index
- Exploitation0/40No signal
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.8/10CVSS 7.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
GluonTS version before 0.17.0 (archive extraction utility) Extraction of a crafted tar archive containing symbolic or hard linksUpgrade to a fixed version: 0.17.0.
Workaround: Do not use GluonTS to extract tar archives from untrusted or unverified sources
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- AWS gluonts
fixed in 0.17.0
Evidence 3
- Advisory
- Advisory
- Patch
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-119083
Is CVE-2026-119083 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Extracting a crafted tar archive that contains symbolic or hard links can write arbitrary files outside the intended extraction directory. The writes run with the privileges of the process doing the extraction.Source: github.com
Which versions are affected by CVE-2026-119083?
gluonts: before 0.17.0.Source: cve.now feed data
Am I affected, and how do I check?
GluonTS versions before 0.17.0 are affected when the archive extraction utility is used on tar archives containing symbolic or hard links. To check the installed version, run pip show gluonts and read the Version line.Source: github.com
How do I fix CVE-2026-119083?
Upgrade GluonTS to 0.17.0 or later. Until the upgrade is done, avoid using GluonTS to extract tar archives from untrusted or unverified sources.Source: github.com