{"id":"CVE-2025-37730","aliases":["BIT-logstash-2025-37730","EUVD-2025-13629","GHSA-qrf7-ph5v-mj2v"],"status":"published","title":"Logstash Improper Certificate Validation in TCP output","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","severity":{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","level":"medium","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-10","score":0.0018,"percentile":0.07659,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-295"],"published":"2025-05-06T17:29:07Z","modified":"2026-10-28T02:30:25Z","fixes":[{"ecosystem":"Bitnami","package":"logstash","fixed_in":["8.18.1","9.0.1"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"logstash","ranges":[{"type":"SEMVER","events":[{"introduced":"8.0.0"},{"fixed":"8.18.1"},{"introduced":"9.0.0"},{"fixed":"9.0.1"}]}]}],"products":[{"vendor":"elastic","product":"logstash"}],"references":[{"url":"https://discuss.elastic.co/t/logstash-8-17-6-8-18-1-and-9-0-1-security-update-esa-2025-08/377869","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-37730","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-qrf7-ph5v-mj2v"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/37xxx/CVE-2025-37730.json","tags":["advisory"]},{"url":"https://github.com/elastic/logstash","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2025-37730","title":"Logstash Improper Certificate Validation in TCP output","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","status":"published","published":"2025-05-06T17:29:07.189Z","modified":"2025-05-06T17:51:59.631Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","level":"medium","assessor":"cna"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T14:32:29.607786Z"}],"euvd":[{"id":"EUVD-2025-13629","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","status":"published","published":"2025-05-06T17:29:07Z","modified":"2025-05-06T17:51:59Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","level":"medium"}],"updated_at":"2026-11-02T20:32:53.861279Z"}],"ghsa":[{"id":"GHSA-qrf7-ph5v-mj2v","title":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM)...","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","status":"published","published":"2025-05-06T18:30:40Z","modified":"2025-05-06T18:30:46Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","level":"medium"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T15:02:09.053127Z"}],"nvd":[{"id":"CVE-2025-37730","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","status":"published","published":"2025-05-06T18:15:38.41Z","modified":"2026-06-17T09:15:19.85Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","level":"medium","assessor":"secondary"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T14:11:04.33372Z"}],"osv":[{"id":"CVE-2025-37730","title":"Logstash Improper Certificate Validation in TCP output","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","status":"published","published":"2025-05-06T17:29:07.189Z","modified":"2026-10-28T02:30:25.676705496Z","cvss":[{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","level":"medium"}],"cwes":["CWE-295"],"updated_at":"2026-11-02T15:44:48.342824Z"},{"id":"BIT-logstash-2025-37730","title":"Logstash Improper Certificate Validation in TCP output","description":"Improper certificate validation in Logstash's TCP output could lead to a man-in-the-middle (MitM) attack in “client” mode, as hostname verification in TCP output was not being performed when the ssl_verification_mode =\u003e full was set.","status":"published","published":"2025-05-08T05:42:10.346Z","modified":"2025-05-20T10:02:07.006Z","updated_at":"2026-11-02T15:28:32.645004Z"}]}}