CVE-2026-25873: OmniGen2-RL Reward Server Unsafe Deserialization RCE
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.
Security readout for executives and security teams
Plain-English summary
OmniGen2-RL’s reward server can treat attacker-supplied internet data as trusted program objects. If the service is reachable, an unauthenticated attacker could run commands on its host, potentially stealing data, altering workloads, or disrupting availability.
Executive priority
Act immediately on internet-accessible deployments and rapidly assess internal deployments. Network isolation is the clearest immediate risk reduction. Because the supplied evidence does not establish a fixed release, require technical owners to verify remediation against vendor guidance rather than assuming an upgrade is safe.
Technical view
The reward server deserializes HTTP POST request bodies using Python pickle without authentication. Because pickle can invoke executable behavior during deserialization, crafted input can produce remote code execution. CVSS 3.1 is 9.8, reflecting network access, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Highest risk applies where OmniGen2-RL reward servers are reachable from untrusted networks. Internal-only services remain exposed to compromised hosts or malicious insiders. The bundle identifies version 0 but gives an unknown default status, so affected-version boundaries and patched-release availability are not established.
Exploitation context
A public technical description and exploit-oriented reference exist, increasing reproducibility risk. However, the bundle says this CVE is not in KEV and provides no evidence of active exploitation in the wild. Publicly exposed instances should still be treated as urgent.
Researcher notes
CWE-502 maps directly to unsafe deserialization. Referenced code locations cover the reward server and proxy, while pull request 139 may document remediation. The supplied bundle does not confirm merge status, release packaging, precise vulnerable commit ranges, default exposure, or observed attacks; validate those points before declaring systems patched.
Mitigation direction
Remove the reward server from public network access immediately.
Restrict access to explicitly authorized training hosts using network controls.
Review pull request 139 and vendor guidance for confirmed remediation status.
Replace affected deployments only with a vendor-confirmed fixed revision or release.
Rotate host credentials and secrets if suspicious access or compromise is identified.
Validation and detection
Inventory OmniGen2-RL deployments and identify running reward server components.
Confirm whether each reward server accepts connections from untrusted networks.
Compare deployed source or revision against pull request 139 and vendor guidance.
Review HTTP, process, and endpoint logs for anomalous reward-server requests or child processes.
After remediation, verify untrusted clients cannot reach or invoke the service.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-502: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-502 · source CWE mapping
Deserialization of Untrusted Data
Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.