CVE-2026-114258 is a medium severity SQL injection vulnerability in the oretnom23 file-management-system-php affecting the files.php component. The flaw arises from manipulation of the fid/id argument, allowing remote attackers to perform SQL injection. The product uses a rolling release model, so no specific affected or fixed versions are available. The vulnerability is publicly known, but no patch or vendor response has been provided yet.
As part of Cisco's ongoing commitment to proactive security and product quality, engineering teams for Cisco Emergency Responder, Cisco Prime Collaboration Deployment, Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), and Cisco Unity Connection have conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.
The vulnerabilities tracked by CVE-2026-76477 are related to issues concerning improper neutralization of special elements used in an SQL command that are grouped under the Common Weakness Enumeration (CWE) Base CWE-89.
### Summary
Slack Morphism exposes the correct Slack request HMAC when signature verification fails.
For an invalid request, `slack-morphism` computes the correct signature for the attacker-controlled timestamp and request body and stores it in `SlackEventWrongSignatureError.generated_hash`. The error's `Debug` and `Display` representations expose that value, and the default Axum listener error handler logs it at error level.
An attacker who can both reach the application's Slack callback endpoint and read its application/service logs can therefore use the verifier as a chosen-message HMAC oracle. The attacker can send an arbitrary request with an invalid signature, recover the correct signature from the resulting log entry, and resend the same request within the five-minute freshness window. The second request passes Slack Morphism's signature verification and reaches the protected application callback without the attacker knowing the Slack signing secret.
I reproduced this end-to-end against both the Axum and Hyper integrations in `slack-morphism` 2.26.0 and 2.27.0.
### Details
The vulnerability is in Slack Morphism's request signature verification error path.
In `src/signature_verifier.rs`, `SlackEventSignatureVerifier::verify` computes the expected signature before comparing it with the untrusted `X-Slack-Signature` supplied by the request.
On a mismatch, the implementation creates a `SlackEventWrongSignatureError` containing the complete correct signature in its public `generated_hash` field.
Relevant source path:
```text
src/signature_verifier.rs:46-59
```
The error type is defined around:
```text
src/signature_verifier.rs:182-199
```
`generated_hash` is a public `String`; the type derives `Debug`, and its `Display` implementation also prints the generated signature.
The resulting source-to-sink path is:
1. `SlackEventSignatureVerifier::verify` computes the expected HMAC for the attacker-controlled timestamp and raw request body.
2. Signature verification fails because the attacker initially sends an invalid signature.
3. Slack Morphism places the correct expected value in `SlackEventWrongSignatureError.generated_hash`.
4. The error's `Debug` and `Display` representations reveal that HMAC.
5. The Axum middleware propagates/formats the error through `src/axum_support/slack_events_middleware.rs`.
6. The default listener error handler in `src/listener.rs` logs the error at error level.
7. The attacker reads the generated HMAC from the logs.
8. The attacker resends the identical timestamp and body using the disclosed value as `X-Slack-Signature`.
9. Slack Morphism accepts the request and executes the protected callback.
The Hyper path is also affected. `src/hyper_tokio/hyper_ext.rs` propagates the verifier error as a service error, and formatting that error similarly exposes the generated signature.
The disclosed value is exactly the credential required to authenticate the corresponding request:
```text
v0=hex(HMAC-SHA256(signing_secret, "v0:" || timestamp || ":" || raw_body))
```
There is no weakness in HMAC-SHA256 or the constant-time comparison itself. The vulnerability is that the expected authentication value is disclosed through the verifier's error path.
#### Affected versions
I reproduced the vulnerability against:
- `slack-morphism` 2.26.0
- `slack-morphism` 2.27.0
- current `master` at audit time:
`e3b3ecabf99dfcf6c3548a42fba89fbfa510d21c`
Git history indicates that the public `generated_hash` field was introduced in:
```text
9bf623bd51c6a9ef0cd22d842cc707a3311f1f22
```
and appears to have existed since v0.10.0. Since versions before 2.26.0 are unsupported and were not dynamically tested during this assessment, I am reporting the independently validated supported range as:
```text
>= 2.26.0, <= 2.27.0
```
No patched release is currently available.
### PoC
The PoC uses only localhost and a synthetic signing secret.
Tested environment:
```text
slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations
```
Synthetic signing secret:
```text
SLACK_MORPHISM_SYNTHETIC_SIGNING_SECRET_7c91
```
Start a Slack Morphism Axum callback endpoint using the normal Slack request signature verification middleware and the default listener error handling.
Send a request using:
```text
Body:
{"type":"attacker_chosen","action":"transfer"}
X-Slack-Request-Timestamp:
<current Unix timestamp>
X-Slack-Signature:
v0=0000000000000000000000000000000000000000000000000000000000000000
```
The all-zero signature is deliberately invalid.
#### First request
The first request is correctly rejected with HTTP 400.
However, Slack Morphism's default error output contains an entry equivalent to:
```text
SlackEventWrongSignatureError {
...
generated_hash: "v0=<correct-HMAC>"
}
```
where `<correct-HMAC>` is the valid Slack request signature for the exact attacker-controlled timestamp and body.
Copy that `generated_hash`.
Before the five-minute timestamp window expire
As part of Cisco's ongoing commitment to proactive security and product quality, engineering teams for Cisco Emergency Responder, Cisco Prime Collaboration Deployment, Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), and Cisco Unity Connection have conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.
The vulnerabilities tracked by CVE-2026-76475 are related to issues concerning improper neutralization of input during web page generation that are grouped under the Common Weakness Enumeration (CWE) Base CWE-79.
As part of Cisco's ongoing commitment to proactive security and product quality, engineering teams for Cisco Emergency Responder, Cisco Prime Collaboration Deployment, Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), and Cisco Unity Connection have conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.
The vulnerabilities tracked by CVE-2026-76474 are related to issues concerning improper authentication that are grouped under the Common Weakness Enumeration (CWE) Class CWE-287.
CVE-2026-76445 is a medium severity vulnerability in Cisco Open Source Snort3 detection engine. It involves a logic flaw in handling GPRS Tunneling Protocol (GTP) extension headers, which can cause the detection engine to enter an infinite loop and restart unexpectedly, resulting in a denial of service (DoS). The vulnerability can be exploited remotely and without authentication by sending crafted fragmented UDP datagrams containing these headers. No confidentiality or integrity impact is reported. The affected versions include multiple specific 3.1.x releases and 3.12.2.0.
As part of Cisco's ongoing commitment to proactive security and product quality, engineering teams for Cisco Emergency Responder, Cisco Prime Collaboration Deployment, Cisco Unified Communications Manager (Unified CM), Cisco Unified Communications Manager IM & Presence Service (Unified CM IM&P), Cisco Unified Communications Manager Session Management Edition (Unified CM SME), and Cisco Unity Connection have conducted a comprehensive internal security review. This review resulted in software hardening releases that address multiple internally discovered vulnerabilities.
The vulnerabilities tracked by CVE-2026-76473 are related to issues concerning improper control of a resource through its lifetime that are grouped under the Common Weakness Enumeration (CWE) Class CWE-74.
A vulnerability in Cisco Expressway Series could allow an unauthenticated, remote attacker to obtain sensitive information from an affected device.
This vulnerability is due to insufficient authorization checks of HTTP requests during Mobile and Remote Access (MRA) provisioning. An attacker could exploit this vulnerability by submitting a crafted URL request to an affected device. A successful exploit could allow the attacker to access sensitive information that they would otherwise not have authorization to access.
Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices.
A vulnerability in the database service feature of Cisco Expressway Series could allow an unauthenticated, remote attacker with network access to a Cisco Expressway device to execute arbitrary operating system commands as root.
This vulnerability is due to the use of persistent cookies. Additionally, there is insufficient validation of client certificates when the TLS Verify Mode is set to Enabled for clustering, which means that client certificates are not validated. An attacker with possession of the cookies could exploit this vulnerability by connecting to the database service and invoking specific remote procedure call (RPC) commands. A successful exploit could allow the attacker to execute arbitrary commands as root on the underlying operating system of an affected device.
Note: Cisco Expressway Series refers to Cisco Expressway Core (Expressway-C) devices and Cisco Expressway Edge (Expressway-E) devices.
A vulnerability in the interprocess communication (IPC) channel of the Secure Firewall Posture module in Cisco Secure Client could allow an authenticated, local attacker to elevate privileges on an affected device.
This vulnerability is due to insufficient validation of user-supplied input. An attacker could exploit this vulnerability by sending a series of crafted IPC messages to a local socket. A successful exploit could allow the attacker to perform limited file write operations on the filesystem with SYSTEM or root privileges.
Although this vulnerability affects the Secure Firewall Posture module in Cisco Secure Client on Windows, macOS, and Linux operating systems, this vulnerability could be used to obtain full root privileges on macOS and Linux. For that reason Cisco has assigned this security advisory a Security Impact Rating (SIR) of High rather than Medium as the score indicates.
CVE-2026-20356 is a high-severity vulnerability in Cisco Cyber Vision involving uncontrolled resource consumption. It was identified during an internal security review by Cisco's Snort 3 engineering team. The issue can lead to denial of service by exhausting system resources. Multiple specific versions of Cisco Cyber Vision are affected. No known exploits are reported in the wild. No patch or remediation details are provided in the input data.
CVE-2026-20236 is a high severity vulnerability in Cisco Cyber Vision involving incorrect calculation issues. These issues fall under the CWE-682 category and were identified during an internal security review by Cisco's Snort 3 Software engineering team. The vulnerability impacts multiple specific versions of Cisco Cyber Vision. The CVSS score of 7.5 indicates a high severity with network attack vector, low attack complexity, no privileges required, no user interaction, and an impact limited to availability. There are no known exploits in the wild and no vendor advisory or patch information is provided.
CVE-2026-20221 is a medium severity vulnerability in Cisco Cyber Vision affecting multiple versions. It involves a NULL pointer dereference in the Snort 3 Detection Engine's handling of nested GRE tunnel decapsulation. An unauthenticated remote attacker can send crafted GRE payloads to trigger an unexpected restart of the detection engine, causing denial of service or bypass conditions depending on configuration. The Snort 3 Detection Engine restarts automatically without manual intervention.
CVE-2026-20291 is a high-severity vulnerability in Cisco Cyber Vision involving improper privilege management. It affects multiple specific versions of the product. The flaw allows an attacker with limited privileges to potentially gain elevated access, impacting confidentiality, integrity, and availability. No known exploits are reported in the wild. Cisco has conducted internal security reviews and released software hardening updates addressing these issues.
CVE-2026-20197 is a medium severity vulnerability in Cisco Open Source Snort3 affecting multiple versions. It involves improper restriction of operations within the bounds of a memory buffer in the Snort 3 Teredo Detection Engine. An unauthenticated remote attacker can send crafted Teredo packets that cause the Snort 3 Detection Engine to restart unexpectedly, resulting in a denial of service (DoS) condition by interrupting packet inspection.
CVE-2026-20218 is a stack-based buffer overflow vulnerability in the Snort 3 Visual Basic for Applications (VBA) Decompression Engine used by multiple Cisco products. An unauthenticated remote attacker can exploit this flaw by sending specially crafted VBA data to the Snort 3 Detection Engine, causing it to restart unexpectedly and resulting in a denial of service (DoS). This vulnerability arises from improper range checking during VBA data decompression. The issue affects multiple specific versions of Cisco Open Source Snort3.
A vulnerability in Cisco Open Source Snort3's GRE Detection Engine allows unauthenticated remote attackers to cause the detection engine to restart by sending crafted GRE packets. This results in a denial-of-service (DoS) condition due to interruption of packet inspection.
CVE-2026-20043 is a critical vulnerability in Cisco Cyber Vision involving out-of-bounds write issues. These vulnerabilities were identified during an internal security review by Cisco's Snort 3 Software engineering team and relate to CWE-787. The flaw affects multiple specific versions of Cisco Cyber Vision. The CVSS v3.1 score is 9.0, indicating high impact on confidentiality, integrity, and availability. No public exploits are known, and no patch or remediation details are provided in the input data.
CVE-2026-20019 is a medium severity vulnerability in Cisco Open Source Snort3 affecting multiple versions. It involves an infinite loop caused by incomplete error checking when parsing UDP Netflow Protocol packets. An unauthenticated remote attacker can exploit this by sending a crafted Netflow packet, causing the Snort 3 Detection Engine to restart unexpectedly and resulting in a denial-of-service (DoS) condition.
CVE-2026-20011 is a medium severity vulnerability in Cisco Open Source Snort3 affecting multiple versions. It involves a buffer access issue with incorrect length values in the Snort 3 SMTP MIME Decoder. An unauthenticated remote attacker can exploit this by sending crafted SMTP packets, causing the Snort 3 Detection Engine to restart unexpectedly, resulting in a denial of service (DoS).