# CVE-2025-47729: TeleMessage TM SGNL Hidden Functionality

> The TeleMessage archiving backend stores cleartext copies of user messages, exposing sensitive data despite claims of end-to-end encryption.

- **Severity:** Low 1.9 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 12 May 2025 (CISA KEV)
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 May 2025
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-h5qv-qcjq-wcff

## What is CVE-2025-47729?

CVE-2025-47729 is a low-severity vulnerability in TeleMessage archiving backend, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The TeleMessage archiving backend through 2025-05-05 holds cleartext copies of messages from TM SGNL (aka Archive Signal) app users, which is different functionality than described in the TeleMessage "End-to-End encryption from the mobile phone through to the corporate archive" documentation, as exploited in the wild in May 2025.

Weakness: CWE-912 (Hidden Functionality)

## Which versions are affected by CVE-2025-47729?

It affects 1 product.


Products: Telemessage Text Message Archiver.

## How do I fix CVE-2025-47729?

No fix has been published for CVE-2025-47729 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Jun 2025.

## Is CVE-2025-47729 being exploited?

Yes. Attackers have exploited CVE-2025-47729 in the wild since at least 12 May 2025.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-47729 and fix it if it is affected.

What it is: CVE-2025-47729 is a low-severity vulnerability in TeleMessage archiving backend, published on 8 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-47729 in the wild since at least 12 May 2025.

Affected product: TeleMessage archiving backend. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-47729/ (Markdown: https://insights.sbomify.com/CVE-2025-47729/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-47729
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-47729
- OSV: https://osv.dev/vulnerability/CVE-2025-47729

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-47729/
Summaries are generated and may contain mistakes; the official description above is the record.