<?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 08:29:59 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-359427</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-359427</link>
      <description>EUVD-2026-359427</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-359427</guid>
    </item>
    <item>
      <title>fkie_cve-2026-48106</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48106</link>
      <description>&lt;p&gt;Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise&amp;#39;s cluster replication receiver at `internal/cluster/replication/receiver.go` validates only the wire-format envelope (length, opcode) of inbound messages. The `MsgReplicateSync` payload itself is accepted without any application-layer authentication — no HMAC, no signature, no per-message nonce. The replication stream is protected at the transport layer by TLS / mTLS, but there is no protection against application-layer message tampering or replay once a peer is on the cluster network. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit replication logs for unexpected `MsgReplicateSync` traffic, and/or disable cluster mode until the fix is available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Arc is an open, SQL-native time-series database for telemetry. Prior to version 26.06.1, Arc Enterprise&amp;#39;s cluster replication receiver at `internal/cluster/replication/receiver.go` validates only the wire-format envelope (length, opcode) of inbound messages. The `MsgReplicateSync` payload itself is accepted without any application-layer authentication — no HMAC, no signature, no per-message nonce. The replication stream is protected at the transport layer by TLS / mTLS, but there is no protection against application-layer message tampering or replay once a peer is on the cluster network. This is fixed in 2026.06.1. Some workarounds are available. Restrict cluster network access to known-trusted peers via strict firewall rules, audit replication logs for unexpected `MsgReplicateSync` traffic, and/or disable cluster mode until the fix is available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-48106</guid>
    </item>
  </channel>
</rss>
