# CVE-2024-27322: Deserialization in R

> Attackers can execute arbitrary code by tricking users into opening malicious RDS files or packages in the R statistical programming language.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Apr 2024
- **Updated:** 13 Feb 2025
- **Also known as:** AZL-42792, AZL-42815, DEBIAN-CVE-2024-27322, GHSA-82x4-8q4x-2qxv, UBUNTU-CVE-2024-27322

## What is CVE-2024-27322?

CVE-2024-27322 is a high-severity unsafe deserialization vulnerability in The R Project R, published on 29 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Deserialization of untrusted data can occur in the R statistical programming language, on any version starting at 1.4.0 up to and not including 4.4.0, enabling a maliciously crafted RDS (R Data Serialization) formatted file or R package to run arbitrary code on an end user’s system when interacted with.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-27322?


## How do I fix CVE-2024-27322?

Upgrade to a fixed version.

## Is CVE-2024-27322 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27322 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-27322 and fix it if it is affected.

What it is: CVE-2024-27322 is a high-severity unsafe deserialization vulnerability in The R Project R, published on 29 Apr 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-27322 exists.

Affected product: The R Project R. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-27322/ (Markdown: https://insights.sbomify.com/CVE-2024-27322/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-27322
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-27322
- OSV: https://osv.dev/vulnerability/CVE-2024-27322

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-27322/
Summaries are generated and may contain mistakes; the official description above is the record.