CVE-2025-27920: Srimax Output Messenger Directory Traversal Vulnerability
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
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.
Description quoted from the CVE record (assigned by mitre, published 2025-05-05).
Weakness: CWE-24 Path Traversal: ‘../filedir’
How it can be exploited
Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality low, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: partial.
- On CISA KEV since
- 2025-05-19
- US federal deadline
- 2025-06-09
- Ransomware use
- Not known
Public exploit evidence (Exploit Observer)
Also known as: BDU:2025-06724, CNNVD-202505-651, EUVD-2025-13464, GHSA-66q6-24vw-2g98
Exploit Observer has no public exploit code that names this CVE or one of its aliases.
Research and write-ups (2)
- Research or write-up: https://outputmessenger.com/cve-2025-27920
- Research or write-up: https://www.outputmessenger.com/cve-2025-27920
Vulnerability databases and vendor advisories (5)
Catalogue entries, not exploit evidence.
- Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2025-13464
- Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-66q6-24vw-2g98
- Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2025-27920
- Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-27920
- Vulnerability database or vendor advisory: https://www.cnnvd.org.cn/home/globalSearch?keyword=CNNVD-202505-651
69 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.
VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.
Live scores
- EPSS
- 0.019
some chance of attack soon - VEDAS
- 0.692
some exploit evidence - On CISA KEV
- Yes, since 2025-05-19
- Detection rule
- None yet
Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish. The vertical line is the day CISA added it to its exploited list.
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Srimax Output Messenger | before 2.0.63 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
Exploit Observer also maps it to: srimax output_messenger, srimax_software_technology output_messenger.
How to fix it
Fixed versions stated in the CVE record: 2.0.63.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vendor guidance:
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Exploits and technical analysis
- https://www.microsoft.com/en-us/security/blog/2025/05/12/marbled-dust-leverages-zero-day-in-output-messenger-for-regional-espionage/ (third-party-advisory)
Government sources
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-27920 (government-resource)
Other references
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.