{"answers":{"affected":"4 open source packages ship an affected version, including org.opensearch.plugin:opensearch-security.","exploited":"There is no known exploitation of GHSA-x5hg-x4gv-j98m in the wild and no public exploit code.","fix":"Upgrade org.opensearch.plugin:opensearch-security to a fixed version for your release line: 2.19.4.0 or 3.3.0.0.","what":"GHSA-x5hg-x4gv-j98m is a vulnerability in org.opensearch.plugin:opensearch-security, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-x5hg-x4gv-j98m and fix it if it is affected.\n\nWhat it is: GHSA-x5hg-x4gv-j98m is a vulnerability in org.opensearch.plugin:opensearch-security, published on 7 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-x5hg-x4gv-j98m in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.opensearch.plugin:opensearch-security (Maven): affected from 2.18.0; fixed in 2.19.4.0\n- org.opensearch.plugin:opensearch-security (Maven): affected from 2.18.0; fixed in 2.19.4.0\n- org.opensearch.plugin:opensearch-security (Maven): affected from 3.0.0; fixed in 3.3.0.0\n- org.opensearch.plugin:opensearch-security (Maven): affected from 3.0.0; fixed in 3.3.0.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-x5hg-x4gv-j98m/ (Markdown: https://insights.sbomify.com/GHSA-x5hg-x4gv-j98m/index.md)","id":"GHSA-x5hg-x4gv-j98m","markdown":"https://insights.sbomify.com/GHSA-x5hg-x4gv-j98m/index.md","name":"GHSA-x5hg-x4gv-j98m","record":{"aliases":[],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenSearch server","requires_auth":"none","summary":"OpenSearch fails to verify TLS hostnames, allowing malicious nodes with valid CA-signed certificates to join clusters and access data.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### 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.","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"OpenSearch has ineffective TLS certificate hostname verification","id":"GHSA-x5hg-x4gv-j98m","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":4,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["2.19.4.0"],"introduced":["2.18.0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":null,"source":"GHSA-x5hg-x4gv-j98m"},{"ecosystem":"Maven","fixed":["2.19.4.0"],"introduced":["2.18.0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","source":"GHSA-x5hg-x4gv-j98m"},{"ecosystem":"Maven","fixed":["3.3.0.0"],"introduced":["3.0.0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":null,"source":"GHSA-x5hg-x4gv-j98m"},{"ecosystem":"Maven","fixed":["3.3.0.0"],"introduced":["3.0.0"],"last_affected":[],"package":"org.opensearch.plugin:opensearch-security","purl":"pkg:maven/org.opensearch.plugin/opensearch-security","source":"GHSA-x5hg-x4gv-j98m"}],"products":null,"published":"2026-05-07","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"OpenSearch fails to verify TLS hostnames, allowing malicious nodes with valid CA-signed certificates to join clusters and access data.","url":"https://insights.sbomify.com/GHSA-x5hg-x4gv-j98m/"}