### Summary
Slack Morphism exposes 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.
I reproduced this end-to-end against both the Axum and Hyper integrations in `slack-morphism` 2.26.0 and 2.27.0.
### Details
The vulnerability is in Slack Morphism's request signature verification error path.
In `src/signature_verifier.rs`, `SlackEventSignatureVerifier::verify` computes the expected signature before comparing it with the untrusted `X-Slack-Signature` supplied by the request.
On a mismatch, the implementation creates a `SlackEventWrongSignatureError` containing the complete correct signature in its public `generated_hash` field.
Relevant source path:
```text
src/signature_verifier.rs:46-59
```
The error type is defined around:
```text
src/signature_verifier.rs:182-199
```
`generated_hash` is a public `String`; the type derives `Debug`, and its `Display` implementation also prints the generated signature.
The resulting source-to-sink path is:
1. `SlackEventSignatureVerifier::verify` computes the expected HMAC for the attacker-controlled timestamp and raw request body.
2. Signature verification fails because the attacker initially sends an invalid signature.
3. Slack Morphism places the correct expected value in `SlackEventWrongSignatureError.generated_hash`.
4. The error's `Debug` and `Display` representations reveal that HMAC.
5. The Axum middleware propagates/formats the error through `src/axum_support/slack_events_middleware.rs`.
6. The default listener error handler in `src/listener.rs` logs the error at error level.
7. The attacker reads the generated HMAC from the logs.
8. The attacker resends the identical timestamp and body using the disclosed value as `X-Slack-Signature`.
9. Slack Morphism accepts the request and executes the protected callback.
The Hyper path is also affected. `src/hyper_tokio/hyper_ext.rs` propagates the verifier error as a service error, and formatting that error similarly exposes the generated signature.
The disclosed value is exactly the credential required to authenticate the corresponding request:
```text
v0=hex(HMAC-SHA256(signing_secret, "v0:" || timestamp || ":" || raw_body))
```
There is no weakness in HMAC-SHA256 or the constant-time comparison itself. The vulnerability is that the expected authentication value is disclosed through the verifier's error path.
#### Affected versions
I reproduced the vulnerability against:
- `slack-morphism` 2.26.0
- `slack-morphism` 2.27.0
- current `master` at audit time:
`e3b3ecabf99dfcf6c3548a42fba89fbfa510d21c`
Git history indicates that the public `generated_hash` field was introduced in:
```text
9bf623bd51c6a9ef0cd22d842cc707a3311f1f22
```
and appears to have existed since v0.10.0. Since versions before 2.26.0 are unsupported and were not dynamically tested during this assessment, I am reporting the independently validated supported range as:
```text
>= 2.26.0, <= 2.27.0
```
No patched release is currently available.
### PoC
The PoC uses only localhost and a synthetic signing secret.
Tested environment:
```text
slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations
```
Synthetic signing secret:
```text
SLACK_MORPHISM_SYNTHETIC_SIGNING_SECRET_7c91
```
Start a Slack Morphism Axum callback endpoint using the normal Slack request signature verification middleware and the default listener error handling.
Send a request using:
```text
Body:
{"type":"attacker_chosen","action":"transfer"}
X-Slack-Request-Timestamp:
<current Unix timestamp>
X-Slack-Signature:
v0=0000000000000000000000000000000000000000000000000000000000000000
```
The all-zero signature is deliberately invalid.
#### First request
The first request is correctly rejected with HTTP 400.
However, Slack Morphism's default error output contains an entry equivalent to:
```text
SlackEventWrongSignatureError {
...
generated_hash: "v0=<correct-HMAC>"
}
```
where `<correct-HMAC>` is the valid Slack request signature for the exact attacker-controlled timestamp and body.
Copy that `generated_hash`.
Before the five-minute timestamp window expire
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13, pointerLock permission requests from some cross-origin iframes caused session.setPermissionRequestHandler() to receive the top-level frame's requestingUrl and isMainFrame values instead of those of the requesting frame. An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could therefore grant the permission under the top-level page's identity. Applications that deny pointerLock for untrusted embedded content are not affected. This issue is fixed in versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13.
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.1, 43.5.1, 44.1.1, and 45.0.0-alpha.4, chrome.tabs.query() returned each tab's url and title to extensions that had neither the tabs permission nor matching host permissions. An application that loaded an extension it did not fully trust through session.extensions.loadExtension could therefore allow that extension to read the URL and title of every webContents in its session. This issue is fixed in versions 42.11.1, 43.5.1, 44.1.1, and 45.0.0-alpha.4.
Multiple vulnerabilities have been identified in Cisco Expressway-C and Expressway-E products, affecting both virtual and appliance versions. These vulnerabilities impact versions 8.5, 8.5.1, and 8.5.3. The advisory references a security hardening release scheduled for October 2026, with fixed software versions noted in the vendor advisory. No specific technical details, CVSS scores, or exploitation information are provided in the input data.
A missing authorization vulnerability exists in BjornTech Swish for WooCommerce (woo-swish-e-commerce) up to version 3.7.8. This flaw allows exploitation of incorrectly configured access control security levels, potentially leading to unauthorized information disclosure and modification. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity level.
A reflected Cross-site Scripting (XSS) vulnerability exists in VideoWhisper.com Paid Videochat Turnkey Site (ppv-live-webcams) up to version 7.5.14. This vulnerability allows improper neutralization of input during web page generation, potentially enabling an attacker to execute arbitrary scripts in a user's browser. The vulnerability has a CVSS 3.1 score of 7.1, indicating high severity with impacts on confidentiality, integrity, and availability. No patch or remediation information is provided in the available data.
A missing authorization vulnerability exists in Magepeople inc.'s WpTravelly tour-booking-manager plugin, affecting versions up to 2.3.5. This flaw allows unauthorized users to exploit incorrectly configured access control security levels. The vulnerability has a CVSS 3.1 base score of 5.3, indicating a medium severity level. No known exploits are reported in the wild, and no official patch or remediation guidance is currently provided.
A security vulnerability (CVE-2026-114248) exists in the dhikshitha29 Insurance-Management-System affecting the Plan Management Form component. The vulnerability involves manipulation of the submit, Plan_no, and Name arguments in the /Admin/includes/AddNewPlan-inc.php file, leading to missing authentication. This flaw can be exploited remotely. The vulnerability has a medium severity with a CVSS score of 5.3. The project uses a rolling release model, so no specific affected or fixed versions are available. The issue was reported early but has not yet received a response or patch from the vendor. Public exploit details have been disclosed but no known exploitation in the wild has been confirmed.
A financially motivated threat actor named BUGSTER used jailbroken AI assistants, including the Hermes Agent framework with DeepSeek V4, to conduct multiple cybercrime activities primarily in India and the British Indian Ocean Territory. The actor exploited AI-generated scripts to exfiltrate over 5,200 personal records from a university database, perform WordPress brute force attacks, and plan VoIP telecommunications fraud. Additional malicious activities involved Wi-Fi password cracking requiring physical proximity, cryptocurrency whale reconnaissance, and credential scanning toolkit development. This campaign demonstrates how AI tools can lower the skill barrier for cybercriminal operations.
A segmentation violation vulnerability exists in the check_media_profile function of the gpac software. This flaw can cause a crash when processing media profiles. The issue affects multiple specific versions of gpac. The vulnerability has a CVSS score of 5.5, indicating a medium severity impact primarily due to availability disruption.
Reachable exit in NTPsec ntpd 1.1.4 through 1.2.5 allows a remote attacker to terminate the daemon via an NTS request with excess NTS Cookie Placeholder extension fields.
This update includes the following RPMs:
prometheus3.5:
* prometheus3.5-3.5.5-0.9.hum1 (aarch64, x86_64)
* prometheus3.5-3.5.5-0.9.hum1.src (src)
Security Fix(es):
prometheus3.5:
* CVE-2026-111943
CVE-2025-71438 is an out-of-bounds read vulnerability in the gpac software, specifically in the function gf_odf_ac4_cfg_dsi_v1 within the /odf/descriptors.c file. This flaw can cause an application crash or denial of service. The vulnerability has a medium severity rating with a CVSS score of 5.5. It affects multiple specific versions of gpac as listed. There is no information about available patches or fixes in the provided data.
CVE-2026-111834 is a critical vulnerability in Mang Board WP by Kitae Park that allows unrestricted upload of files with dangerous types, enabling attackers to upload web shells to the web server. This vulnerability affects all versions prior to 2.4.5. It has a high CVSS score of 9.9, indicating severe impact on confidentiality, integrity, and availability. A fix is available in version 2.4.5.
CVE-2026-111833 is a path traversal vulnerability in Bold Grid weForms affecting versions prior to 1.6.29. This flaw allows an attacker to improperly access files outside a restricted directory, potentially leading to denial of service. The vulnerability has a high severity rating with a CVSS score of 7.5. A fix is available in version 1.6.29.
CVE-2026-111837 is a stored cross-site scripting (XSS) vulnerability in the Contest Gallery product by Wasiliy Strecker. The flaw involves improper neutralization of input during web page generation, allowing attackers to inject malicious scripts. This vulnerability affects versions from initial releases up to 34.0.1. A fix is available in version 34.0.2. The CVSS 3.1 base score is 6.5, indicating a medium severity level.
Two vulnerabilities in PHP versions 8.1, 8.3, and 8.5 allow remote attackers to execute arbitrary code. The first vulnerability (CVE-2026-109618) involves incorrect handling of out-of-memory conditions during request processing. The second (CVE-2026-109619) involves improper management of internal request state across worker reuse. These issues could cause PHP to crash or run malicious programs if exploited. Fixed versions are available for Ubuntu distributions.
