How severe is CVE-2025-48927?

CVE-2025-48927 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-48927?

Affected package information for CVE-2025-48927 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2025-48927?

No fixed version has been published for CVE-2025-48927 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2025-48927 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48927 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48927?

CVE-2025-48927 has an EPSS (Exploit Prediction Scoring System) score of 9.5%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2025-48927 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2025-48927 (TeleMessage TM SGNL Initialization of a Resource with an Insecure Default Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-07-01. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-07-22. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2025-48927?

CVE-2025-48927 is classified as CWE-1188 (CWE-1188). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Which products and versions are affected by CVE-2025-48927?

CVE-2025-48927 affects smarsh telemessage. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2025-48927 published, and has it been updated?

CVE-2025-48927 was published on May 28, 2025 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2025-07-01 — agencies required to remediate by 2025-07-22

CVE-2025-48927

MEDIUM

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.

Published

May 28, 2025

Updated

Nov 5, 2025

Affected

0 pkgs

Patched

None yet

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

9.5%probability of exploitation in next 30 days

Lower Risk93th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

1 product · 1 configurations

Application

telemessagesmarsh

all

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2025-48927 in your stack?

O3 detects CVE-2025-48927 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works