CVE-2025-27920
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.
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 attack uses ../ sequences in parameters of HTTP requests to traverse directories, which is unusual and can be detected by a WAF rule matching such sequences. A WAF rule can match ../ sequences in parameters. No tracked WAF vendor has published a rule for this CVE yet, so you would write it yourself.
What a custom rule would match: ../ sequences in parameters
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-27920 being exploited?
Yes. CVE-2025-27920 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-27920?
CVE-2025-27920 is rated High with a CVSS score of 7.2. 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-27920?
Yes. A fix has been recorded for CVE-2025-27920. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2025-27920 affect?
CVE-2025-27920 affects srimax:output_messenger. 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< 2.0.63
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 26 Aug 2025 (SSVC 2.0.3).
timeline
- 5 May 2025Published
- 19 May 2025Added to CISA KEV (exploited in the wild) · 13 days later
- 9 Jun 2025CISA remediation due date (US federal agencies) · 21 days later
- 26 Aug 2025CISA SSVC assessment: exploitation active · 79 days (about 3 months) later
- 21 Oct 2025CVE record last updated · 56 days later
- 2 Nov 2026Analysed by vulneraibility.com · 377 days (about 1 year) later
- Advisorymicrosoft.com /en-us/security/blog/2025/05/12/marbled-dust-leverages-zero-day-in-output-messen
- Linksrimax.com /products-2/output-messenger/
- Linkoutputmessenger.com /cve-2025-27920/
- Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-27920
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.