{"id":"GHSA-x5hg-x4gv-j98m","aliases":[],"summary":"OpenSearch has ineffective TLS certificate hostname verification","published_at":"2026-05-07T00:09:18Z","modified_at":"2026-05-07T00:21:11.903034Z","products":[{"slug":"opensearch","name":"OpenSearch","category":"monitoring"}],"rating":{"severity":"low","score":2.2,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N","attack_path":"internet_authenticated","user_interaction":false,"malicious":false},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"priority":3.2,"record_count":1,"vendors":["GitHub"],"details":"### Description\n\nA regression was introduced in OpenSearch 2.18.0 that caused the `plugins.security.ssl.transport.enforce_hostname_verification` setting to be ineffective. When this setting was enabled, OpenSearch did not verify that the hostname in a connecting node's TLS certificate matched the hostname of the connection. This could allow a node with a valid certificate (signed by the cluster's trusted CA) but an incorrect hostname SAN to join the cluster.\n\n### Impact\n\nClusters running affected versions with hostname verification enabled did not receive the expected protection from this setting. A node presenting a certificate signed by the cluster's trusted CA could join the cluster regardless of whether its hostname SAN matched. This regression does not affect certificate validation itself — only the additional hostname verification check.\n\n### Patches\n\nThis issue is fixed in OpenSearch 2.19.4 and 3.3.0.\n\n### Workarounds\n\nUse more restrictive values for `plugins.security.nodes_dn` to limit which certificates are accepted for node-to-node communication.","affected_stack":[{"ecosystem":"Maven","package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.18.0"},{"fixed":"2.19.4.0"}]}],"versions":["2.18.0.0","2.19.0.0","2.19.1.0","2.19.2.0","2.19.3.0"],"fixed":["2.19.4.0"],"provider":"osv","source":"GHSA-x5hg-x4gv-j98m","relation":"self"},{"ecosystem":"Maven","package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.3.0.0"}]}],"versions":["3.0.0.0","3.1.0.0","3.2.0.0"],"fixed":["3.3.0.0"],"provider":"osv","source":"GHSA-x5hg-x4gv-j98m","relation":"self"}],"affected_other":[],"product_status":[],"records":[{"provider":"osv","source_id":"GHSA-x5hg-x4gv-j98m","relation":"self","url":"https://osv.dev/vulnerability/GHSA-x5hg-x4gv-j98m","license":"CC-BY-4.0","published_at":"2026-05-07T00:09:18Z","modified_at":"2026-05-07T00:21:11.903034Z","summary":"OpenSearch has ineffective TLS certificate hostname verification","details":"### Description\n\nA regression was introduced in OpenSearch 2.18.0 that caused the `plugins.security.ssl.transport.enforce_hostname_verification` setting to be ineffective. When this setting was enabled, OpenSearch did not verify that the hostname in a connecting node's TLS certificate matched the hostname of the connection. This could allow a node with a valid certificate (signed by the cluster's trusted CA) but an incorrect hostname SAN to join the cluster.\n\n### Impact\n\nClusters running affected versions with hostname verification enabled did not receive the expected protection from this setting. A node presenting a certificate signed by the cluster's trusted CA could join the cluster regardless of whether its hostname SAN matched. This regression does not affect certificate validation itself — only the additional hostname verification check.\n\n### Patches\n\nThis issue is fixed in OpenSearch 2.19.4 and 3.3.0.\n\n### Workarounds\n\nUse more restrictive values for `plugins.security.nodes_dn` to limit which certificates are accepted for node-to-node communication.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:N","source":"GHSA-x5hg-x4gv-j98m"}],"affected":[{"ecosystem":"Maven","package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"2.18.0"},{"fixed":"2.19.4.0"}]}],"versions":["2.18.0.0","2.19.0.0","2.19.1.0","2.19.2.0","2.19.3.0"],"fixed":["2.19.4.0"],"provider":"osv","source":"GHSA-x5hg-x4gv-j98m","relation":"self"},{"ecosystem":"Maven","package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.3.0.0"}]}],"versions":["3.0.0.0","3.1.0.0","3.2.0.0"],"fixed":["3.3.0.0"],"provider":"osv","source":"GHSA-x5hg-x4gv-j98m","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/opensearch-project/security/security/advisories/GHSA-x5hg-x4gv-j98m"},{"type":"PACKAGE","url":"https://github.com/opensearch-project/security"}]}],"references":[{"type":"WEB","url":"https://github.com/opensearch-project/security/security/advisories/GHSA-x5hg-x4gv-j98m"},{"type":"PACKAGE","url":"https://github.com/opensearch-project/security"}],"sources":[{"provider":"osv","source_id":"GHSA-x5hg-x4gv-j98m","url":"https://osv.dev/vulnerability/GHSA-x5hg-x4gv-j98m","license":"CC-BY-4.0","modified_at":"2026-05-07T00:21:11.903034Z","relation":"self"}]}
