<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 11:01:11 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-337318</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-337318</link>
      <description>EUVD-2026-337318</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-337318</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34226</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34226</link>
      <description>&lt;p&gt;Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. Versions prior to 20.8.9 may attach cookies from the current page origin (`window.location`) instead of the request target URL when `fetch(..., { credentials: &amp;#34;include&amp;#34; })` is used. This can leak cookies from origin A to destination B. Version 20.8.9 fixes the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Happy DOM is a JavaScript implementation of a web browser without its graphical user interface. Versions prior to 20.8.9 may attach cookies from the current page origin (`window.location`) instead of the request target URL when `fetch(..., { credentials: &amp;#34;include&amp;#34; })` is used. This can leak cookies from origin A to destination B. Version 20.8.9 fixes the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34226</guid>
    </item>
    <item>
      <title>GHSA-w4gp-fjgq-3q4g — Happy DOM's fetch credentials include uses page-origin cookies instead of target-origin cookies</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-w4gp-fjgq-3q4g</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: happy-dom&lt;/p&gt;
&lt;p&gt;### Summary
`happy-dom` may attach cookies from the current page origin (`window.location`) instead of the request target URL when `fetch(..., { credentials: &amp;#34;include&amp;#34; })` is used. This can leak cookies from origin A to destination B.&lt;/p&gt;
&lt;p&gt;### Details
In [`packages/happy-dom/src/fetch/utilities/FetchRequestHeaderUtility.ts`](https://github.com/capricorn86/happy-dom/blob/f8d8cad41e9722fab9eefb9dfb3cca696462e908/packages/happy-dom/src/fetch/utilities/FetchRequestHeaderUtility.ts) (`getRequestHeaders()`), cookie selection is performed with `originURL`:&lt;/p&gt;
&lt;p&gt;```ts
const originURL = new URL(options.window.location.href);
const isCORS = FetchCORSUtility.isCORS(originURL, options.request[PropertySymbol.url]);
// ...
const cookies = options.browserFrame.page.context.cookieContainer.getCookies(
  originURL,
  false
);
```&lt;/p&gt;
&lt;p&gt;Here, `originURL` represents the page URL, not the request destination URL. For outgoing requests, cookie lookup should use the request URL (for example: `new URL(options.request[PropertySymbol.url])`).&lt;/p&gt;
&lt;p&gt;### PoC Script Content&lt;/p&gt;
&lt;p&gt;```javascript
const http = require(&amp;#39;http&amp;#39;);
const dns = require(&amp;#39;dns&amp;#39;).promises;
const { Browser } = require(&amp;#39;happy-dom&amp;#39;);&lt;/p&gt;
&lt;p&gt;async function listen(server, host) {
  return new Promise((resolve) =&amp;gt; server.listen(0, host, () =&amp;gt; resolve(server.address().port)));
}&lt;/p&gt;
&lt;p&gt;async function run() {
  let observedCookieHeader = null;
  const pageHost = process.env.PAGE_HOST || &amp;#39;a.127.0.0.1.nip.io&amp;#39;;
  const apiHost = process.env.API_HOST || &amp;#39;b.127.0.0.1.nip.io&amp;#39;;…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: happy-dom&lt;/p&gt;
&lt;p&gt;### Summary
`happy-dom` may attach cookies from the current page origin (`window.location`) instead of the request target URL when `fetch(..., { credentials: &amp;#34;include&amp;#34; })` is used. This can leak cookies from origin A to destination B.&lt;/p&gt;
&lt;p&gt;### Details
In [`packages/happy-dom/src/fetch/utilities/FetchRequestHeaderUtility.ts`](https://github.com/capricorn86/happy-dom/blob/f8d8cad41e9722fab9eefb9dfb3cca696462e908/packages/happy-dom/src/fetch/utilities/FetchRequestHeaderUtility.ts) (`getRequestHeaders()`), cookie selection is performed with `originURL`:&lt;/p&gt;
&lt;p&gt;```ts
const originURL = new URL(options.window.location.href);
const isCORS = FetchCORSUtility.isCORS(originURL, options.request[PropertySymbol.url]);
// ...
const cookies = options.browserFrame.page.context.cookieContainer.getCookies(
  originURL,
  false
);
```&lt;/p&gt;
&lt;p&gt;Here, `originURL` represents the page URL, not the request destination URL. For outgoing requests, cookie lookup should use the request URL (for example: `new URL(options.request[PropertySymbol.url])`).&lt;/p&gt;
&lt;p&gt;### PoC Script Content&lt;/p&gt;
&lt;p&gt;```javascript
const http = require(&amp;#39;http&amp;#39;);
const dns = require(&amp;#39;dns&amp;#39;).promises;
const { Browser } = require(&amp;#39;happy-dom&amp;#39;);&lt;/p&gt;
&lt;p&gt;async function listen(server, host) {
  return new Promise((resolve) =&amp;gt; server.listen(0, host, () =&amp;gt; resolve(server.address().port)));
}&lt;/p&gt;
&lt;p&gt;async function run() {
  let observedCookieHeader = null;
  const pageHost = process.env.PAGE_HOST || &amp;#39;a.127.0.0.1.nip.io&amp;#39;;
  const apiHost = process.env.API_HOST || &amp;#39;b.127.0.0.1.nip.io&amp;#39;;…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-w4gp-fjgq-3q4g</guid>
    </item>
  </channel>
</rss>
