How severe is CVE-2025-27920?

CVE-2025-27920 has a CVSS score of 7.2/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-27920?

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

How do I fix CVE-2025-27920?

No fixed version has been published for CVE-2025-27920 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-27920 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-27920 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-27920?

CVE-2025-27920 has an EPSS (Exploit Prediction Scoring System) score of 50.1%, placing it in the 98th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

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

Yes. CVE-2025-27920 (Srimax Output Messenger Directory Traversal Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-05-19. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-06-09. 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-27920?

CVE-2025-27920 is classified as CWE-24 (CWE-24). 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-27920?

CVE-2025-27920 affects srimax output messenger. Check the affected-products list on this page against your deployed version to confirm exposure.

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

CVE-2025-27920 was published on May 5, 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.

CVE-2025-27920: Output Messenger CWE-24 (High 7.2)

EPSS Exploitation Probability

via FIRST.org ↗

50.1%probability of exploitation in next 30 days

High Risk98th 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

Output Messenger before 2.0.63 was vulnerable to a directory traversal attack through improper file path handling. By using ../ sequences in parameters, attackers could access sensitive files outside the intended directory, potentially leading to configuration leakage or arbitrary file access.

Affected Products

1 product · 1 configurations

Application

output messengersrimax

< 2.0.63

range

Frequently Asked Questions

Output Messenger before 2.0.63 was vulnerable to a directory traversal attack through improper file path handling. By using ../ sequences in parameters, attackers could access sensitive files outside the intended directory, potentially leading to configuration leakage or arbitrary file access.

O3 Security · Impact-Aware SCA

Is CVE-2025-27920 in your stack?

O3 detects CVE-2025-27920 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