Threats / TeleMessage / CVE-2025-48927
CVE-2025-48927
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
TeleMessage TM SGNL vulnerability
TeleMessage TM SGNL exposes a heap dump endpoint via insecurely configured Spring Boot Actuator, allowing unauthenticated access to sensitive memory contents.
Verdict
Today item — known-exploited.
An exposed /heapdump endpoint permits attackers to extract heap memory dumps containing credentials, session tokens, and application secrets without authentication, enabling lateral movement and privilege escalation.
CISA KEV Yes · 2025-07-015EPSS 0.08659 (verify live)6CVSS 5.33CISA SSVC Exploitation: active · Automatable: yes · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
7 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-07-01).
Probability (EPSS)
EPSS 0.08659 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 5.3 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N) · Affected: TeleMessage, TM SGNL. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 3.1, set at disclosure.
Weakness (CWE)
Mapped to CWE-1188 Insecure Default Initialization — weakness family: Authorization / access control.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: partialCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 34 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I discover the exposed /heapdump endpoint is accessible without credentials.
Business
Attackers gain direct access to application memory containing sensitive data.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I download the heap dump and extract plaintext credentials and API tokens from memory.
Business
Compromised credentials enable unauthorized access to user accounts and backend systems.
3
Lateral reach — past segmentation narrative 3
Attacker
I use extracted tokens to impersonate legitimate users and access protected resources.
Business
User data confidentiality is breached; attackers gain persistent access to the platform.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05