Intel

AIKIDO-2026-276642

github.com/dunglas/mercure/caddy is vulnerable to Exposure of Resource to Wrong Sphere

GHSA-qqgv-h269-4x6gPublished Oct 13, 2026
October 13, 2026

78

CVE Score

High

Exposure of Resource to Wrong Sphere

Are you affected? Scan for Free

TL;DR

Caddy's pooled transports for the Mercure module and its deprecated transport key are shared across every hub configured in the same process, keyed only by target or path and not by hub name. Two differently named hubs in one Caddy instance reuse the same pooled transport, local subscriber list, or BoltDB handle, so one hub's subscribers can receive another hub's private updates. The fix includes the configured hub name in the key for every pooled transport so differently named hubs never share subscribers or history.

How do I fix this?

Upgrade the github.com/dunglas/mercure/caddy library to the patch version.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you run more than one hub in the same Caddy process.

Versions

0.11.3 - 1.0.0

Fixed in 1.0.1

Background info

github.com/dunglas/mercure/caddy is vulnerable to Exposure of Resource to Wrong Sphere in versions 0.11.3 - 1.0.0.

Get secure today,
quickly and for free.

Secure your code, cloud, and runtime in one central system. Connect a repo to discover what the reasoning agents find in your codebase.

No credit card required | Scan results in 32 seconds.

Trusted by 150k+ orgs
  • Revolut
  • n8n
  • Lovable
  • Deel
  • Prove
  • Omnea