# CVE-2024-42002: Unsafe use of eval() method in ros2 topic hz tool

> A local attacker can execute arbitrary code via the unsanitized eval() function in the ROS 2 topic hz tool's filter option.

- **Severity:** High 8.6 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2026
- **Updated:** 30 Sep 2026

## What is CVE-2024-42002?

CVE-2024-42002 is a high-severity code injection vulnerability in Open Source Robotics Foundation Robot Operating System 2 (ROS 2), published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A code injection vulnerability has been discovered in the Robot Operating System 2 (ROS 2) 'ros2topic' command-line tool, affecting all ROS 2 distributions from Crystal Clemmys up to and including Lyrical Luth and Rolling Ridley. The vulnerability lies in the 'hz' verb, which reports the publishing rate of a topic and accepts a user-provided Python expression via the --filter option. This input is passed directly to the eval() function without sanitization, allowing a local user to craft and execute arbitrary code.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-94 (Improper Control of Generation of Code)

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


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

No fix has been published for CVE-2024-42002 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-42002 being exploited?

There is no known exploitation of CVE-2024-42002 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-42002 is a high-severity code injection vulnerability in Open Source Robotics Foundation Robot Operating System 2 (ROS 2), published on 28 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-42002 in the wild and no public exploit code.

Affected product: Open Source Robotics Foundation Robot Operating System 2 (ROS 2). 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-42002/ (Markdown: https://insights.sbomify.com/CVE-2024-42002/index.md)
```

## Sources

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

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