How severe is CVE-2022-39292?

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

Which packages are affected by CVE-2022-39292?

CVE-2022-39292 affects the following packages: slack-morphism (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2022-39292?

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

How do I detect CVE-2022-39292 in my crates.io dependencies?

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

How do I mitigate CVE-2022-39292 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.

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

No public exploit code has been indexed for CVE-2022-39292 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-39292?

CVE-2022-39292 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 59th 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-39292?

CVE-2022-39292 is classified as CWE-1258 (CWE-1258). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2022-39292 was published on October 10, 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.

🦀

🦀 crates.io

Not in CISA KEV

HIGH severity

CVE-2022-39292 — slack-morphism

HIGHFix: abdolence/slack-morphism-rust@48a1da2

CVE-2022-39292 is a high-severity (CVSS 7.5) CWE-1258 vulnerability in slack-morphism. A fix is available for slack-morphism — see the affected versions and patch details below.

Exposure of sensitive Slack webhook URLs in debug logs and traces

Also known asGHSA-4mjx-2gh5-ph8hRUSTSEC-2022-0087

Published

Oct 10, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 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-39292.

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% 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

🦀slack-morphism

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

Description

Impact

Debug logs expose sensitive URLs for Slack webhooks that contain private information.

Patches

The problem is fixed in v1.3.2 which redacts sensitive URLs for webhooks.

Workarounds

Disabling/filtering debug logs in case you use Slack webhooks using tracing log level and filters.

References

https://github.com/abdolence/slack-morphism-rust/releases/tag/v1.3.2

For more information

If you have any questions or comments about this advisory:

Open an issue in repo
Read our security policy

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`slack-morphism`	all versions	1.3.2`cargo update -p slack-morphism --precise 1.3.2`

Affected Products

1 product · 1 configurations

Application

slack morphismslack_morphism_project

≤ 1.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for slack-morphism, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update slack-morphism to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-39292 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.

Frequently Asked Questions

### Impact Debug logs expose sensitive URLs for Slack webhooks that contain private information. ### Patches The problem is fixed in v1.3.2 which redacts sensitive URLs for webhooks. ### Workarounds Disabling/filtering debug logs in case you use Slack webhooks using tracing log level and filters. ### References https://github.com/abdolence/slack-morphism-rust/releases/tag/v1.3.2 ### For more information If you have any questions or comments about this advisory: * Open an issue in [repo](https://github.com/abdolence/slack-morphism-rust) * Read our [security policy](https://github.com/abdo