CVE-2026-39972
Mercure is a protocol for pushing data updates to web browsers and …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/dunglas/mercure/commit/4964a69be904fd61e35b5f1e691271663b6fdd64
- github.com/dunglas/mercure/security/advisories/GHSA-hwr4-mq23-wcv5
- github.com/dunglas/mercure/releases/tag/v0.22.0
- github.com/advisories/GHSA-hwr4-mq23-wcv5
- nvd.nist.gov/vuln/detail/CVE-2026-39972
- nvd.nist.gov/vuln/detail/CVE-2026-39972
- cve.org/CVERecord?id=CVE-2026-39972
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.