Skip to main content
CVE-2026-133707VulnerabilityPublished

The targets R package before 1.12.1 contains a code execution vulnerability that allows attackers to run arbitrary R

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-133707· High 8.5

Not known to be exploited · CVSS 8.5 High : upgrade to 1.12.1 soon.

Data as of 20 Nov 2026, 16:21 UTC

CVSS 4.0 base score
8.5High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.5
CNA (VulnCheck)CVSS 3.17.8
Patch
Available – fixed in 1.12.1
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade targets to 1.12.1.

Affected software

ProductAffectedFixed in
ropenscitargetsAffected
  • <1.12.1
Fixed in
  • 1.12.1
GitHubtargetspkg:github/targetsOther threatsAffected
  • <1.12.1
Fixed in
  • 1.12.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fixed version 1.12.1 or later is implied but not explicitly stated in the input; however, the description specifies the vulnerability affects versions before 1.12.1. Users should upgrade to version 1.12.1 or later to remediate this vulnerability.

Description

The targets R package versions before 1.12.1 contain a code execution vulnerability. This flaw allows attackers to execute arbitrary R code by embedding malicious format functions in the data store metadata file. The vulnerability is triggered when victims use functions such as tar_read(), tar_load(), or tar_workspace() to access the compromised data store.

References

Community reviews

Loading reviews…