LiveActive security incident?Get immediate response
CVE Record

CVE-2025-47729: The TeleMessage archiving backend through 2025-05-05 holds cleartext copies of messages from TM SGNL (aka A...

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.

LowCVSS 1.9Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

TeleMessage’s archiving backend reportedly kept cleartext copies of messages from TM SGNL, also called Archive Signal, despite documentation describing end-to-end encryption to the corporate archive. The issue is listed in CISA KEV and the CVE says it was exploited in May 2025. Business risk is highest for organizations that used TeleMessage for regulated or sensitive communications archiving.

Executive priority

Prioritize as a vendor-risk and sensitive-communications exposure issue, not as a conventional network takeover flaw. KEV status and reported exploitation justify urgent inventory, legal or compliance coordination, and vendor confirmation.

Technical view

CVE-2025-47729 covers TeleMessage archiving backend behavior through 2025-05-05: cleartext message copies existed in the archive backend. The CVE maps this to CWE-912 and gives CVSS 3.1 score 1.9, but KEV status raises operational urgency. The source bundle does not name a vendor patch, fixed version, or detailed remediation.

Likely exposure

Exposure likely applies to organizations using TeleMessage’s archiving backend with TM SGNL or Archive Signal before or through 2025-05-05. The affected-version data is sparse and default status is unknown, so inventory confirmation is essential.

Exploitation context

Active exploitation is supported by the CVE description and CISA KEV listing. Public references indicate TeleMessage was investigating reports and that operations stopped after a hack report. No source bundle evidence provides exploit mechanics, attacker identity, or a complete victim list.

Researcher notes

The CVSS score is low because the vector is constrained, but the real-world impact depends on message sensitivity and backend access. Evidence is incomplete on affected versions, fix availability, and mitigations. Avoid assuming Signal itself is affected; sources describe TeleMessage’s archiving backend behavior.

Mitigation direction

  • Identify any TeleMessage archiving backend or TM SGNL use in the organization.
  • Check TeleMessage and CISA guidance for official remediation or service status.
  • Preserve relevant archive, access, and audit logs for incident review.
  • Treat affected archived message content as potentially exposed.
  • Review retention, encryption, and vendor assurance requirements for regulated messaging.

Validation and detection

  • Confirm whether TeleMessage services were active through 2025-05-05.
  • Determine whether TM SGNL or Archive Signal users existed in your environment.
  • Review vendor contracts and architecture documents for archive backend use.
  • Check logs for unusual archive access around May 2025.
  • Validate whether archived message content was stored or accessible in cleartext.
Prepared
Confidence
medium
Sources
6

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-912: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2025-47729 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
1.9 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
5Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
1.9CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N0.51.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

1.9Low
CVSS 3.1 vector shape for CVE-2025-47729Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TeleMessagearchiving backend0unknown
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-912 · source CWE mapping

Hidden Functionality

Hidden Functionality represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.