{"answers":{"affected":"2 open source packages ship an affected version, including org.apache.directory.api:api-ldap-client-api. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-35563 in the wild and no public exploit code.","fix":"Upgrade org.apache.directory.api:api-ldap-client-api to 2.1.8 or later.","what":"CVE-2026-35563 is a high-severity vulnerability in Apache Directory LDAP API, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-35563 and fix it if it is affected.\n\nWhat it is: CVE-2026-35563 is a high-severity vulnerability in Apache Directory LDAP API, published on 1 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-35563 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.apache.directory.api:api-ldap-client-api (Maven): affected from 2.0.0; fixed in 2.1.8\n- org.apache.directory.api:api-ldap-client-api (Maven): affected from 2.0.0; fixed in 2.1.8\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/CVE-2026-35563/ (Markdown: https://insights.sbomify.com/CVE-2026-35563/index.md)","id":"CVE-2026-35563","markdown":"https://insights.sbomify.com/CVE-2026-35563/index.md","name":"CVE-2026-35563","record":{"aliases":["CLEANSTART-2026-EU32419","DEBIAN-CVE-2026-35563","GHSA-85rw-g4f4-jprr","UBUNTU-CVE-2026-35563"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"LDAP client library","requires_auth":"low_privilege","summary":"Attackers can impersonate LDAP servers via MITM due to missing hostname verification, allowing data interception or modification.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"directory_ldap_api","vendor":"apache"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:H/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"It was identified that the LDAP client implementation in version 2.1.7 does not verify if the server certificate matches the intended LDAP \nhostname. While the underlying code validates the certificate chain \nagainst a trusted authority, the absence of endpoint identification \nallows a valid certificate issued for an entirely unrelated host to be \nimproperly accepted. This oversight leaves the connection highly \nvulnerable to server impersonation and complete connection compromise.\n\nThe\n root cause of this vulnerability lies in the incomplete TLS server \nidentity verification within the LDAP client implementation.\n\nThe attacker requires MITM capability on the network to exploit this vulnerability. This attacker must be able to present a certificate trusted by the client's configured trust store.\n\nThe hostname verification has been enforced in the new version of the LDAP API","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Apache Directory LDAP API lacks server certificate verification for LDAP hostnames","id":"CVE-2026-35563","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"Apache Storm UI: Stored Cross-Site Scripting (XSS) via Unsanitized Topology Metadata in Storm UI","id":"CVE-2026-35565"},"packages":[{"ecosystem":"Maven","fixed":["2.1.8"],"introduced":["2.0.0"],"last_affected":[],"package":"org.apache.directory.api:api-ldap-client-api","purl":null,"source":"GHSA-85rw-g4f4-jprr"},{"ecosystem":"Maven","fixed":["2.1.8"],"introduced":["2.0.0"],"last_affected":[],"package":"org.apache.directory.api:api-ldap-client-api","purl":"pkg:maven/org.apache.directory.api/api-ldap-client-api","source":"GHSA-85rw-g4f4-jprr"}],"prev":{"headline":"Allocation of resources without limits in parsing components in Amazon Athena ODBC driver","id":"CVE-2026-35562"},"products":["Apache Directory LDAP API"],"published":"2026-06-01","related":[{"cvss_score":9.8,"headline":"Credential leak in org.apache.directory.api:apache-ldap-api","id":"CVE-2018-1337","kev_date_added":null,"published":"2018-07-10"},{"cvss_score":7.5,"headline":"Exposure of Sensitive Information to an Unauthorized Actor in Apache Directory LDAP API","id":"CVE-2015-3250","kev_date_added":null,"published":"2017-09-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-06-01","vendors":["Apache Software Foundation"]},"summary":"Attackers can impersonate LDAP servers via MITM due to missing hostname verification, allowing data interception or modification.","url":"https://insights.sbomify.com/CVE-2026-35563/"}