How severe is CVE-2022-22916?

CVE-2022-22916 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-22916?

Affected package information for CVE-2022-22916 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2022-22916?

No fixed version has been published for CVE-2022-22916 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2022-22916 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2022-22916, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-22916?

CVE-2022-22916 has an EPSS (Exploit Prediction Scoring System) score of 90.2%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

When was CVE-2022-22916 published, and has it been updated?

CVE-2022-22916 was published on February 17, 2022 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2022-22916

CRITICAL

Published

Feb 17, 2022

Updated

Apr 10, 2026

Affected

0 pkgs

Patched

None yet

Exploits

4 known

EPSS Exploitation Probability

via FIRST.org ↗

90.2%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vulnerability via /x_program_center/jaxrs/invoke.

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vuln…

github.comNVDFeb 2022

O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vuln…

github.comGithubMay 2022

O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vuln…

github.comGithubMay 2022

Frequently Asked Questions

O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vulnerability via /x_program_center/jaxrs/invoke.

O3 Security · Impact-Aware SCA

Is CVE-2022-22916 in your stack?

O3 detects CVE-2022-22916 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works