Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-25873

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
OmniGen2-RL contains an unauthenticated remote code execution vulnerability in the reward server component that allows remote attackers to execute arbitrary commands by sending malicious HTTP POST requests. Attackers can exploit insecure pickle deserialization of request bodies to achieve code execution on the host system running the exposed service.

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

OmniGen2-RL's reward server component has an unauthenticated remote code execution vulnerability. Attackers can send malicious HTTP POST requests containing specially crafted pickle-serialized data that, when deserialized by the server, allows arbitrary command execution on the host system.

MitigationImmediately restrict network access to the reward server and disable it if not required. If the service is needed, implement authentication and replace insecure pickle deserialization with secure formats like JSON, or use a safe unpickler library with allowlist verification.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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. Identify if OmniGen2-RL is installed
    Search for OmniGen2-RL related files, packages, or directories in common installation locations. Use commands like 'pip list | grep -i omni' or 'find / -name "*omnigen*" 2>/dev/null' to locate the software.
    Affected if OmniGen2-RL software is found in the environment
  2. Locate running reward server processes
    Run 'ps aux | grep -i reward' or 'netstat -tlnp | grep -E "(port|8080|5000|8000)"' to find the reward server component actively listening for HTTP connections.
    Affected if A reward server process is running and accepting HTTP connections on a network port
  3. Inspect reward server code for pickle deserialization
    Examine the reward server source code for usage of 'pickle.load()', 'pickle.loads()', or 'cPickile.load()' on incoming request data. Search for patterns like 'pickle.load(request.body)' or similar deserialization of HTTP POST content.
    Affected if The code uses pickle to deserialize request bodies from HTTP POST requests without validation
  4. Check if authentication is disabled on the endpoint
    Review the reward server configuration and code to determine if the HTTP endpoint implements any authentication or authorization checks before processing request data.
    Affected if The reward server accepts requests without requiring authentication (the vulnerability is specifically unauthenticated RCE)
  5. Compare installed version to any known affected versions
    If a version number is discoverable (via 'pip show omnigen2-rl' or examining version files), compare it against the affected version range provided by the CVE.
    Affected if The installed version falls within an affected range specified by the CVE

A user is affected if OmniGen2-RL is installed with the reward server running, the code uses pickle to deserialize unauthenticated HTTP POST request bodies, and the server is network-accessible.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Immediately restrict network access to the reward server and disable it if not required. If the service is needed, implement authentication and replace insecure pickle deserialization with secure formats like JSON, or use a safe unpickler library with allowlist verification.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing10.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,860
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2026-25873 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