Live › vulnerability › CVE-2026-50571
Go to dashboardThe WebSub W3C recommendation's intent-verification step has subscribers echo the hub.challenge value without requiring safe content typing or disabled MIME sniffing. An attacker can use a crafted verification request to run HTML or JavaScript in the subscriber's origin, reading session-bound data and browser storage.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 23:29 UTC. All times on this page are UTC.
Applications acting as WebSub subscribers that echo hub.challenge in responses served from their own origin are the exposed case. Systems that only receive content through a hub, or that never serve verification responses from an authenticated origin, are less exposed. The advisory does not name specific products or versions.
No product ranges from the sources yet.
text/html or sniffable content type.X-Content-Type-Options: nosniff.text/plain and set X-Content-Type-Options: nosniff on that response.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
WebSub is a W3C recommendation produced by the Social Web Working Group. In recommendation REC-websub-20180123, the intent-verification protocol requires a subscriber to echo the hub.challenge value, also exposed as hub_challenge by some frameworks, but does not require safe response media typing or disabled MIME sniffing. An attacker can initiate a subscription to obtain a callback URL and redirect a victim browser to a crafted verification request containing HTML or JavaScript. Subscribers that return the challenge as text/html can execute the reflected content in the subscriber origin, using a victim's existing session to read private data or perform actions, exposing localStorage or sessionStorage and browser permissions granted to that origin. An alternative uses the verification response as an attacker-controlled same-origin script resource to bypass script-src 'self'; this can remain possible with application/octet-stream when MIME sniffing is allowed. Safe media typing and X-Content-Type-Options: nosniff are both needed to address the described scenarios. WebSub Rocks demonstrated reflection, but the advisory does not establish practical impact on that demonstration site.
This page as .md · .json · in your agent: get_signal("CVE-2026-50571")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.