cve.bz

CVE-2026-113799 abdolence slack-morphism-rust

5.3 mediumEPSS 0.4%Fix available

Medium (5.3) in abdolence slack-morphism-rust. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in slack-morphism 2.28.0.

On this page
Slack Morphism is a client library for Slack Web/Events API/Socket Mode and Block Kit. Versions 1.0.0 through 2.27.0 expose the correct Slack request HMAC when signature verification fails. For an invalid request, `slack-morphism` computes the correct signature for the attacker-controlled timestamp and request body and stores it in `SlackEventWrongSignatureError.generated_hash`. The error's `Debug` and `Display` representations expose that value, and the default Axum listener error handler logs it at error level. An attacker who can both reach the application's Slack callback endpoint and read its application/service logs can therefore use the verifier as a chosen-message HMAC oracle. The attacker can send an arbitrary request with an invalid signature, recover the correct signature from the resulting log entry, and resend the same request within the five-minute freshness window. The second request passes Slack Morphism's signature verification and reaches the protected application callback without the attacker knowing the Slack signing secret. Version 2.28.0 patches the issue.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 38th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: partial, assessed 2026-10-30. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-532 Insertion of Sensitive Information into Log File
OWASP Top 10
A09:2025 Logging & Alerting Failures
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • slack-morphism (crates.io): fixed in 2.28.0

Ask an AI about this CVE

Show the promptExplain CVE-2026-113799 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-113799?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-113799?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-113799 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
abdolence slack-morphism-rust>= 1.0.0, < 2.28.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-26w4-8w32-4x3vcrates.ioslack-morphism>=1.0.0 <2.28.02.28.0

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate because successful exploitation requires multiple compounding prerequisites, including network reachability to the endpoint and existing read privileges over application error logs. Although an attacker possessing log access could replay the leaked cryptographic token within a short time window to execute forged actions, `slack-morphism` is not included in core Red Hat product distributions. Consequently, typical Red Hat enterprise environments remain unaffected unless custom application stacks build upon this third-party Rust crate.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-113799.

Attack patterns (CAPEC)

  • CAPEC-215 Fuzzing for application mapping Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON