{"answers":{"affected":"2 open source packages ship an affected version, including slack-morphism.","exploited":"There is no known exploitation of CVE-2026-113799 in the wild and no public exploit code.","fix":"Upgrade slack-morphism to 2.28.0 or later.","what":"CVE-2026-113799 is a medium-severity vulnerability in abdolence slack-morphism-rust, published on 21 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-113799 and fix it if it is affected.\n\nWhat it is: CVE-2026-113799 is a medium-severity vulnerability in abdolence slack-morphism-rust, published on 21 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-113799 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- slack-morphism (crates.io): affected from 1.0.0; fixed in 2.28.0\n- slack-morphism (crates.io): affected from 1.0.0; fixed in 2.28.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-113799/ (Markdown: https://insights.sbomify.com/CVE-2026-113799/index.md)","id":"CVE-2026-113799","markdown":"https://insights.sbomify.com/CVE-2026-113799/index.md","name":"CVE-2026-113799","record":{"aliases":["GHSA-26w4-8w32-4x3v"],"analysis":null,"analysis_generated_by":null,"assigner":"GitHub_M","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-532","name":"Insertion of Sensitive Information into Log File"}],"description":"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.","ecosystems":["crates.io"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Slack Morphism verifier errors disclose valid HMACs in the logs","id":"CVE-2026-113799","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":null,"year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Electron: HID and USB permission checks can be attributed to the wrong origin","id":"CVE-2026-113800"},"packages":[{"ecosystem":"crates.io","fixed":["2.28.0"],"introduced":["1.0.0"],"last_affected":[],"package":"slack-morphism","purl":null,"source":"GHSA-26w4-8w32-4x3v"},{"ecosystem":"crates.io","fixed":["2.28.0"],"introduced":["1.0.0"],"last_affected":[],"package":"slack-morphism","purl":"pkg:cargo/slack-morphism","source":"GHSA-26w4-8w32-4x3v"}],"prev":{"headline":"Electron: Pointer lock permission requests can be attributed to the wrong frame","id":"CVE-2026-113798"},"products":["slack-morphism-rust"],"published":"2026-10-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-21","vendors":["abdolence"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-113799/"}