TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Vulnerability
CVE-2025-48927
How serious is it
- Severity: not rated yet.
- Exploit prediction (EPSS): 11% chance of exploitation in the next 30 days, higher than 96% of all vulnerabilities.
- Confirmed exploited in the wild (CISA KEV).
- No public exploit in Exploit-DB.
Is your app affected by CVE-2025-48927?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- TeleMessage TM SGNL
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
TeleMessage TM SGNL contains an initialization of a resource with an insecure default vulnerability. This vulnerability relies on how the Spring Boot Actuator is configured with an exposed heap dump endpoint at a /heapdump URI.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- No references listed.
Merged from CISA KEV, FIRST EPSS. Last updated 24 Oct 2026. All vulnerabilities · RSS · JSON