-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Major - P3
-
Affects Version/s: 8.2.4, 8.0.18, 7.0.29
-
Component/s: None
-
None
-
Server Security
-
ALL
-
v8.2, v8.0, v7.0
-
-
Server Security 2026-01-30, Server Security 2026-02-13
-
(copied to CRM)
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Summary
Recently reduced pre-auth message limits cause mongocryptd to reject large commands.
Background
A driver test started failing on server 8.0.18 and 7.0.29. Example task: first execution passed with server 8.0.17, the second failed with 8.0.18, with mongocryptd logging:
{"t":{"$date":"2026-01-28T11:20:08.629-05:00"},"s":"I", "c":"EXECUTOR", "id":22988, "ctx":"conn2","msg":"Error receiving request from client. Ending connection from remote","attr":{"error":{"code":17,"codeName":"ProtocolError","errmsg":"recv(): message msgLen 2111419 is invalid. Min 16 Max: 16384"},"remote":"127.0.0.1:56962","connectionId":2}}
The test sends bulk write operations to mongocryptd for client-side encryption. I expect recent changes reduced the maximum acceptable pre-auth size. But I expect pre-auth limits are not applicable to mongocryptd. Drivers do not authenticate to mongocryptd, since mongocryptd is expected to run alongside client applications. And large commands are expected to be sent to mongocryptd to encrypt.
Workarounds
As a short-term workaround: start mongocryptd with a larger preAuthMaximumMessageSizeBytes (set via setParameter).
Affected versions
- 8.2.4, 8.2.5 (
SERVER-116490) - 8.0.18, 8.0.19 (
SERVER-116495) - 7.0.29, 7.0.30 (
SERVER-116496)
- causes
-
CSHARP-5862 Skip large encryption tests on latest variants
-
- Closed
-
- is related to
-
SERVER-116490 [v8.2.4] Adjust the maximum buffer size for ingress requests
-
- Closed
-
-
SERVER-116495 [v8.0.18] Adjust the maximum buffer size for ingress requests
-
- Closed
-
-
SERVER-116496 [v7.0.29] Adjust the maximum buffer size for ingress requests
-
- Closed
-
- related to
-
SERVER-118435 Improve test coverage for mongocryptd
-
- Open
-