CVE-2025-48925: The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing

Q: How do I fix CVE-2025-48925?

telemessage: upgrade to newer than 2025-05-05. Exact commands for each OS are on this page.

Q: Is CVE-2025-48925 being exploited?

CVE-2025-48925 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-48925 affect?

CVE-2025-48925 affects telemessage. Severity is medium (CVSS 4.3). The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential.

Q: How urgent is CVE-2025-48925?

Priority 20/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2025-48925 is a medium-severity flaw (CVSS 4.3) affecting telemessage. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 80%)
CISA exploited list	No
Weakness	CWE-836
Published	2025-05-28
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: smarsh

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-05-28 17:15 UTCPublished CVE record published
2026-06-17 09:30 UTCUpdated Record last modified

smarsh telemessage UPGRADE

Affected: <= 2025-05-05

Fixed in: newer than 2025-05-05

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy telemessage || rpm -q telemessage || telemessage --version

2. UPGRADE to newer than 2025-05-05 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade telemessage

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade telemessage

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-48925?

telemessage: upgrade to newer than 2025-05-05. Exact commands for each OS are on this page.

Is CVE-2025-48925 being exploited?

CVE-2025-48925 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-48925 affect?

CVE-2025-48925 affects telemessage. Severity is medium (CVSS 4.3). The TeleMessage service through 2025-05-05 relies on the client side (e.g., the TM SGNL app) to do MD5 hashing, and then accepts the hash as the authentication credential.

How urgent is CVE-2025-48925?

Priority 20/100. No elevated risk signals yet.

Related CVEs

CVE-2025-48931 LOW 3.2 UPGRADE The TeleMessage service through 2025-05-05 relies on MD5 for password hashing, which opens up various attack p
CVE-2025-48930 LOW 2.8 UPGRADE The TeleMessage service through 2025-05-05 stores certain cleartext information in memory, even though memory
CVE-2025-48929 MEDIUM 4.0 UPGRADE The TeleMessage service through 2025-05-05 implements authentication through a long-lived credential (e.g., no
CVE-2025-48928 MEDIUM 4.0 EXPLOITED MITIGATE TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere Vulnerability
CVE-2025-48927 MEDIUM 5.3 EXPLOITED MITIGATE TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Vulnerability

References

← Back to latest CVEs