1 hour ago · Tech · hide

This is the short story of CVE-2026-130935, a bug/vulnerability I reported to Google on 2025-01-25, which was fixed on 2026-11-17. A referrer policy is a website’s declaration to a browser, asking it to modify the algorithm used to populate the Referer header when fetching subresources, prefetching, or performing navigations. For example, a website can use the no-referrer policy to prevent the browser from sending the Referer header completely, or the same-origin policy to send it only when the request is made to a URL with the same origin. The origin policy sends only the origin, without any of the other specific details (URL path, and so on). This allows websites to control how much information about the referring page is disclosed to connected-to websites. These days, browsers default to strict-origin-when-cross-origin, which sends the full URL (excluding #fragments) to same-origin requests, only the origin to cross-origin requests, and no header at all for https -> http requests.…

Commenting on Bubbles has been removed. Why? If you want to talk about this post, write to the author, use the comments on their blog if it has them, or reply with a "RE:" post on your own blog. Suggestions? feedback@bubbles.town