Bump org.mongodb:mongodb-driver-sync from 5.10.0 to 5.11.0

[dependabot]

Bumps org.mongodb:mongodb-driver-sync from 5.10.0 to 5.11.0.

Release notes

Sourced from org.mongodb:mongodb-driver-sync's releases.

Java Driver 5.11.0 (August 28, 2026)

What's Changed

• Java 6173 CSFLE/QE Support for HTTP Proxies by @​strogiyotec in mongodb/mongo-java-driver#2043

CSFLE/QE Http proxies notes

• The driver always negotiates TLS with the KMS host itself, using the SSLContext configured for the KMS provider. Implementations must not negotiate TLS with the KMS host; doing so would let an intermediary read the key material in transit.
• An implementation may use TLS for its own connection to the intermediary, in which case it returns an SSLSocket and the driver layers the KMS host's TLS session on top of it.
• Ownership of the returned socket passes to the driver, which closes it when the KMS request completes. A socket that is never returned must be closed by the implementation.
• Applicable only to the synchronous driver. The reactive streams driver rejects(RuntimeException) a configured callback.

Code example

Code example uses only the JDK API , so no HTTP client dependency is required. If you use your own HTTP client, it must return the tunnelled socket without negotiating TLS with the KMS host

First define the callback

private static final String PROXY_HOST = "proxy.example.com";
private static final int PROXY_PORT = 8080;
private static final int TIMEOUT_MILLIS = 10_000;
// Routes every KMS request through an HTTP proxy using the HTTP CONNECT method

// refer to the docs https://www.rfc-editor.org/info/rfc9110/#section-9.3.6

KmsConnectCallback proxyCallback = context -> {

Socket socket = new Socket();

try {

// 1. Connect to the proxy, not to the KMS host.

socket.connect(new InetSocketAddress(PROXY_HOST, PROXY_PORT), TIMEOUT_MILLIS);

socket.setSoTimeout(TIMEOUT_MILLIS);
    // 2. Ask the proxy to open a tunnel to the KMS host the driver wants to reach. Only the
    //    driver knows which host that is, so always take it from the context rather than
    //    hard-coding it.
    String target = context.getHost() + ":" + context.getPort();
    String connectRequest = "CONNECT " + target + " HTTP/1.1\r\n"
            + "Host: " + target + "\r\n"
            // If the proxy requires authentication, add the appropriate header, for example:
            // + "Proxy-Authorization: Basic " + base64("user:password") + "\r\n"
            + "\r\n";
    socket.getOutputStream().write(connectRequest.getBytes(StandardCharsets.US_ASCII));
// 3. Check the proxy accepted the tunnel before handing the socket back.
checkProxyAcceptedTunnel(socket.getInputStream());

} catch (IOException | RuntimeException e) {

// The driver never received this socket, so it cannot close it for you.

socket.close();

throw e;


</tr></table>

... (truncated)

Commits

• c96aad1 Version: bump 5.11.0
• 027d4cc CSFLE/QE Support for HTTP Proxies (#2043)
• 9af9be1 Version: bump 5.11.0-SNAPSHOT
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

Qodana for JVM

2 new problems were found

Inspection name	Severity	Problems
Unstable API Usage	🔶 Warning	2

View the detailed Qodana report

To be able to view the detailed Qodana report, you can either:

• Register at Qodana Cloud and configure the action
• Use GitHub Code Scanning with Qodana
• Host Qodana report at GitHub Pages
• Inspect and use qodana.sarif.json (see the Qodana SARIF format for details)

To get *.log files or any other Qodana artifacts, run the action with upload-result option set to true,
so that the action will upload the files as the job artifacts:

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2026.2.0
        with:
          upload-result: true

Contact Qodana team

Contact us at qodana-support@jetbrains.com

• Or via our issue tracker: https://jb.gg/qodana-issue
• Or share your feedback: https://jb.gg/qodana-discussions