slack-morphism

Version	Released
`2.31.1` patch	Oct 21, 2026
`2.31.0` minor	Oct 10, 2026
`2.30.0` minor	Oct 08, 2026
`2.29.0` minor	Sep 19, 2026
`2.28.0` minor	Sep 09, 2026
`2.27.0` minor 1 CVE	Sep 06, 2026
`2.26.0` minor 1 CVE	Sep 02, 2026
`2.25.0` minor 1 CVE	Aug 20, 2026
`2.24.1` unknown 1 CVE	Jul 29, 2026
`2.24.0` unknown 1 CVE	Jul 24, 2026
`2.23.0` unknown 1 CVE	Jul 14, 2026
`2.22.0` unknown 1 CVE	May 16, 2026
`2.21.0` unknown 1 CVE	May 09, 2026
`2.20.0` unknown 1 CVE	Apr 11, 2026
`2.19.0` unknown 1 CVE	Mar 11, 2026
`2.18.0` unknown 1 CVE	Feb 21, 2026
`2.17.0` unknown 1 CVE	Nov 06, 2025
`2.16.0` unknown 1 CVE	Sep 14, 2025
`2.15.0` unknown 1 CVE	Aug 24, 2025
`2.14.0` unknown 1 CVE	Jun 21, 2025
`2.12.0` unknown 1 CVE	Jun 03, 2025
`2.11.0` unknown 1 CVE	Apr 21, 2025
`2.10.1` unknown 1 CVE	Mar 19, 2025
`2.10.0` unknown 1 CVE	Feb 23, 2025
`2.9.0` unknown 1 CVE	Feb 02, 2025
`2.8.0` unknown 1 CVE	Jan 01, 2025
`2.7.0` unknown 1 CVE	Dec 09, 2024
`2.6.2` unknown 1 CVE	Dec 07, 2024
`2.6.1` unknown 1 CVE	Dec 06, 2024
`2.6.0` unknown 1 CVE	Nov 12, 2024
`2.5.0` unknown 1 CVE	Oct 04, 2024
`2.4.1` unknown 1 CVE	Jul 31, 2024
`2.4.0` unknown 1 CVE	Jun 28, 2024
`2.3.2` unknown 1 CVE	Jun 06, 2024
`2.3.1` unknown 1 CVE	Jun 02, 2024
`2.3.0` unknown 1 CVE	Jun 02, 2024
`2.2.0` unknown 1 CVE	Apr 22, 2024
`2.1.0` unknown 1 CVE	Mar 04, 2024
`2.0.0` unknown 1 CVE	Jan 27, 2024
`1.17.0` unknown 1 CVE	Jan 14, 2024
`1.16.1` unknown 1 CVE	Dec 14, 2023
`1.16.0` unknown yanked 1 CVE	Dec 08, 2023
`1.15.1` unknown 1 CVE	Oct 25, 2023
`1.15.0` unknown yanked 1 CVE	Oct 24, 2023
`1.14.5` unknown 1 CVE	Oct 11, 2023
`1.14.3` unknown 1 CVE	Sep 16, 2023
`1.14.2` unknown 1 CVE	Aug 21, 2023
`1.14.1` unknown 1 CVE	Aug 16, 2023
`1.14.0` unknown 1 CVE	Jul 10, 2023
`1.12.0` unknown 1 CVE	May 31, 2023

2.31.1 patch

Oct 21, 2026

2.31.0 minor

Oct 10, 2026

2.30.0 minor

Oct 08, 2026

2.29.0 minor

Sep 19, 2026

2.28.0 minor

Sep 09, 2026

2.27.0 minor

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Sep 06, 2026

2.26.0 minor

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Sep 02, 2026

2.25.0 minor

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Aug 20, 2026

2.24.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jul 29, 2026

2.24.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jul 24, 2026

2.23.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jul 14, 2026

2.22.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

May 16, 2026

2.21.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

May 09, 2026

2.20.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Apr 11, 2026

2.19.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Mar 11, 2026

2.18.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Feb 21, 2026

2.17.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Nov 06, 2025

2.16.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Sep 14, 2025

2.15.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Aug 24, 2025

2.14.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jun 21, 2025

2.12.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jun 03, 2025

2.11.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Apr 21, 2025

2.10.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Mar 19, 2025

2.10.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Feb 23, 2025

2.9.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Feb 02, 2025

2.8.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jan 01, 2025

2.7.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Dec 09, 2024

2.6.2 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Dec 07, 2024

2.6.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Dec 06, 2024

2.6.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Nov 12, 2024

2.5.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Oct 04, 2024

2.4.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jul 31, 2024

2.4.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jun 28, 2024

2.3.2 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jun 06, 2024

2.3.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jun 02, 2024

2.3.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jun 02, 2024

2.2.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Apr 22, 2024

2.1.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Mar 04, 2024

2.0.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jan 27, 2024

1.17.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jan 14, 2024

