dbcve.org
Robot Operating SystemOperating system · Openrobotics

CVE-2025-3753

HIGH · 7.8 CVSS v3.1 Published 2025-07-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A code execution vulnerability has been identified in the Robot Operating System (ROS) 'rosbag' tool, affecting ROS distributions Noetic Ninjemys and earlier. The vulnerability arises from the use of the eval() function to process unsanitized, user-supplied input in the 'rosbag filter' command. This flaw enables attackers to craft and execute arbitrary Python code.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A code execution vulnerability exists in the ROS 'rosbag' tool where the eval() function processes unsanitized user-supplied input in the 'rosbag filter' command. Attackers can craft malicious input that gets evaluated by eval(), allowing arbitrary Python code execution. The vulnerability affects ROS Noetic Ninjemys and earlier distributions.

MitigationReplace eval() with safer alternatives such as restricted expression evaluators (e.g., using Python's AST module with sandboxed evaluation), or implement strict input validation and sanitization before processing any user-provided filter expressions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Robot Operating SystemOperating system
Affected:= indigo_igloo= kinetic_kame= melodic_morenia= noetic_ninjemys

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if rosbag is installed
    Run 'rospack find rosbag' or 'python3 -c "import rosbag; print(rosbag.__file__)"' to locate the rosbag package installation
    Affected if rosbag is not found on the system, the user is not affected by this vulnerability
  2. Identify the rosbag version
    Run 'rosbag --version' or check the package metadata with 'rosversion -a' and look for the ROS distribution name (indigo, kinetic, melodic, or noetic)
    Affected if The installed version corresponds to ROS distributions indigo_igloo, kinetic_kame, melodic_morenia, or noetic_ninjemys, indicating a potentially vulnerable release
  3. Verify the rosbag filter command exists
    Run 'rosbag filter --help' to confirm the filter subcommand is available
    Affected if The filter command is not present, the specific vulnerability attack surface does not exist
  4. Inspect the rosbag filter source code
    Locate the rosbag filter implementation (typically in /opt/ros/<distro>/lib/python3*/rosbag/ or the source directory) and search for eval() usage within the filter logic
    Affected if The source code contains eval() processing user-supplied filter expressions without sanitization, confirming the vulnerability is present
  5. Determine if filter expressions accept external input
    Review how the rosbag filter command accepts and processes filter expressions (via command line arguments or configuration files)
    Affected if User-supplied filter expressions can be passed directly to the rosbag filter command, enabling exploitation of the eval() vulnerability

The environment is affected if rosbag is installed with a vulnerable version (indigo through noetic), the filter command is available, and the source code contains unsanitized eval() usage with user-provided filter expressions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace eval() with safer alternatives such as restricted expression evaluators (e.g., using Python's AST module with sandboxed evaluation), or implement strict input validation and sanitization before processing any user-provided filter expressions.

Fix this in Robot Operating System Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3753 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3753 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data