<?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>Wed, 07 Oct 2026 13:16:20 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-222193</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-222193</link>
      <description>EUVD-2026-222193</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-222193</guid>
    </item>
    <item>
      <title>fkie_cve-2025-27794</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-27794</link>
      <description>&lt;p&gt;Flarum is open-source forum software. A session hijacking vulnerability exists in versions prior to 1.8.10 when an attacker-controlled authoritative subdomain under a parent domain (e.g., `subdomain.host.com`) sets cookies scoped to the parent domain (`.host.com`). This allows session token replacement for applications hosted on sibling subdomains (e.g., `community.host.com`) if session tokens aren&amp;#39;t rotated post-authentication. Key Constraints are that the attacker must control any subdomain under the parent domain (e.g., `evil.host.com` or `x.y.host.com`), and the parent domain must not be on the Public Suffix List. Due to non-existent session token rotation after authenticating we can theoretically reproduce the vulnerability by using browser dev tools, but due to the browser&amp;#39;s security measures this does not seem to be exploitable as described. Version 1.8.10 contains a patch for the issue.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flarum is open-source forum software. A session hijacking vulnerability exists in versions prior to 1.8.10 when an attacker-controlled authoritative subdomain under a parent domain (e.g., `subdomain.host.com`) sets cookies scoped to the parent domain (`.host.com`). This allows session token replacement for applications hosted on sibling subdomains (e.g., `community.host.com`) if session tokens aren&amp;#39;t rotated post-authentication. Key Constraints are that the attacker must control any subdomain under the parent domain (e.g., `evil.host.com` or `x.y.host.com`), and the parent domain must not be on the Public Suffix List. Due to non-existent session token rotation after authenticating we can theoretically reproduce the vulnerability by using browser dev tools, but due to the browser&amp;#39;s security measures this does not seem to be exploitable as described. Version 1.8.10 contains a patch for the issue.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-27794</guid>
    </item>
    <item>
      <title>GHSA-hg9j-64wp-m9px — Flarum Vulnerable to Session Hijacking via Authoritative Subdomain Cookie Overwrite</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hg9j-64wp-m9px</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flarum/core, Packagist: flarum/framework&lt;/p&gt;
&lt;p&gt;## **Summary**  
A session hijacking vulnerability exists when an attacker-controlled **authoritative subdomain** under a parent domain (e.g., `subdomain.host.com`) sets cookies scoped to the parent domain (`.host.com`). This allows session token replacement for applications hosted on sibling subdomains (e.g., `community.host.com`) if session tokens aren&amp;#39;t rotated post-authentication.&lt;/p&gt;
&lt;p&gt;**Key Constraints**:  
- Attacker must control **any subdomain** under the parent domain (e.g., `evil.host.com` or `x.y.host.com`).  
- Parent domain must **not** be on the [Public Suffix List](https://publicsuffix.org/).&lt;/p&gt;
&lt;p&gt;Due to non-existent session token rotation after authenticating we can theoretically reproduce the vulnerability by using browser dev tools, but due to the browser&amp;#39;s security measures this does not seem to be exploitable as described.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## **Proof of Concept (Deno)**  
```ts
Deno.serve({
    port: 8000, // default
    hostname: &amp;#39;localhost&amp;#39;,
    onListen: (o) =&amp;gt; console.log(`Server started at http://${o.hostname}:${o.port}`, o),
  },
  async (req) =&amp;gt; (console.log(req), new Response(
    `You&amp;#39;ve been served! You came from ${req.headers.get(&amp;#39;referer&amp;#39;)}`,
    {
      //status: 302, // would redirect user to page they came from
      status: 200,
      headers: {
        &amp;#39;set-cookie&amp;#39;: &amp;#39;session_cookie=mytoken; Domain=.deno.dev; Secure; HttpOnly&amp;#39;,
        &amp;#39;location&amp;#39;: req.headers.get(&amp;#39;referer&amp;#39;)
      }
    }
  ))
);
```&lt;/p&gt;
&lt;p&gt;### **Attack Flow**  
1. **Attacker Setup**: Hosts serve…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: flarum/core, Packagist: flarum/framework&lt;/p&gt;
&lt;p&gt;## **Summary**  
A session hijacking vulnerability exists when an attacker-controlled **authoritative subdomain** under a parent domain (e.g., `subdomain.host.com`) sets cookies scoped to the parent domain (`.host.com`). This allows session token replacement for applications hosted on sibling subdomains (e.g., `community.host.com`) if session tokens aren&amp;#39;t rotated post-authentication.&lt;/p&gt;
&lt;p&gt;**Key Constraints**:  
- Attacker must control **any subdomain** under the parent domain (e.g., `evil.host.com` or `x.y.host.com`).  
- Parent domain must **not** be on the [Public Suffix List](https://publicsuffix.org/).&lt;/p&gt;
&lt;p&gt;Due to non-existent session token rotation after authenticating we can theoretically reproduce the vulnerability by using browser dev tools, but due to the browser&amp;#39;s security measures this does not seem to be exploitable as described.&lt;/p&gt;
&lt;p&gt;---&lt;/p&gt;
&lt;p&gt;## **Proof of Concept (Deno)**  
```ts
Deno.serve({
    port: 8000, // default
    hostname: &amp;#39;localhost&amp;#39;,
    onListen: (o) =&amp;gt; console.log(`Server started at http://${o.hostname}:${o.port}`, o),
  },
  async (req) =&amp;gt; (console.log(req), new Response(
    `You&amp;#39;ve been served! You came from ${req.headers.get(&amp;#39;referer&amp;#39;)}`,
    {
      //status: 302, // would redirect user to page they came from
      status: 200,
      headers: {
        &amp;#39;set-cookie&amp;#39;: &amp;#39;session_cookie=mytoken; Domain=.deno.dev; Secure; HttpOnly&amp;#39;,
        &amp;#39;location&amp;#39;: req.headers.get(&amp;#39;referer&amp;#39;)
      }
    }
  ))
);
```&lt;/p&gt;
&lt;p&gt;### **Attack Flow**  
1. **Attacker Setup**: Hosts serve…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hg9j-64wp-m9px</guid>
    </item>
  </channel>
</rss>
