<?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 15:26:31 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-357585</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-357585</link>
      <description>EUVD-2026-357585</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-357585</guid>
    </item>
    <item>
      <title>fkie_cve-2026-62283</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-62283</link>
      <description>&lt;p&gt;Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&amp;amp;M tool. Nezha versions 1.14.13 through 1.14.14 and 2.0.0 through 2.0.9 do not bind stream identifiers created by CreateStream in service/rpc/io_stream.go to their creating user, and `GET /ws/terminal/:id` and `GET /ws/file/:id` only check whether the supplied UUID exists. An authenticated RoleMember who obtains a live stream UUID from logs, browser history, referer data, or telemetry can attach to another user&amp;#39;s terminal or file-manager session, read and write target-server files, and execute shell commands. This issue is fixed in version 2.0.10.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Nezha Monitoring is a self-hostable, lightweight, servers and websites monitoring and O&amp;amp;M tool. Nezha versions 1.14.13 through 1.14.14 and 2.0.0 through 2.0.9 do not bind stream identifiers created by CreateStream in service/rpc/io_stream.go to their creating user, and `GET /ws/terminal/:id` and `GET /ws/file/:id` only check whether the supplied UUID exists. An authenticated RoleMember who obtains a live stream UUID from logs, browser history, referer data, or telemetry can attach to another user&amp;#39;s terminal or file-manager session, read and write target-server files, and execute shell commands. This issue is fixed in version 2.0.10.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-62283</guid>
    </item>
    <item>
      <title>GHSA-q6xx-5vr8-p898 — Nezha vulnerable to cross-tenant terminal/file-manager session hijack via WebSocket stream UUID without ownership check</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-q6xx-5vr8-p898</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nezhahq/nezha&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In nezha **v1.14.13–v1.14.14** and **v2.0.0–v2.0.9**, the WebSocket endpoints `GET /ws/terminal/:id` and `GET /ws/file/:id` authenticate the caller only by the presence of a valid stream UUID, with no ownership check tying that UUID to the user who created the stream. Any authenticated dashboard user (including a `RoleMember`) who learns a live stream UUID can attach to the session and gain interactive shell access or full file-manager control on the target server — i.e. cross-tenant RCE.&lt;/p&gt;
&lt;p&gt;This was silently fixed in commit [`6661d6a`](https://github.com/nezhahq/nezha/commit/6661d6a7fc1c269f55c7f4e775082ad23fbe0f54) (2026-05-18, shipped in v2.0.10). At submission time no public CVE/GHSA covers this fix, so operators of v1.14.x and pre-v2.0.10 v2.x deployments have no signal that they are running vulnerable code.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Stream allocation — `service/rpc/io_stream.go` (v2.0.9):**&lt;/p&gt;
&lt;p&gt;```go
func (s *NezhaHandler) CreateStream(streamId string) {
    s.ioStreamMutex.Lock()
    defer s.ioStreamMutex.Unlock()&lt;/p&gt;
&lt;p&gt;s.ioStreams[streamId] = &amp;amp;ioStreamContext{
        userIoConnectCh:  make(chan struct{}),
        agentIoConnectCh: make(chan struct{}),
    }
}
```&lt;/p&gt;
&lt;p&gt;No creator is bound to the stream.&lt;/p&gt;
&lt;p&gt;**Stream attach — `cmd/dashboard/controller/terminal.go` (v2.0.9):**&lt;/p&gt;
&lt;p&gt;```go
// @Router /ws/terminal/{id} [get]
func terminalStream(c *gin.Context) (any, error) {
    streamId := c.Param(&amp;#34;id&amp;#34;)
    if _, err := rpc.NezhaHandlerSingleton.GetStream(streamId); err != nil {…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/nezhahq/nezha&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In nezha **v1.14.13–v1.14.14** and **v2.0.0–v2.0.9**, the WebSocket endpoints `GET /ws/terminal/:id` and `GET /ws/file/:id` authenticate the caller only by the presence of a valid stream UUID, with no ownership check tying that UUID to the user who created the stream. Any authenticated dashboard user (including a `RoleMember`) who learns a live stream UUID can attach to the session and gain interactive shell access or full file-manager control on the target server — i.e. cross-tenant RCE.&lt;/p&gt;
&lt;p&gt;This was silently fixed in commit [`6661d6a`](https://github.com/nezhahq/nezha/commit/6661d6a7fc1c269f55c7f4e775082ad23fbe0f54) (2026-05-18, shipped in v2.0.10). At submission time no public CVE/GHSA covers this fix, so operators of v1.14.x and pre-v2.0.10 v2.x deployments have no signal that they are running vulnerable code.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;**Stream allocation — `service/rpc/io_stream.go` (v2.0.9):**&lt;/p&gt;
&lt;p&gt;```go
func (s *NezhaHandler) CreateStream(streamId string) {
    s.ioStreamMutex.Lock()
    defer s.ioStreamMutex.Unlock()&lt;/p&gt;
&lt;p&gt;s.ioStreams[streamId] = &amp;amp;ioStreamContext{
        userIoConnectCh:  make(chan struct{}),
        agentIoConnectCh: make(chan struct{}),
    }
}
```&lt;/p&gt;
&lt;p&gt;No creator is bound to the stream.&lt;/p&gt;
&lt;p&gt;**Stream attach — `cmd/dashboard/controller/terminal.go` (v2.0.9):**&lt;/p&gt;
&lt;p&gt;```go
// @Router /ws/terminal/{id} [get]
func terminalStream(c *gin.Context) (any, error) {
    streamId := c.Param(&amp;#34;id&amp;#34;)
    if _, err := rpc.NezhaHandlerSingleton.GetStream(streamId); err != nil {…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-q6xx-5vr8-p898</guid>
    </item>
  </channel>
</rss>
