Most recent entries from all

EUVD-2026-290297

fkie_cve-2026-39972

Mercure is a protocol for pushing data updates to web browsers and other HTTP clients in a battery-efficient way. Prior to 0.22.0, a cache key collision vulnerability in TopicSelectorStore allows an attacker to poison the match result cache, potentially causing private updates to be delivered to unauthorized subscribers or blocking delivery to authorized ones. The cache key was constructed by concatenating the topic selector and topic with an underscore separator. Because both topic selectors and topics can contain underscores, two distinct pairs can produce the same key. An attacker who can subscribe to the hub or publish updates with crafted topic names can exploit this to bypass authorization checks on private updates. This vulnerability is fixed in 0.22.0.

GHSA-hwr4-mq23-wcv5 — mercure has Topic Selector Cache Key Collision

Affected: Go: github.com/dunglas/mercure

### Impact

A cache key collision vulnerability in `TopicSelectorStore` allows an attacker to poison the match result cache, potentially causing private updates to be delivered to unauthorized subscribers or blocking delivery to authorized ones.

The cache key was constructed by concatenating the topic selector and topic with an underscore separator:

```go k = "m_" + topicSelector + "_" + topic ```

Because both topic selectors and topics can contain underscores, two distinct pairs can produce the same key:

``` selector="foo_bar" topic="baz" → key: "m_foo_bar_baz" selector="foo" topic="bar_baz" → key: "m_foo_bar_baz" ```

An attacker who can subscribe to the hub or publish updates with crafted topic names can exploit this to bypass authorization checks on private updates.

### Patches

The vulnerability is fixed by replacing string-encoded cache keys with typed Go struct keys that are inherently collision-free:

```go type matchCacheKey struct { topicSelector string topic string } ```

The internal `TopicSelectorStoreCache` interface and sharded cache abstraction have also been removed in favor of a single typed otter cache.

Users should upgrade to version **0.22.0** or later.

### Workarounds

Disable the topic selector cache by setting `topic_selector_cache` to `-1` in the Caddyfile, or by passing a cache size of `0` when using the library directly. This eliminates the vulnerability at the cost of reduced performance.