<?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>Thu, 15 Oct 2026 18:19:32 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-234358</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-234358</link>
      <description>EUVD-2026-234358</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-234358</guid>
    </item>
    <item>
      <title>fkie_cve-2022-24721</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-24721</link>
      <description>&lt;p&gt;CometD is a scalable comet implementation for web messaging. In any version prior to 5.0.11, 6.0.6, and 7.0.6, internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels. By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other users&amp;#39; (possibly sensitive) data. By publishing to those channels, a remote user may be able to create/modify/delete other user&amp;#39;s data and modify the cluster structure. A fix is available in versions 5.0.11, 6.0.6, and 7.0.6. As a workaround, install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CometD is a scalable comet implementation for web messaging. In any version prior to 5.0.11, 6.0.6, and 7.0.6, internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels. By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other users&amp;#39; (possibly sensitive) data. By publishing to those channels, a remote user may be able to create/modify/delete other user&amp;#39;s data and modify the cluster structure. A fix is available in versions 5.0.11, 6.0.6, and 7.0.6. As a workaround, install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-24721</guid>
    </item>
    <item>
      <title>GHSA-rjmq-6v55-4rjv — Improper Authorization in org.cometd.oort</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rjmq-6v55-4rjv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.cometd.java:cometd-java-oort&lt;/p&gt;
&lt;p&gt;### Impact
Internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels.
By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other user&amp;#39;s (possibly sensitive) data.
By publishing to those channels, a remote user may be able to create/modify/delete other user&amp;#39;s data and modify the cluster structure.
The issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5.&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.&lt;/p&gt;
&lt;p&gt;### Workarounds
The workaround is to install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.
This workaround could be implemented in any affected version.&lt;/p&gt;
&lt;p&gt;### References
cometd/cometd#1146&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Email us at [security@webtide.com](mailto:security@webtide.com)&lt;/p&gt;
&lt;p&gt;### Credits
https://www.redteam-pentesting.de/&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.cometd.java:cometd-java-oort&lt;/p&gt;
&lt;p&gt;### Impact
Internal usage of Oort and Seti channels is improperly authorized, so any remote user could subscribe and publish to those channels.
By subscribing to those channels, a remote user may be able to watch cluster-internal traffic that contains other user&amp;#39;s (possibly sensitive) data.
By publishing to those channels, a remote user may be able to create/modify/delete other user&amp;#39;s data and modify the cluster structure.
The issue impacts any version up to 5.0.10, 6.0.5 and 7.0.5.&lt;/p&gt;
&lt;p&gt;### Patches
The issue has been fixed in 5.0.11, 6.0.6 and 7.0.6.&lt;/p&gt;
&lt;p&gt;### Workarounds
The workaround is to install a custom `SecurityPolicy` that forbids subscription and publishing to remote, non-Oort, sessions on Oort and Seti channels.
This workaround could be implemented in any affected version.&lt;/p&gt;
&lt;p&gt;### References
cometd/cometd#1146&lt;/p&gt;
&lt;p&gt;### For more information
If you have any questions or comments about this advisory:
* Email us at [security@webtide.com](mailto:security@webtide.com)&lt;/p&gt;
&lt;p&gt;### Credits
https://www.redteam-pentesting.de/&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rjmq-6v55-4rjv</guid>
    </item>
    <item>
      <title>gsd-2022-24721</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-24721</link>
      <description>gsd-2022-24721</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-24721</guid>
    </item>
  </channel>
</rss>
