dbcve.org
Improper Input ValidationWeakness · CWE-20

CVE-2025-10975

MEDIUM · 6.3 CVSS v3.1 Published 2025-09-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 vulnerability was found in GuanxingLu vlarl up to 31abc0baf53ef8f5db666a1c882e1ea64def2997. This vulnerability affects the function experiments.robot.bridge.reasoning_server::run_reasoning_server of the file experiments/robot/bridge/reasoning_server.py of the component ZeroMQ. Performing manipulation of the argument Message results in deserialization. Remote exploitation of the attack is possible. The exploit has been made public and could be used. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided.

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 · moderate confidence

A deserialization vulnerability exists in the ZeroMQ messaging component (reasoning_server.py) of the vlarl project. The run_reasoning_server function processes a Message argument without proper validation, allowing remote attackers to inject malicious serialized objects and potentially execute arbitrary code.

MitigationImplement strict input validation on the Message argument before deserialization; validate message structure, whitelist expected types, or migrate to a safe serialization format. Restrict network access to the reasoning server and monitor for exploitation attempts.

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

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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Locate vlarl project installation
    Search for the vlarl project directory or check common installation paths (e.g., pip show vlarl, find / -name 'vlarl' 2>/dev/null, or check working directories for reasoning_server.py)
    Affected if The vlarl project or reasoning_server.py file is found on the system
  2. Identify reasoning_server.py and the run_reasoning_server function
    Examine reasoning_server.py for the run_reasoning_server function definition and verify it accepts and processes a Message argument without validation (look for pickle.loads, json.loads, or similar deserialization calls)
    Affected if The file contains run_reasoning_server that deserializes Message input without validation
  3. Verify ZeroMQ is used for messaging
    Check imports in reasoning_server.py for zmq, msgpack, or other serialization libraries; confirm the server binds to a ZeroMQ socket
    Affected if The server uses ZeroMQ (zmq library) for message handling
  4. Determine if the reasoning server is network-accessible
    Check if the server binds to an interface other than localhost (0.0.0.0 or external IP) or is exposed via configuration; review startup scripts or service configurations for binding address
    Affected if The server binds to a network interface accessible from outside localhost or is exposed to network traffic
  5. Confirm the server is running or configured to run
    Check running processes for reasoning_server, or review systemd service files, crontabs, or startup scripts that would launch the vulnerable component
    Affected if The reasoning server process is actively running or configured to start automatically

A user is affected if the vlarl reasoning_server.py with an unprotected ZeroMQ message deserialization is present and network-accessible to handle untrusted input.

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

Implement strict input validation on the Message argument before deserialization; validate message structure, whitelist expected types, or migrate to a safe serialization format. Restrict network access to the reasoning server and monitor for exploitation attempts.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-10975 — 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-10975 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