How severe is CVE-2022-34558?

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

Which packages are affected by CVE-2022-34558?

CVE-2022-34558 affects the following packages: wmagent (PyPI), reqmgr2 (PyPI), reqmon (PyPI), global-workqueue (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-34558?

Update wmagent to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34558 is resolved across your whole dependency graph.

How do I detect CVE-2022-34558 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wmagent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-34558 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2022-34558?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-34558 can be triaged on real exposure rather than presence alone.

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

Yes. There are 1 known exploit references for CVE-2022-34558, including 1 in-the-wild exploitation 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-34558?

CVE-2022-34558 has an EPSS (Exploit Prediction Scoring System) score of 1.3%, placing it in the 68th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

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

CVE-2022-34558 was published on July 29, 2022 and was last updated on June 29, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

CRITICAL severity

CVE-2022-34558 — wmagent

CRITICAL

CVE-2022-34558 is a critical-severity (CVSS 9.8) remote code execution vulnerability in wmagent. 1 public exploit reference exists, so weaponization risk is real. A fix is available for wmagent — see the affected versions and patch details below.

WMAgent arbitrary code execution via a crafted dbs-client package

Also known asPYSEC-2022-43136PYSEC-2022-43163PYSEC-2022-43174PYSEC-2026-523

Published

Jul 29, 2022

Updated

Jun 29, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

1 known

Exploitation data as of Sep 21, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

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.

How urgent is this, really

CVE-2022-34558 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

4 pkgs affected

🐍wmagent🐍reqmgr2🐍reqmon🐍global-workqueue

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

WMAgent v1.3.3rc2 and 1.3.3rc1, reqmgr 2 1.4.1rc5 and 1.4.0rc2, reqmon 1.4.1rc5, and global-workqueue 1.4.1rc5 allows attackers to execute arbitrary code via a crafted dbs-client package.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`wmagent`	≥ 1.3.3rc1&&< 2.0.4	2.0.4`pip install --upgrade 'wmagent==2.0.4'`
🐍PyPI	`reqmgr2`	≥ 1.4.0rc2&&< 2.0.4	2.0.4`pip install --upgrade 'reqmgr2==2.0.4'`
🐍PyPI	`reqmon`	≥ 1.4.1rc5&&< 2.0.4	2.0.4`pip install --upgrade 'reqmon==2.0.4'`
🐍PyPI	`global-workqueue`	≥ 1.4.1rc5&&< 2.0.4	2.0.4`pip install --upgrade 'global-workqueue==2.0.4'`

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.

WMAgent v1.3.3rc2 and 1.3.3rc1, reqmgr 2 1.4.1rc5 and 1.4.0rc2, reqmon 1…

github.comNVDAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for wmagent, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update wmagent to 2.0.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-34558 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2022-34558 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2022-34558. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

WMAgent v1.3.3rc2 and 1.3.3rc1, reqmgr2 1.4.1rc5 and 1.4.0rc2, reqmon 1.4.1rc5, and global-workqueue 1.4.1rc5 allows attackers to execute arbitrary code via a crafted dbs-client package.

O3 Security · Impact-Aware SCA

Is CVE-2022-34558 in your dependencies?

O3 Security finds CVE-2022-34558 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works