# CVE-2025-48927: TeleMessage TM SGNL Initialization of a Resource with an Insecure Default

> Attackers can access exposed Spring Boot Actuator heap dumps to retrieve sensitive memory data from the TeleMessage service.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 1 Jul 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2025
- **Updated:** 26 Feb 2026
- **Also known as:** GHSA-vg5q-95gg-rqfg

## What is CVE-2025-48927?

CVE-2025-48927 is a medium-severity vulnerability in TeleMessage service, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TeleMessage service through 2025-05-05 configures Spring Boot Actuator with an exposed heap dump endpoint at a /heapdump URI, as exploited in the wild in May 2025.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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

It affects 1 product.


Products: Smarsh Telemessage.

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

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

## Is CVE-2025-48927 being exploited?

Yes. Attackers have exploited CVE-2025-48927 in the wild since at least 1 Jul 2025.

## Other vulnerabilities in TeleMessage service

- [CVE-2025-48928](https://insights.sbomify.com/CVE-2025-48928/): TeleMessage TM SGNL Exposure of Core Dump File to an Unauthorized Control Sphere (medium 4.0, exploited in the wild)
- [CVE-2025-47730](https://insights.sbomify.com/CVE-2025-47730/): Hardcoded credentials in archiving backend (medium 4.8)
- [CVE-2025-48925](https://insights.sbomify.com/CVE-2025-48925/): Weak cryptography in service (medium 4.3)
- [CVE-2025-48926](https://insights.sbomify.com/CVE-2025-48926/): Information disclosure in service (medium 4.3)
- [CVE-2025-48929](https://insights.sbomify.com/CVE-2025-48929/): Auth bypass in service (medium 4.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48927 is a medium-severity vulnerability in TeleMessage service, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-48927 in the wild since at least 1 Jul 2025.

Affected product: TeleMessage service. 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-48927/ (Markdown: https://insights.sbomify.com/CVE-2025-48927/index.md)
```

## Sources

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

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