1.16.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Dec 14, 2023

1.16.0 unknown yanked

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Dec 08, 2023

1.15.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Oct 25, 2023

1.15.0 unknown yanked

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Oct 24, 2023

1.14.5 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Oct 11, 2023

1.14.3 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Sep 16, 2023

1.14.2 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Aug 21, 2023

1.14.1 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Aug 16, 2023

1.14.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

Jul 10, 2023

1.12.0 unknown

1 CVE

CVE-2026-113799 GHSA-26w4-8w32-4x3v Oct 21, 2026

Slack Morphism verifier errors disclose valid HMACs in the logs

5.3 / 10

Medium

Network High Low None Unchanged None High None

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:

src/signature_verifier.rs:46-59

The error type is defined around:

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:

SlackEventSignatureVerifier::verify computes the expected HMAC for the attacker-controlled timestamp and raw request body.
Signature verification fails because the attacker initially sends an invalid signature.
Slack Morphism places the correct expected value in SlackEventWrongSignatureError.generated_hash.
The error's Debug and Display representations reveal that HMAC.
The Axum middleware propagates/formats the error through src/axum_support/slack_events_middleware.rs.
The default listener error handler in src/listener.rs logs the error at error level.
The attacker reads the generated HMAC from the logs.
The attacker resends the identical timestamp and body using the disclosed value as X-Slack-Signature.
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:

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:

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:

>= 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:

slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations

Synthetic signing secret:

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:

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:

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 expires, resend the identical body and timestamp, changing only the signature header:

X-Slack-Signature: v0=<correct-HMAC-from-error>

Result

The second request returns HTTP 200 and the protected application callback executes.

In my end-to-end Axum reproduction the application observed:

PROTECTED_CALLBACK_EXECUTED body={"type":"attacker_chosen","action":"transfer"}

I independently reproduced the same primitive through the Hyper integration. The invalid request produces a service error containing:

WrongSignatureError(... generated_hash: "v0=<correct-HMAC>")

and replaying that value with the same timestamp and body causes the protected callback to execute.

Expected behavior

An invalid Slack request should be rejected without exposing any verifier-derived value that could authenticate a subsequent request.

Neither verifier error objects nor application logs should contain the expected HMAC.

Actual behavior

The invalid request is rejected, but Slack Morphism exposes the correct HMAC for the attacker-selected timestamp and body through the verifier error.

Reusing that disclosed HMAC within the freshness window causes the previously invalid attacker-controlled request to pass authentication and reach the protected callback.

Impact

An attacker requires:

network access to a Slack Morphism Events API, slash-command, interaction, or equivalent signed callback endpoint; and
lower-privilege read access to the application's/service's logs containing the verifier error.

The attacker does not need:

the Slack signing secret;
a Slack access token;
a Slack app token;
access to a Slack workspace; or
permission to modify the application's configuration.

The demonstrated impact is an authentication-boundary bypass: a lower-trust log reader can generate a valid signature for attacker-chosen request bytes and cause application functionality protected by Slack request authentication to execute.

The downstream consequences depend on the consuming application. A forged event, slash command, or interaction may trigger whatever business operations that application deliberately exposes to authenticated Slack callbacks. I am not claiming that the vulnerability itself grants access to Slack data or provides a specific application-level operation.

This is a Slack Morphism vulnerability rather than an Axum/Hyper or downstream application issue because Slack Morphism itself:

computes the correct HMAC;
places it into its own public error type;
exposes it through Debug and Display;
and, in the default Axum path, sends it to its own error logger.

Signature verification is enabled and correctly configured in the reproduction.

Suggested remediation

The safest fix is to remove generated_hash from SlackEventWrongSignatureError entirely.

The expected HMAC should not be retained in a public error object because merely changing Display would still leave other disclosure paths such as derived Debug, callers inspecting the public field, or nested error formatting.

Signature mismatch errors should contain only non-sensitive diagnostic information.

I also recommend:

implementing sanitized Debug and Display representations for verification errors;
reviewing all Axum and Hyper signature-error sinks;
returning an ordinary sanitized HTTP authentication failure from the Hyper integration instead of exposing cryptographic verification state as a service error;
adding equivalent regression coverage for Events API, commands, and interactions; and
advising users whose logs exposed generated_hash values to rotate the Slack signing secret if those logs were accessible to an untrusted party.

A regression test can directly assert that the expected HMAC is absent from both representations:

let error = verifier.verify(BOGUS, BODY, TIMESTAMP).unwrap_err();

assert!(!format!("{error:?}").contains(CORRECT_HMAC));
assert!(!format!("{error}").contains(CORRECT_HMAC));

An integration regression test should additionally verify that default listener logs do not contain the expected HMAC and that a request using the original invalid signature never reaches the application callback.

Fixed in


          2.28.0

References

Updated Oct 21, 2026 · Source: OSV.dev

May 31, 2023

Activity

Reach

Details