CVE-2026-105930 is an authorization vulnerability in Apache Pulsar affecting deployments with authentication, authorization, and package management enabled. It allows an authenticated user with permission to register or update functions, sources, or sinks in their own tenant namespace to access package contents stored in another tenant's namespace without having explicit package permissions there. The issue leads to disclosure of package contents, which may include sensitive application code or credentials, but does not allow modification or deletion of packages or affect service availability. The vulnerability affects Apache Pulsar versions from 2.8.0 before 4.0.14, from 4.1.0 through 4.1.3, and from 4.2.0 before 4.2.5. Fixed versions are 4.0.14 and 4.2.5 and later.
CVE-2026-105927 is an authorization vulnerability in Apache Pulsar's WebSocket service that allows an authenticated user with consume permission on a topic to inject messages into arbitrary topics via the dead letter policy configuration. The WebSocket service does not verify produce permissions on the dead letter topic, enabling unauthorized message injection. This vulnerability affects Apache Pulsar versions from 2.3.0 before 4.0.14 and from 4.1.0 before 4.2.5. The WebSocket service is disabled by default and can be disabled as a mitigation if not required. The vulnerability does not allow reading, modifying, or deleting existing messages, but injected messages may impact downstream applications depending on their processing logic.
CVE-2026-105926 is a missing authorization vulnerability in Apache Pulsar affecting the broker's binary protocol schema commands GetSchema and GetOrCreateSchema. Authenticated clients without proper permissions could read or register schema versions on topics in other namespaces or tenants, potentially leading to schema information disclosure and disruption of producers and consumers due to schema incompatibility. The vulnerability affects Pulsar versions from 2.2.0 before 4.0.14, 4.1.0 through 4.1.3, and 4.2.0 before 4.2.5. Fixed versions enforce appropriate topic permissions for these commands.
Apache Pulsar versions from 2.8.1 before 4.0.14 and from 4.1.0 before 4.2.5 contain a critical vulnerability in the MultiRolesTokenAuthorizationProvider. When the anonymousUserRole fallback is enabled, the provider fails to verify the cryptographic signature of JSON Web Tokens (JWTs), allowing unauthenticated clients to forge or use unsigned tokens to gain arbitrary roles, including super-user privileges. This enables unauthorized read and modification of tenants, namespaces, topics, permissions, and broker configuration. Deployments using the default authorization provider or without the anonymousUserRole setting are not affected. The issue is fixed in versions 4.0.14 and 4.2.5 and later.
MikroTik RouterOS versions up to 7.23.6 and 7.24.5 are affected by a session token replay vulnerability in the WebFig interface. The flaw allows attackers to bypass authentication by replaying captured session tokens across new ECDH sessions due to insufficient session expiration and token validation. The vulnerability arises because session tokens are generated with fixed salts and validated without verifying channel context, enabling persistent administrative access until tokens are cleared. This issue extends the impact of a prior transport-layer exposure vulnerability (CVE-2025-61481) which remains unpatched.
Two critical remote code execution vulnerabilities, collectively known as PHP2Shell, affect PHP versions back to 5.4 and impact widely used web applications such as WordPress, Drupal, and Joomla. These vulnerabilities involve memory management and error handling components of PHP and allow unauthenticated attackers to execute arbitrary code. Exploitation attempts have been detected in the wild shortly after patches were released. The flaws also enable reading sensitive process memory, potentially exposing credentials and secrets. Patches are available in PHP versions 8.5.12, 8.4.27, 8.3.36, 8.2.35, and backports for 7.4, 8.0, and 8.1. The PHP Foundation and security firms urge immediate patching due to the severity and active exploitation attempts.
A reachable exit vulnerability exists in NTPsec ntpd versions 1.1.4 through 1.2.5, allowing a remote attacker to cause a denial of service by crashing the daemon. This vulnerability impacts availability but does not affect confidentiality or integrity. The CVSS score is 7.5, indicating a high severity level.
CVE-2026-76481 is a high-severity vulnerability in Cisco Emergency Responder involving improper handling of exceptional conditions. This flaw is part of a group of issues identified through Cisco's internal security review and relates to CWE-703. The vulnerability affects multiple specific versions of Cisco Emergency Responder. It has a CVSS 3.1 score of 7.5, indicating high impact primarily on availability. No public exploits or known active exploitation have been reported.
CVE-2026-113800 is an origin validation error in the Electron framework affecting versions prior to 42.11.3, 43.7.0, 44.3.0, and 45.0.0-alpha.5. The flaw causes permission checks for HID and USB devices made from an iframe to incorrectly use the top-level frame's origin instead of the requesting iframe's origin. This can allow a cross-origin untrusted iframe to gain device access intended only for the top-level page. The issue is fixed in the specified versions.
### Summary
Slack Morphism exposes the correct Slack request HMAC when signature verification fails.
For an invalid request, `slack-morphism` computes the correct signature for the attacker-controlled timestamp and request body and stores it in `SlackEventWrongSignatureError.generated_hash`. The error's `Debug` and `Display` representations expose that value, and the default Axum listener error handler logs it at error level.
An attacker who can both reach the application's Slack callback endpoint and read its application/service logs can therefore use the verifier as a chosen-message HMAC oracle. The attacker can send an arbitrary request with an invalid signature, recover the correct signature from the resulting log entry, and resend the same request within the five-minute freshness window. The second request passes Slack Morphism's signature verification and reaches the protected application callback without the attacker knowing the Slack signing secret.
I reproduced this end-to-end against both the Axum and Hyper integrations in `slack-morphism` 2.26.0 and 2.27.0.
### Details
The vulnerability is in Slack Morphism's request signature verification error path.
In `src/signature_verifier.rs`, `SlackEventSignatureVerifier::verify` computes the expected signature before comparing it with the untrusted `X-Slack-Signature` supplied by the request.
On a mismatch, the implementation creates a `SlackEventWrongSignatureError` containing the complete correct signature in its public `generated_hash` field.
Relevant source path:
```text
src/signature_verifier.rs:46-59
```
The error type is defined around:
```text
src/signature_verifier.rs:182-199
```
`generated_hash` is a public `String`; the type derives `Debug`, and its `Display` implementation also prints the generated signature.
The resulting source-to-sink path is:
1. `SlackEventSignatureVerifier::verify` computes the expected HMAC for the attacker-controlled timestamp and raw request body.
2. Signature verification fails because the attacker initially sends an invalid signature.
3. Slack Morphism places the correct expected value in `SlackEventWrongSignatureError.generated_hash`.
4. The error's `Debug` and `Display` representations reveal that HMAC.
5. The Axum middleware propagates/formats the error through `src/axum_support/slack_events_middleware.rs`.
6. The default listener error handler in `src/listener.rs` logs the error at error level.
7. The attacker reads the generated HMAC from the logs.
8. The attacker resends the identical timestamp and body using the disclosed value as `X-Slack-Signature`.
9. Slack Morphism accepts the request and executes the protected callback.
The Hyper path is also affected. `src/hyper_tokio/hyper_ext.rs` propagates the verifier error as a service error, and formatting that error similarly exposes the generated signature.
The disclosed value is exactly the credential required to authenticate the corresponding request:
```text
v0=hex(HMAC-SHA256(signing_secret, "v0:" || timestamp || ":" || raw_body))
```
There is no weakness in HMAC-SHA256 or the constant-time comparison itself. The vulnerability is that the expected authentication value is disclosed through the verifier's error path.
#### Affected versions
I reproduced the vulnerability against:
- `slack-morphism` 2.26.0
- `slack-morphism` 2.27.0
- current `master` at audit time:
`e3b3ecabf99dfcf6c3548a42fba89fbfa510d21c`
Git history indicates that the public `generated_hash` field was introduced in:
```text
9bf623bd51c6a9ef0cd22d842cc707a3311f1f22
```
and appears to have existed since v0.10.0. Since versions before 2.26.0 are unsupported and were not dynamically tested during this assessment, I am reporting the independently validated supported range as:
```text
>= 2.26.0, <= 2.27.0
```
No patched release is currently available.
### PoC
The PoC uses only localhost and a synthetic signing secret.
Tested environment:
```text
slack-morphism = 2.27.0
Rust 1.98.1
Linux x86_64
Axum and Hyper integrations
```
Synthetic signing secret:
```text
SLACK_MORPHISM_SYNTHETIC_SIGNING_SECRET_7c91
```
Start a Slack Morphism Axum callback endpoint using the normal Slack request signature verification middleware and the default listener error handling.
Send a request using:
```text
Body:
{"type":"attacker_chosen","action":"transfer"}
X-Slack-Request-Timestamp:
<current Unix timestamp>
X-Slack-Signature:
v0=0000000000000000000000000000000000000000000000000000000000000000
```
The all-zero signature is deliberately invalid.
#### First request
The first request is correctly rejected with HTTP 400.
However, Slack Morphism's default error output contains an entry equivalent to:
```text
SlackEventWrongSignatureError {
...
generated_hash: "v0=<correct-HMAC>"
}
```
where `<correct-HMAC>` is the valid Slack request signature for the exact attacker-controlled timestamp and body.
Copy that `generated_hash`.
Before the five-minute timestamp window expire
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13, pointerLock permission requests from some cross-origin iframes caused session.setPermissionRequestHandler() to receive the top-level frame's requestingUrl and isMainFrame values instead of those of the requesting frame. An application that embeds untrusted iframe content and grants pointer lock based on the requesting origin could therefore grant the permission under the top-level page's identity. Applications that deny pointerLock for untrusted embedded content are not affected. This issue is fixed in versions 42.11.9, 43.7.6, 44.5.0, and 45.0.0-alpha.13.
Electron is a framework for writing cross-platform desktop applications using JavaScript, HTML and CSS. Prior to versions 42.11.1, 43.5.1, 44.1.1, and 45.0.0-alpha.4, chrome.tabs.query() returned each tab's url and title to extensions that had neither the tabs permission nor matching host permissions. An application that loaded an extension it did not fully trust through session.extensions.loadExtension could therefore allow that extension to read the URL and title of every webContents in its session. This issue is fixed in versions 42.11.1, 43.5.1, 44.1.1, and 45.0.0-alpha.4.
Multiple vulnerabilities have been identified in Cisco Expressway-C and Expressway-E products, affecting both virtual and appliance versions. These vulnerabilities impact versions 8.5, 8.5.1, and 8.5.3. The advisory references a security hardening release scheduled for October 2026, with fixed software versions noted in the vendor advisory. No specific technical details, CVSS scores, or exploitation information are provided in the input data.
A missing authorization vulnerability exists in BjornTech Swish for WooCommerce (woo-swish-e-commerce) up to version 3.7.8. This flaw allows exploitation of incorrectly configured access control security levels, potentially leading to unauthorized information disclosure and modification. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity level.
A path traversal vulnerability (CWE-22) exists in Bold Grid weForms allowing attackers to access restricted directories. This affects versions up to and including 1.6.28. The vulnerability has a CVSS 3.1 score of 7.5, indicating high severity with network attack vector, low attack complexity, no privileges or user interaction required, and impacts availability. No patch or remediation information is currently provided.
A stored cross-site scripting (XSS) vulnerability exists in Wasiliy Strecker Contest Gallery up to version 34.0.1. This vulnerability allows improper neutralization of input during web page generation, potentially enabling an attacker to inject malicious scripts. The vulnerability has a CVSS 3.1 base score of 6.5, indicating a medium severity level.
A reflected Cross-site Scripting (XSS) vulnerability exists in VideoWhisper.com Paid Videochat Turnkey Site (ppv-live-webcams) up to version 7.5.14. This vulnerability allows improper neutralization of input during web page generation, potentially enabling an attacker to execute arbitrary scripts in a user's browser. The vulnerability has a CVSS 3.1 score of 7.1, indicating high severity with impacts on confidentiality, integrity, and availability. No patch or remediation information is provided in the available data.
A missing authorization vulnerability exists in Magepeople inc.'s WpTravelly tour-booking-manager plugin, affecting versions up to 2.3.5. This flaw allows unauthorized users to exploit incorrectly configured access control security levels. The vulnerability has a CVSS 3.1 base score of 5.3, indicating a medium severity level. No known exploits are reported in the wild, and no official patch or remediation guidance is currently provided.