Threats / TeleMessage / CVE-2025-48928
CVE-2025-48928
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-09-19
TeleMessage TM SGNL vulnerability
TeleMessage TM SGNL exposes sensitive heap memory including passwords through accessible core dump files, allowing unauthorized access to credentials transmitted over HTTP.
Verdict
Today item — known-exploited.
An unauthenticated attacker can retrieve exposed core dump files from the JSP application containing heap memory with plaintext passwords and other sensitive data, enabling credential compromise and unauthorized system access.
CISA KEV Yes · 2025-07-015EPSS 0.00553 (verify live)6CVSS 43CISA SSVC Exploitation: active · Automatable: no · Impact: partial4
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
5 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.00553 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 4 (CVSS:3.1/AV:L/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-528 CWE-528.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: no · 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.
WeaknessCWE-528 · CWE-528
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 identify and access exposed core dump files from the TM SGNL JSP application.
Business
Sensitive credentials and authentication data become accessible to unauthorized parties.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I extract plaintext passwords and session information from the exposed heap memory dumps.
Business
User accounts and administrative credentials are compromised, enabling lateral movement.
3
Lateral reach — past segmentation narrative 3
Attacker
I use recovered credentials to authenticate to TM SGNL or connected systems.
Business
Attackers gain persistent access to messaging infrastructure and user communications.
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
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by mitreCNA
Credited with finding itNo finder is named in the public CVE record or the scanned vendor advisory — attribution scoped to the sources checked.
Found an error? Propose a correction.
A correction is a cited counter-claim — it must cite a source,
gets reviewed by a second human, and is never auto-applied. See the
correction convention and our identity
npub1j7gt9ky7sfcrjn8jjee6693dkzvk4rahs0fk2suu7968dfns62zs3mqm3y.