<?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>Fri, 09 Oct 2026 14:46:18 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-5555</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-5555</link>
      <description>EUVD-2026-5555</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-5555</guid>
    </item>
    <item>
      <title>fkie_cve-2024-34712</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-34712</link>
      <description>&lt;p&gt;Oceanic is a NodeJS library for interfacing with Discord. Prior to version 1.10.4, input to functions such as `Client.rest.channels.removeBan` is not url-encoded, resulting in specially crafted input such as `../../../channels/{id}` being normalized into the url `/api/v10/channels/{id}`, and deleting a channel rather than removing a ban. Version 1.10.4 fixes this issue. Some workarounds are available. One may sanitize user input, ensuring strings are valid for the purpose they are being used for. One may also encode input with `encodeURIComponent` before providing it to the library.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Oceanic is a NodeJS library for interfacing with Discord. Prior to version 1.10.4, input to functions such as `Client.rest.channels.removeBan` is not url-encoded, resulting in specially crafted input such as `../../../channels/{id}` being normalized into the url `/api/v10/channels/{id}`, and deleting a channel rather than removing a ban. Version 1.10.4 fixes this issue. Some workarounds are available. One may sanitize user input, ensuring strings are valid for the purpose they are being used for. One may also encode input with `encodeURIComponent` before providing it to the library.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-34712</guid>
    </item>
    <item>
      <title>GHSA-5h5v-hw44-f6gg — Oceanic allows unsanitized user input to lead to path traversal in URLs</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-5h5v-hw44-f6gg</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: oceanic.js&lt;/p&gt;
&lt;p&gt;### Impact
Input to functions such as `Client.rest.channels.removeBan` is not url-encoded, resulting in specially crafted input such as `../../../channels/{id}` being normalized into the url `/api/v10/channels/{id}`, and deleting a channel rather than removing a ban.&lt;/p&gt;
&lt;p&gt;### Workarounds
* Sanitizing user input, ensuring strings are valid for the purpose they are being used for.
* Encoding input with `encodeURIComponent` before providing it to the library.&lt;/p&gt;
&lt;p&gt;### References
OceanicJS/Oceanic@8bf8ee8373b8c565fbdbf70a609aba4fbc1a1ffe&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: oceanic.js&lt;/p&gt;
&lt;p&gt;### Impact
Input to functions such as `Client.rest.channels.removeBan` is not url-encoded, resulting in specially crafted input such as `../../../channels/{id}` being normalized into the url `/api/v10/channels/{id}`, and deleting a channel rather than removing a ban.&lt;/p&gt;
&lt;p&gt;### Workarounds
* Sanitizing user input, ensuring strings are valid for the purpose they are being used for.
* Encoding input with `encodeURIComponent` before providing it to the library.&lt;/p&gt;
&lt;p&gt;### References
OceanicJS/Oceanic@8bf8ee8373b8c565fbdbf70a609aba4fbc1a1ffe&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-5h5v-hw44-f6gg</guid>
    </item>
  </channel>
</rss>
