Vulnerability Description
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.
Related Weaknesses (CWE)
References
- https://github.com/dunglas/mercure/commit/4964a69be904fd61e35b5f1e691271663b6fdd
- https://github.com/dunglas/mercure/security/advisories/GHSA-hwr4-mq23-wcv5
FAQ
What is CVE-2026-39972?
CVE-2026-39972 is a documented vulnerability. 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 a...
How severe is CVE-2026-39972?
CVSS scoring is not yet available for CVE-2026-39972. Check NVD for updates.
Is there a patch for CVE-2026-39972?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.