How severe is CVE-2022-36024?

CVE-2022-36024 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-36024?

CVE-2022-36024 affects the following packages: py-cord (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2022-36024?

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

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

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

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

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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

No public exploit code has been indexed for CVE-2022-36024 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

CVE-2022-36024 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 57th 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.

What type of vulnerability is CVE-2022-36024?

CVE-2022-36024 is classified as CWE-284 (CWE-284), CWE-862 (CWE-862). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2022-36024 was published on August 18, 2022 and was last updated on October 28, 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

HIGH severity

CVE-2022-36024 — py-cord

HIGHFix: Pycord-Development/pycord#1568

CVE-2022-36024 is a high-severity (CVSS 7.5) CWE-284 vulnerability in py-cord. A fix is available for py-cord — see the affected versions and patch details below.

Bots using py-cord as discord api wrapper are vulnerable to shutdowns through remote code execution

Also known asGHSA-qmhj-m29v-gvmrPYSEC-2022-43146

Published

Aug 18, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2022-36024.

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk+0.02%

Lower risk than most CVEs57th percentile — riskier than 57% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐍py-cord

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

Impact

py-cord is a an API wrapper for Discord written in Python. Bots using py-cord version 2.0.0 are vulnerable to remote shutdown if they are added to the server with the application.commands scope without the bot scope. Currently, it appears that all public bots that use slash commands are affected.

Patches

This issue has been patched in version 2.0.1.

Workarounds

There are currently no recommended workarounds - please upgrade to a patched version.

References

https://github.com/Pycord-Development/pycord/pull/1568

For more information

If you have any questions or comments about this advisory:

Open an issue in our GitHub
Email us at [email protected]

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`py-cord`	≥ 2.0.0&&< 2.0.1	2.0.1`pip install --upgrade 'py-cord==2.0.1'`

Affected Products

1 product · 1 configurations

Application

pycordpycord_development

1 version

2.0.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for py-cord, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update py-cord to 2.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-36024 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact py-cord is a an API wrapper for Discord written in Python. Bots using py-cord version 2.0.0 are vulnerable to remote shutdown if they are added to the server with the `application.commands` scope without the `bot` scope. Currently, it appears that all public bots that use slash commands are affected. ### Patches This issue has been patched in version 2.0.1. ### Workarounds There are currently no recommended workarounds - please upgrade to a patched version. ### References https://github.com/Pycord-Development/pycord/pull/1568 ### For more information If you have any questions or