Issues fixed in MarkLogic Server 10.0-7.4
- Last Updated: April 6, 2026
- 1 minute read
- MarkLogic Server
- Documentation
Released: Aug 2, 2023
The following issues have been addressed in this release:
| Platform | Component | Bug ID | Details |
|---|---|---|---|
| all | BUG-60412 | MarkLogic connections to AWS KMS and Azure KeyVault fail due to the use of TLSv1.0 AWS and Azure have discontinued the use of TLS 1.0 and 1.1 and now require TLS 1.2. MarkLogic does not yet support TLS 1.2 for communication with an external KMS so once AWS and Azure require TLS 1.2, MarkLogic will no longer be able to communicate with AWS KMS or Azure Key Vault. |
|
| all | BUG-60460 | MLCMD uses log4j 2.14.1, which has a critical secure vulnerability MLCMD uses log4j 2.14.1, which has a critical security vulnerability (see https://nvd.nist.gov/vuln/detail/CVE-2021-44228). Log4j 2.16 addresses the vulnerability. |
|
| all | BUG-60459 | op.fromSearch() and op.fromSearchDocs() security constraints Optic queries using either op.fromSearch()/op:from-search() or op.fromSearchDocs()/op:from-search-docs() operators may return more documents than theoretically accessible. |