<?xml version="1.0" encoding="UTF-8"?><?xml-stylesheet type="text/xsl" href="../assets/feed.xsl"?><rss version="2.0"><channel><title>PatchTheCVE: gotenna</title><link>https://patchthecve.com/</link><description>CVEs with upgrade or downgrade fix steps</description><item><title>CVE-2025-32890: An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12</title><link>https://patchthecve.com/cve/CVE-2025-32890.html</link><guid>https://patchthecve.com/cve/CVE-2025-32890.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>MEDIUM 5.3: An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12. It uses a custom implementation of encryption without any additional integrity checking mechanisms. This leaves messages malleable to an attacker that can access the message.</description></item><item><title>CVE-2025-32889: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5</title><link>https://patchthecve.com/cve/CVE-2025-32889.html</link><guid>https://patchthecve.com/cve/CVE-2025-32889.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>HIGH 7.3: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. The verification token used for sending SMS through a goTenna server is hardcoded in the app.</description></item><item><title>CVE-2025-32888: An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12</title><link>https://patchthecve.com/cve/CVE-2025-32888.html</link><guid>https://patchthecve.com/cve/CVE-2025-32888.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>HIGH 7.3: An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12. The verification token used for sending SMS through a goTenna server is hardcoded in the app.</description></item><item><title>CVE-2025-32887: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5</title><link>https://patchthecve.com/cve/CVE-2025-32887.html</link><guid>https://patchthecve.com/cve/CVE-2025-32887.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>HIGH 7.1: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. A command channel includes the next hop. which can be intercepted and used to break frequency hopping.</description></item><item><title>CVE-2025-32886: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5</title><link>https://patchthecve.com/cve/CVE-2025-32886.html</link><guid>https://patchthecve.com/cve/CVE-2025-32886.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>MEDIUM 4.0: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. All packets sent over RF are also sent over UART with USB Shell, allowing someone with local access to gain information about the protocol and intercept sensitive data.</description></item><item><title>CVE-2025-32885: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5</title><link>https://patchthecve.com/cve/CVE-2025-32885.html</link><guid>https://patchthecve.com/cve/CVE-2025-32885.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>MEDIUM 6.5: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. The app there makes it possible to inject any custom message (into existing v1 networks) with any GID and Callsign via a software defined radio. This can be exploited if the device is being used in an unencrypted envir</description></item><item><title>CVE-2025-32884: An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12</title><link>https://patchthecve.com/cve/CVE-2025-32884.html</link><guid>https://patchthecve.com/cve/CVE-2025-32884.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>MEDIUM 4.3: An issue was discovered on goTenna Mesh devices with app 5.5.3 and firmware 1.1.12. By default, a GID is the user&#x27;s phone number unless they specifically opt out. A phone number is very sensitive information because it can be tied back to individuals. The app does not encrypt the GID in messages.</description></item><item><title>CVE-2025-32882: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5</title><link>https://patchthecve.com/cve/CVE-2025-32882.html</link><guid>https://patchthecve.com/cve/CVE-2025-32882.html</guid><pubDate>Wed, 17 Jun 2026 09:12:45 +0000</pubDate><description>MEDIUM 5.3: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. The app uses a custom implementation of encryption without any additional integrity checking mechanisms. This leaves messages malleable to an attacker that can access the message.</description></item><item><title>CVE-2025-32881: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5</title><link>https://patchthecve.com/cve/CVE-2025-32881.html</link><guid>https://patchthecve.com/cve/CVE-2025-32881.html</guid><pubDate>Wed, 17 Jun 2026 09:12:44 +0000</pubDate><description>MEDIUM 4.3: An issue was discovered on goTenna v1 devices with app 5.5.3 and firmware 0.25.5. By default, the GID is the user&#x27;s phone number unless they specifically opt out. A phone number is very sensitive information because it can be tied back to individuals. The app does not encrypt the GID in messages.</description></item><item><title>CVE-2024-45838: The goTenna Pro ATAK Plugin does not encrypt callsigns in messages</title><link>https://patchthecve.com/cve/CVE-2024-45838.html</link><guid>https://patchthecve.com/cve/CVE-2024-45838.html</guid><pubDate>Wed, 17 Jun 2026 07:54:54 +0000</pubDate><description>MEDIUM 4.3: The goTenna Pro ATAK Plugin does not encrypt callsigns in messages. It 
is advised to not use sensitive information in callsigns when using this
 and previous versions of the plugin. Update to current plugin version 
