CVE-2022-22916

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 38.4%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 38%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
65(Track*)
EG Risk 65/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS
98.4%
KEV
Not listed

Published

February 17, 2022

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 19, 2026
No patch confirmed yet.
generic

O2OA-POC/POC.md at main · wendell1224/O2OA-POC · GitHub

https://github.com/wendell1224/O2OA-POC/blob/main/POC.md

Vendor Advisories for CVE-2022-22916(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 11× in last 7d / 43× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-24 14:15 UTCEPSS rescore
  2. 2026-07-23 14:16 UTCEPSS rescore
  3. 2026-07-23 02:08 UTCEG score recompute
  4. 2026-07-22 22:55 UTCEG score recompute
  5. 2026-07-22 14:06 UTCEPSS rescore
  6. 2026-07-22 14:06 UTCEPSS rescore
  7. 2026-07-21 15:22 UTCEPSS rescore
  8. 2026-07-21 15:22 UTCEPSS rescore
  9. 2026-07-20 17:05 UTCEPSS rescore
  10. 2026-07-19 14:29 UTCEPSS rescore
  11. 2026-07-19 02:27 UTCEPSS rescore
  12. 2026-07-18 10:02 UTCEPSS rescore
  13. 2026-07-18 10:02 UTCEPSS rescore
  14. 2026-07-17 22:59 UTCOSV refresh
  15. 2026-07-16 17:00 UTCEPSS rescore
  16. 2026-07-16 17:00 UTCEPSS rescore
  17. 2026-07-15 16:56 UTCEPSS rescore
  18. 2026-07-15 16:56 UTCEPSS rescore
  19. 2026-07-15 01:58 UTCEPSS rescore
  20. 2026-07-15 01:58 UTCEPSS rescore
  21. 2026-07-13 22:27 UTCEPSS rescore
  22. 2026-07-13 06:11 UTCEPSS rescore
  23. 2026-07-13 06:11 UTCEPSS rescore
  24. 2026-07-12 05:44 UTCEPSS rescore
  25. 2026-07-11 08:25 UTCEPSS rescore
Show 55 more
  1. 2026-07-09 19:07 UTCEPSS rescore
  2. 2026-07-09 02:55 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  3. 2026-07-09 01:24 UTCMITRE cvelistV5
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-06 02:21 UTCEPSS rescore
  6. 2026-07-05 02:28 UTCEPSS rescore
  7. 2026-07-05 00:28 UTCNVD updateCVSS v3 → 9.8 · severity → CRITICAL
  8. 2026-07-04 23:57 UTCMITRE cvelistV5
  9. 2026-07-01 15:04 UTCEPSS rescore
  10. 2026-06-30 23:20 UTCEPSS rescore
  11. 2026-06-30 23:20 UTCEPSS rescore
  12. 2026-06-29 20:32 UTCOSV refresh
  13. 2026-06-29 14:04 UTCEPSS rescore
  14. 2026-06-29 14:04 UTCEPSS rescore
  15. 2026-06-28 14:06 UTCEPSS rescore
  16. 2026-06-28 04:54 UTCEPSS rescore
  17. 2026-06-28 04:54 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-25 13:48 UTCEPSS rescore
  20. 2026-06-24 14:03 UTCEPSS rescore
  21. 2026-06-24 14:03 UTCEPSS rescore
  22. 2026-06-23 21:31 UTCEPSS rescore
  23. 2026-06-23 21:31 UTCEPSS rescore
  24. 2026-06-22 14:24 UTCEPSS rescore
  25. 2026-06-21 01:58 UTCEPSS rescore
  26. 2026-06-21 01:58 UTCEPSS rescore
  27. 2026-06-18 17:51 UTCEPSS rescore
  28. 2026-06-18 17:51 UTCEPSS rescore
  29. 2026-06-17 17:51 UTCEPSS rescore
  30. 2026-06-17 17:51 UTCEPSS rescore
  31. 2026-06-16 17:51 UTCEPSS rescore
  32. 2026-06-15 17:46 UTCEPSS rescore
  33. 2026-06-13 22:58 UTCEPSS rescore
  34. 2026-06-13 22:58 UTCEPSS rescore
  35. 2026-06-12 23:10 UTCEPSS rescore
  36. 2026-06-12 23:10 UTCEPSS rescore
  37. 2026-06-12 08:40 UTCOSV refresh
  38. 2026-06-10 22:16 UTCEPSS rescore
  39. 2026-06-10 13:20 UTCEPSS rescore
  40. 2026-06-08 14:15 UTCEPSS rescore
  41. 2026-06-08 14:15 UTCEPSS rescore
  42. 2026-06-05 22:45 UTCEPSS rescore
  43. 2026-06-05 06:09 UTCEPSS rescore
  44. 2026-06-05 06:09 UTCEPSS rescore
  45. 2026-06-01 13:50 UTCEPSS rescore
  46. 2026-06-01 13:50 UTCEPSS rescore
  47. 2026-06-01 13:50 UTCEPSS rescore
  48. 2026-05-29 13:42 UTCEPSS rescore
  49. 2026-05-28 13:43 UTCEPSS rescore
  50. 2026-05-28 13:43 UTCEPSS rescore
  51. 2026-05-28 13:43 UTCEPSS rescore
  52. 2026-05-27 13:39 UTCEPSS rescore
  53. 2026-05-27 13:39 UTCEPSS rescore
  54. 2026-05-26 02:53 UTCEG score recompute
  55. 2026-05-26 02:53 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoC0x7eTeam/CVE-2022-22916
    First seen May 21, 2022

    CVE-2022-22916,O2OA RCE 远程命令执行

    Open source ↗

Frequently asked(5)

What is CVE-2022-22916?
CVE-2022-22916 is a critical vulnerability published on February 17, 2022. O2OA v6.4.7 was discovered to contain a remote code execution (RCE) vulnerability via /xprogramcenter/jaxrs/invoke.
When was CVE-2022-22916 disclosed?
CVE-2022-22916 was first published in the National Vulnerability Database on February 17, 2022, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-22916 actively exploited?
CVE-2022-22916 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-22916?
CVE-2022-22916 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-22916?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-22916, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2022-22916

Explore →

Is Your Infrastructure Affected by CVE-2022-22916?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs