{"uuid": "f49f604e-fa96-4736-a5c5-e83f687ed934", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-1795", "type": "seen", "source": "https://t.me/cvedetector/19181", "content": "{\n  \"Source\": \"CVE FEED\",\n  \"Title\": \"CVE-2025-1795 - Microsoft Exchange Comma Encoding Vulnerability\", \n  \"Content\": \"CVE ID : CVE-2025-1795 \nPublished : Feb. 28, 2025, 7:15 p.m. | 1\u00a0hour, 13\u00a0minutes ago \nDescription : During an address list folding when a separating comma ends up on a folded line and that line is to be unicode-encoded then the separator itself is also unicode-encoded. Expected behavior is that the separating comma remains a plan comma. This can result in the address header being misinterpreted by some mail servers. \nSeverity: 0.0 | NA \nVisit the link for more details, such as CVSS details, affected products, timeline, and more...\",\n  \"Detection Date\": \"28 Feb 2025\",\n  \"Type\": \"Vulnerability\"\n}\n\ud83d\udd39 t.me/cvedetector \ud83d\udd39", "creation_timestamp": "2025-02-28T22:03:01.000000Z"}