which uses AES-256 encryption for callsigns in encrypted operation</description></item><item><title>CVE-2024-45723: The goTenna Pro ATAK Plugin does not use SecureRandom when generating 
passwords for sharing cryptographic key</title><link>https://patchthecve.com/cve/CVE-2024-45723.html</link><guid>https://patchthecve.com/cve/CVE-2024-45723.html</guid><pubDate>Wed, 17 Jun 2026 07:54:42 +0000</pubDate><description>MEDIUM 6.5: The goTenna Pro ATAK Plugin 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</description></item><item><title>CVE-2024-45374: The goTenna Pro ATAK plugin uses a weak password for sharing encryption 
keys via the key broadcast method</title><link>https://patchthecve.com/cve/CVE-2024-45374.html</link><guid>https://patchthecve.com/cve/CVE-2024-45374.html</guid><pubDate>Wed, 17 Jun 2026 07:54:06 +0000</pubDate><description>MEDIUM 5.3: The goTenna Pro ATAK plugin 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 v</description></item><item><title>CVE-2024-43814: The goTenna Pro ATAK Plugin&#x27;s default settings are to share Automatic 
Position, Location, and Information (PL</title><link>https://patchthecve.com/cve/CVE-2024-43814.html</link><guid>https://patchthecve.com/cve/CVE-2024-43814.html</guid><pubDate>Wed, 17 Jun 2026 07:51:45 +0000</pubDate><description>MEDIUM 4.3: The goTenna Pro ATAK Plugin&#x27;s default settings are to share Automatic 
Position, Location, and Information (PLI) updates every 60 seconds once 
the plugin is active and goTenna is connected. Users that are unaware of
 their settings and have not activated encryption before a mission may 
accidentall</description></item><item><title>CVE-2024-43108: The goTenna Pro ATAK Plugin uses AES CTR type encryption for short, 
encrypted messages without any additional</title><link>https://patchthecve.com/cve/CVE-2024-43108.html</link><guid>https://patchthecve.com/cve/CVE-2024-43108.html</guid><pubDate>Wed, 17 Jun 2026 07:50:27 +0000</pubDate><description>MEDIUM 5.3: The goTenna Pro ATAK Plugin 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 advised to continue to use encryption in the plugin and 
update to the curr</description></item><item><title>CVE-2024-41931: The goTenna Pro ATAK Plugin encryption key name is always sent 
unencrypted when the key is sent over RF throu</title><link>https://patchthecve.com/cve/CVE-2024-41931.html</link><guid>https://patchthecve.com/cve/CVE-2024-41931.html</guid><pubDate>Wed, 17 Jun 2026 07:48:28 +0000</pubDate><description>MEDIUM 4.3: The goTenna Pro ATAK Plugin encryption key name is always sent 
unencrypted when the key is sent over RF through a broadcast message. It
 is advised to share the encryption key via local QR for higher security
 operations.</description></item><item><title>CVE-2024-41722: In the goTenna Pro ATAK Plugin there is a vulnerability that makes it 
possible to inject any custom message w</title><link>https://patchthecve.com/cve/CVE-2024-41722.html</link><guid>https://patchthecve.com/cve/CVE-2024-41722.html</guid><pubDate>Wed, 17 Jun 2026 07:48:07 +0000</pubDate><description>MEDIUM 6.5: In the goTenna Pro ATAK Plugin there is a vulnerability that makes it 
possible to inject any custom message with any GID and Callsign using a 
software defined radio in existing goTenna mesh networks. This 
vulnerability can be exploited if the device is being used in an 
unencrypted environment or</description></item></channel></rss>