Goal Reached Thanks to every supporter β€” we hit 100%!

Goal: 1000 CNY Β· Raised: 1000 CNY

100.0%

CVE-2026-25873 β€” AI Deep Analysis Summary

CVSS 9.8 Β· Critical

Q1What is this vulnerability? (Essence + Consequences)

🚨 **Essence**: OmniGen2-RL has an **Unsafe Pickle Deserialization** flaw in its reward server. πŸ’₯ **Consequences**: Attackers can achieve **Remote Code Execution (RCE)**, leading to total system compromise.

Q2Root Cause? (CWE/Flaw)

πŸ›‘οΈ **Root Cause**: **CWE-502** (Deserialization of Untrusted Data). The code blindly unpickles user-controlled input without validation. πŸ“‰ **Flaw**: Trusting external data as executable Python objects.

Q3Who is affected? (Versions/Components)

πŸ‘₯ **Affected**: **Beijing Academy of Artificial Intelligence (BAAI)**'s **OmniGen2-RL** product. Specifically the `reward_server` components. πŸ“¦ **Version**: All versions prior to the fix (implied by the advisory).

Q4What can hackers do? (Privileges/Data)

πŸ’€ **Hacker Power**: Full **Remote Code Execution**. πŸ“‚ **Data**: Complete access to Confidentiality, Integrity, and Availability. The attacker owns the server.

Q5Is exploitation threshold high? (Auth/Config)

⚑ **Threshold**: **LOW**. CVSS Vector: `AV:N/AC:L/PR:N/UI:N`. No authentication, no user interaction, and network-accessible. 🎯 **Easy to exploit** for anyone on the network.

Q6Is there a public Exp? (PoC/Wild Exploitation)

πŸ” **Public Exploit**: **Yes**. References point to specific code lines in `reward_proxy.py` and `reward_server.py` on GitHub. πŸ“ **PoC**: Available via VulnCheck advisory and source code analysis.

Q7How to self-check? (Features/Scanning)

πŸ”Ž **Self-Check**: Scan for `pickle.loads()` or `pickle.load()` in `OmniGen2-RL/reward_server/` directories. πŸ“‹ **Look for**: Unsanitized input passed directly to deserialization functions.

Q8Is it fixed officially? (Patch/Mitigation)

🩹 **Fix**: Update to the patched version of OmniGen2-RL. πŸ“– **Reference**: Check the GitHub commit history or BAAI advisory for the specific fix commit. πŸ› οΈ **Mitigation**: Disable the reward server if not needed.

Q9What if no patch? (Workaround)

🚧 **No Patch?**: **Isolate** the reward server. 🚫 **Block** network access to port/service. πŸ›‘ **Disable** the `reward_server` component entirely if not essential for your workflow.

Q10Is it urgent? (Priority Suggestion)

πŸ”₯ **Urgency**: **CRITICAL**. CVSS Score is **9.8** (High). 🚨 Immediate action required. RCE via network is a top-priority threat. Patch or isolate NOW.