CVE-2022-31126

CRITICALNVD 10.010.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under NVD CVSS v3. EPSS exploit probability: 49.9%, top 1% 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
Trending — 3 sources updated this weekWeaponized
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 50%CVSS: 10.0Exploit: NoneExposed: 0

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

Roxy-wi is an open source web interface for managing Haproxy, Nginx, Apache and Keepalived servers. A vulnerability in Roxy-wi allows a remote, unauthenticated attacker to code execution by sending a specially crafted HTTP request to /app/options.py file. This affects Roxy-wi versions before 6.1.1.0. Users are advised to upgrade. There are no known workarounds for this issue.

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
86(Track)
EG Risk 86/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
Severity100% × 45%
Exploitation65% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.8%
KEV
Not listed

Published

July 6, 2022

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Jul 18, 2026
Patch available. Sources: github.
github Patch Available

Unauthenticated Remote Code Execution via ssh_command · Advisory · roxy-wi/roxy-wi · GitHub

https://github.com/hap-wi/roxy-wi/security/advisories/GHSA-mh86-878h-43c9

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 15× in last 7d / 42× 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-23 14:16 UTCEPSS rescore
  2. 2026-07-23 14:16 UTCEPSS rescore
  3. 2026-07-23 02:11 UTCEG score recompute
  4. 2026-07-22 22:58 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-19 02:27 UTCEPSS rescore
  13. 2026-07-18 10:03 UTCEPSS rescore
  14. 2026-07-18 10:02 UTCEPSS rescore
  15. 2026-07-17 04:24 UTCOSV refresh
  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-13 22:27 UTCEPSS rescore
  20. 2026-07-13 06:11 UTCEPSS rescore
  21. 2026-07-13 06:11 UTCEPSS rescore
  22. 2026-07-12 05:44 UTCEPSS rescore
  23. 2026-07-12 05:44 UTCEPSS rescore
  24. 2026-07-11 08:25 UTCEPSS rescore
  25. 2026-07-11 08:25 UTCEPSS rescore
Show 54 more
  1. 2026-07-09 19:07 UTCEPSS rescore
  2. 2026-07-07 13:44 UTCEPSS rescore
  3. 2026-07-05 02:28 UTCEPSS rescore
  4. 2026-07-05 02:28 UTCEPSS rescore
  5. 2026-07-04 06:29 UTCEPSS rescore
  6. 2026-07-04 06:29 UTCEPSS rescore
  7. 2026-07-01 15:04 UTCEPSS rescore
  8. 2026-06-30 23:20 UTCEPSS rescore
  9. 2026-06-30 23:20 UTCEPSS rescore
  10. 2026-06-29 02:32 UTCOSV refresh
  11. 2026-06-28 14:06 UTCEPSS rescore
  12. 2026-06-28 04:54 UTCEPSS rescore
  13. 2026-06-27 03:07 UTCEPSS rescore
  14. 2026-06-25 13:48 UTCEPSS rescore
  15. 2026-06-25 13:48 UTCEPSS rescore
  16. 2026-06-24 14:03 UTCEPSS rescore
  17. 2026-06-24 14:03 UTCEPSS rescore
  18. 2026-06-23 21:31 UTCEPSS rescore
  19. 2026-06-23 21:31 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-21 01:58 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-18 17:51 UTCEPSS rescore
  24. 2026-06-17 17:51 UTCEPSS rescore
  25. 2026-06-17 17:51 UTCEPSS rescore
  26. 2026-06-16 17:51 UTCEPSS rescore
  27. 2026-06-16 17:51 UTCEPSS rescore
  28. 2026-06-15 17:46 UTCEPSS rescore
  29. 2026-06-12 23:10 UTCEPSS rescore
  30. 2026-06-12 23:10 UTCEPSS rescore
  31. 2026-06-11 22:25 UTCOSV refresh
  32. 2026-06-10 22:16 UTCEPSS rescore
  33. 2026-06-10 13:20 UTCEPSS rescore
  34. 2026-06-08 14:15 UTCEPSS rescore
  35. 2026-06-08 14:15 UTCEPSS rescore
  36. 2026-06-05 22:45 UTCEPSS rescore
  37. 2026-06-05 22:45 UTCEPSS rescore
  38. 2026-06-05 06:09 UTCEPSS rescore
  39. 2026-06-05 06:09 UTCEPSS rescore
  40. 2026-06-02 20:11 UTCEPSS rescore
  41. 2026-06-02 20:11 UTCEPSS rescore
  42. 2026-06-02 20:11 UTCEPSS rescore
  43. 2026-06-01 13:50 UTCEPSS rescore
  44. 2026-06-01 13:50 UTCEPSS rescore
  45. 2026-05-28 13:43 UTCEPSS rescore
  46. 2026-05-28 13:43 UTCEPSS rescore
  47. 2026-05-28 13:43 UTCEPSS rescore
  48. 2026-05-27 13:39 UTCEPSS rescore
  49. 2026-05-27 13:39 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-26 07:17 UTCEPSS rescore
  52. 2026-05-26 07:17 UTCEPSS rescore
  53. 2026-05-26 07:17 UTCEPSS rescore
  54. 2026-05-25 19:23 UTCEG score recompute

Publicly available exploits

(2 references)

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

  • Exploit-DBEDB-51227✓ verified
    First seen Apr 3, 2023

    Roxy WI v6.1.0.0 - Unauthenticated Remote Code Execution (RCE)

    Open source ↗
  • Nucleihttp/cves/2022/CVE-2022-31126.yaml
    First seen Jan 1, 2022

    Roxy-WI - Remote Code Execution

    Open source ↗

Frequently asked(5)

What is CVE-2022-31126?
CVE-2022-31126 is a critical vulnerability published on July 6, 2022. Roxy-wi is an open source web interface for managing Haproxy, Nginx, Apache and Keepalived servers. A vulnerability in Roxy-wi allows a remote, unauthenticated attacker to code execution by sending a specially crafted HTTP request to /app/options.py file. This affects Roxy-wi versions before…
When was CVE-2022-31126 disclosed?
CVE-2022-31126 was first published in the National Vulnerability Database on July 6, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-31126 actively exploited?
CVE-2022-31126 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-31126?
CVE-2022-31126 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2022-31126?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-31126, 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-31126

Explore →

Is Your Infrastructure Affected by CVE-2022-31126?

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