<?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 13:57:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-159992</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-159992</link>
      <description>EUVD-2026-159992</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-159992</guid>
    </item>
    <item>
      <title>fkie_cve-2024-31206</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-31206</link>
      <description>&lt;p&gt;dectalk-tts is a Node package to interact with the aeiou Dectalk web API. In `dectalk-tts@1.0.0`, network requests to the third-party API are sent over HTTP, which is unencrypted. Unencrypted traffic can be easily intercepted and modified by attackers. Anyone who uses the package could be the victim of a man-in-the-middle (MITM) attack. The network request was upgraded to HTTPS in version `1.0.1`. There are no workarounds, but some precautions include not sending any sensitive information and carefully verifying the API response before saving it.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;dectalk-tts is a Node package to interact with the aeiou Dectalk web API. In `dectalk-tts@1.0.0`, network requests to the third-party API are sent over HTTP, which is unencrypted. Unencrypted traffic can be easily intercepted and modified by attackers. Anyone who uses the package could be the victim of a man-in-the-middle (MITM) attack. The network request was upgraded to HTTPS in version `1.0.1`. There are no workarounds, but some precautions include not sending any sensitive information and carefully verifying the API response before saving it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-31206</guid>
    </item>
    <item>
      <title>GHSA-6cf6-8hvr-r68w — dectalk-tts Uses Unencrypted HTTP Request</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6cf6-8hvr-r68w</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: dectalk-tts&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In `dectalk-tts@1.0.0`, network requests to the third-party API are sent over HTTP, which is unencrypted. Unencrypted traffic can be easily intercepted and modified by attackers. Anyone who uses the package could be the victim of a [man-in-the-middle (MITM)](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) attack.&lt;/p&gt;
&lt;p&gt;&amp;lt;ins&amp;gt;Theft&amp;lt;/ins&amp;gt;&lt;/p&gt;
&lt;p&gt;Because `dectalk-tts` is a text-to-speech package, user requests are expected to only contain natural language. The package [README](https://github.com/JstnMcBrd/dectalk-tts/blob/main/README.md) warns that user input is sent to a third-party API, so users should not send sensitive information regardless.&lt;/p&gt;
&lt;p&gt;But if users ignore the warnings and send sensitive information anyway, that information could be stolen by attackers.&lt;/p&gt;
&lt;p&gt;&amp;lt;ins&amp;gt;Modification&amp;lt;/ins&amp;gt;&lt;/p&gt;
&lt;p&gt;Attackers could manipulate requests to the API. However, the worst a modified request could do is return an incorrect audio file or bad request rejection.&lt;/p&gt;
&lt;p&gt;Attackers could also manipulate responses from the API, returning malicious output to the user. Output is expected to be a wav-encoded buffer, which users will likely save to a file. This could be a dangerous entrypoint to the user&amp;#39;s filesystem.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The network request was upgraded to HTTPS in version `1.0.1`. No other changes were made, so updating is risk-free.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There are no workarounds, but here are some precautions:&lt;/p&gt;
&lt;p&gt;- Do not send any sensitive information.&lt;/p&gt;
&lt;p&gt;- Carefully verify the API response before…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: dectalk-tts&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;In `dectalk-tts@1.0.0`, network requests to the third-party API are sent over HTTP, which is unencrypted. Unencrypted traffic can be easily intercepted and modified by attackers. Anyone who uses the package could be the victim of a [man-in-the-middle (MITM)](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) attack.&lt;/p&gt;
&lt;p&gt;&amp;lt;ins&amp;gt;Theft&amp;lt;/ins&amp;gt;&lt;/p&gt;
&lt;p&gt;Because `dectalk-tts` is a text-to-speech package, user requests are expected to only contain natural language. The package [README](https://github.com/JstnMcBrd/dectalk-tts/blob/main/README.md) warns that user input is sent to a third-party API, so users should not send sensitive information regardless.&lt;/p&gt;
&lt;p&gt;But if users ignore the warnings and send sensitive information anyway, that information could be stolen by attackers.&lt;/p&gt;
&lt;p&gt;&amp;lt;ins&amp;gt;Modification&amp;lt;/ins&amp;gt;&lt;/p&gt;
&lt;p&gt;Attackers could manipulate requests to the API. However, the worst a modified request could do is return an incorrect audio file or bad request rejection.&lt;/p&gt;
&lt;p&gt;Attackers could also manipulate responses from the API, returning malicious output to the user. Output is expected to be a wav-encoded buffer, which users will likely save to a file. This could be a dangerous entrypoint to the user&amp;#39;s filesystem.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The network request was upgraded to HTTPS in version `1.0.1`. No other changes were made, so updating is risk-free.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;There are no workarounds, but here are some precautions:&lt;/p&gt;
&lt;p&gt;- Do not send any sensitive information.&lt;/p&gt;
&lt;p&gt;- Carefully verify the API response before…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6cf6-8hvr-r68w</guid>
    </item>
    <item>
      <title>gsd-2024-31206</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-31206</link>
      <description>gsd-2024-31206</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-31206</guid>
    </item>
  </channel>
</rss>
