<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-03T15:34:30.997787+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-196243</id>
    <title>EUVD-2026-196243</title>
    <updated>2026-10-03T15:34:31.060721+00:00</updated>
    <content>EUVD-2026-196243</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-196243"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2024-47126</id>
    <title>fkie_cve-2024-47126</title>
    <updated>2026-10-03T15:34:31.060770+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The goTenna Pro App does not use SecureRandom when generating passwords 
for sharing cryptographic keys. The random function in use makes it 
easier for attackers to brute force this password if the broadcasted 
encryption key is captured over RF. This only applies to the optional 
broadcast of an encryption key, so it is advised to share the key with 
local QR code for higher security operations.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2024-47126"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-7vrc-hc62-3f49</id>
    <title>GHSA-7vrc-hc62-3f49</title>
    <updated>2026-10-03T15:34:31.060820+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The goTenna Pro series does not use SecureRandom when generating its cryptographic keys. The random function in use is not suitable for cryptographic use.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-7vrc-hc62-3f49"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/icsa-24-270-04</id>
    <title>ICSA-24-270-04 — goTenna Pro X and Pro X2 (Update A)</title>
    <updated>2026-10-03T15:34:31.060848+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The goTenna Pro App uses a weak password for sharing encryption keys via the key broadcast method. If the broadcasted encryption key is captured over RF, and password is cracked via brute force attack, it is possible to decrypt it and use it to decrypt all future and past messages sent via encrypted broadcast with that particular key. This only applies when the key is broadcasted over RF. This is an optional feature, so it is recommended to use local QR encryption key sharing for additional security on this and previous versions. In the goTenna Pro App, the encryption keys are stored along with a static IV on the End User Device (EUD). This allows for complete decryption of keys stored on the EUD if physically compromised. This allows an attacker to decrypt all encrypted broadcast communications based on encryption keys stored on the EUD. This requires access to and control of the EUD, so it is recommended to use strong access control measures and layered encryption on the EUD for more secure operation. The goTenna Pro App uses AES CTR type encryption for short, encrypted messages without any additional integrity checking mechanisms. This leaves messages malleable to an attacker that can access the message. It is recommended to continue to use encryption in the app and update to the current release for more secure operations. The goTenna Pro App does not encrypt callsigns in messages. It is recommended to not use sensitive information in callsigns when using this and previou…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/icsa-24-270-04"/>
  </entry>
</feed>
