# CVE-2026-50571 — w3c websub

> As of 2026-10-28, CVE-2026-50571 is a MEDIUM-severity vulnerability in w3c websub, CVSS v3.1 5.7, EPSS 0.2% (14.1th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-50571 as of 2026-10-28; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

**Last updated:** 2026-10-28

## What is CVE-2026-50571?

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.

The record classifies CVE-2026-50571 under weakness class [CWE-79](https://intel.threadlinqs.com/cwe/CWE-79). Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs a user to take an action first, and has high impact on integrity. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 23 days ago.

## Severity and exploitation probability

- **CVSS v3.1 base score:** 5.7 — MEDIUM (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N`)
- **EPSS (FIRST):** 0.2% probability of exploitation in the next 30 days, higher than 14.1% of all scored CVEs
- **CISA KEV:** Not listed in the CISA Known Exploited Vulnerabilities catalog
- **Threadlinqs priority:** 3.4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- **Published:** 2026-10-27

## Is CVE-2026-50571 being exploited?

It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.

## Affected products and versions

- **w3c**: websub

## How to fix CVE-2026-50571

No vendor patch reference has been recorded for CVE-2026-50571 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

## Threat activity tracking CVE-2026-50571

No threat campaign in the Threadlinqs corpus currently references CVE-2026-50571, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

## Sources

Enriched from CVE.org, NVD, FIRST EPSS. This product uses the NVD API but is not endorsed or certified by the NVD.

**Vendor advisory and patch**

- [github.com](https://github.com/w3c/websub/security/advisories/GHSA-f4hw-w632-m6wh)

**Other references**

- [github.com](https://github.com/aaronpk/websub.rocks/commit/c9e24b8815c0d9f43350f0408ce2aedf9aa78ede)

Canonical: https://intel.threadlinqs.com/cve/CVE-2026-50571
No Threadlinqs detection currently covers CVE-2026-50571; it is re-checked on every ingest.
Indicator values unlock with TL Creds (https://threadlinqs.com/tl-creds); MCP access for AI agents needs Purple: https://intel.threadlinqs.com/mcp
