CVE-2025-48927
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.
do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Can a WAF block it? Partly. The vulnerability involves an exposed heap dump endpoint accessible via an HTTP request to the /heapdump URI, which is unusual and not typically accessed by normal users, allowing a WAF to detect and block such requests. A WAF rule can match requests to /heapdump endpoint. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.
What a custom rule would match: requests to /heapdump endpoint
Also consider: patch · custom WAF rule
Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Is CVE-2025-48927 being exploited?
Yes. CVE-2025-48927 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.
How severe is CVE-2025-48927?
CVE-2025-48927 is rated Medium with a CVSS score of 5.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2025-48927?
Not known from our data. No patch reference has been recorded for CVE-2025-48927, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2025-48927 affect?
CVE-2025-48927 affects smarsh:telemessage. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
- affected<= 2025-05-05
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- active
- automatable
- yes
- technical impact
- partial
Assessed by CISA 17 Jul 2025 (SSVC 2.0.3).
timeline
- 28 May 2025Published
- 1 Jul 2025Added to CISA KEV (exploited in the wild) · 33 days later
- 17 Jul 2025CISA SSVC assessment: exploitation active · 16 days later
- 22 Jul 2025CISA remediation due date (US federal agencies) · 5 days later
- 26 Feb 2026CVE record last updated · 220 days (about 7 months) later
- 2 Nov 2026Analysed by vulneraibility.com · 249 days (about 8 months) later
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA KEV catalog: exploitation, date added, due date
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.