Skip to main content
Menu
CVEs

targets local code execution via custom storage metadata

Only affects targets 1.12.0 and earlier (plus the development main branch through 0d4c9ba147) when the data store uses a custom tar_format() or a CAS repository. Fixed in 1.12.1.

CVE-2026-133707EUVD-2026-131549Published , updated

8.5HighCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 1.12.1
Who is exposed
Specific setups only

Summary

The targets R package, before the fixed release, lets an attacker run arbitrary R code through a crafted data store whose metadata plants custom format or repository functions. The attacker must reach the victim locally, and code runs when the victim calls functions such as tar_read(), tar_load() or tar_workspace() on that data store.

Written by a model

Original description

The targets R package before 1.12.1 contains a code execution vulnerability that allows attackers to run arbitrary R code by planting format functions in the data store metadata file. Attackers can supply a crafted _targets data store whose custom format or CAS repository functions are passed to eval(parse()), executing code when victims call tar_read(), tar_load() or tar_workspace().

Who should check

Teams running the R package targets before 1.12.1 that read pipeline data stores from others, shared, cloud, or CI storage, using custom tar_format() or tar_repository_cas() storage.

“Affecting targets >= 0, < 1.12.1”

vulncheck.com

What to do

  1. Check whether your setup matches what the bug needs.

    The data store uses a custom storage format created with tar_format(). The data store uses a CAS repository (tar_repository_cas) whose functions are evaluated from the store. The affected targets versions are 1.12.0 and earlier, plus the development main branch through 0d4c9ba147.
  2. Upgrade to a fixed version: 1.12.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133707 (targets R package before 1.12.1 Code Execution via Custom Storage Metadata), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133707 (entry last updated 2026-11-20):
Affected:
- ropensci targets: fixed in 1.12.1
Fixed versions: 1.12.1.
Conditions (all must be true for the bug to be hit):
- The data store uses a custom storage format created with tar_format(). (source: https://github.com/ropensci/targets/issues/1602)
- The data store uses a CAS repository (tar_repository_cas) whose functions are evaluated from the store. (source: https://github.com/ropensci/targets/issues/1602)
- The affected targets versions are 1.12.0 and earlier, plus the development main branch through 0d4c9ba147. (source: https://github.com/ropensci/targets/issues/1602)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-133707 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133707 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ropensci/targets/commit/a9681eb237500c7e9a0814cfde31bd05c53d934f
- https://github.com/ropensci/targets/issues/1602
- https://github.com/ropensci/targets/blob/1.12.0/R/class_store_format_custom.R
- https://github.com/ropensci/targets/blob/1.12.0/R/class_store_repository_cas.R
- https://github.com/ropensci/targets/releases/tag/1.12.1
- https://www.vulncheck.com/advisories/targets-r-package-before-1.12.1-code-execution-via-custom-storage-metadata
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133707
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133707"}.

Affected versions

cve.now Index

30Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.5/10CVSS 8.5, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 40 if CISA's SSVC rates it automatable

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated

Evidence 8

Questions about CVE-2026-133707

Is CVE-2026-133707 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. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Some targets pipelines save custom storage read and write functions as R source in the data store, and the code evaluates them when the store is read. A crafted store can therefore run arbitrary R code with the reader's own privileges before any value is returned.

Source: github.com, vulncheck.com

Which versions are affected by CVE-2026-133707?

targets: before 1.12.1.

Source: cve.now feed data

Am I affected, and how do I check?

Versions 1.12.0 and earlier are affected, along with the development main branch through commit 0d4c9ba147. The setup that matters is a data store that uses a custom storage format created with tar_format() or a CAS repository (tar_repository_cas); check the installed version with packageVersion("targets") and whether the pipeline calls tar_format() or tar_repository_cas().

Source: github.com, vulncheck.com

How do I fix CVE-2026-133707?

Upgrade the targets R package to version 1.12.1 or later. The advisory names no patch identifiers beyond that version.

Source: github.com, vulncheck.com

No corrections so far. Something wrong on this page? Report an error.