CVE-2026-129934: Credential exposure via unmasked option values in Go driver connection string parse errors
The MongoDB Go driver's connection string parser includes the raw, undecoded value of a query option in the error it returns when that value contains invalid percent encodings. When the option holds a secret, such as a TLS key file password or an AWS session token, the secret appears in plain text in the error. A party with low-privileged read access to wherever the application records or displays that error may learn the secret.
Affected Software
Event History
Frequently Asked Questions
Who is exposed to this issue?
Applications using the MongoDB Go driver are exposed when a connection string contains a secret-bearing query option with invalid percent encoding and the resulting parse error is recorded or displayed. Low-privileged users who can read those errors may be able to obtain the secret.
What must happen for a secret to be disclosed?
An invalid percent encoding must be present in the raw value of a connection-string query option, and that option must contain a secret such as a TLS key file password or AWS session token. The parser must return an error, and an unauthorized party must be able to read the location where the application logs or displays it.
How can teams reduce exposure before a fix is applied?
Avoid placing secrets in connection-string query option values that could be emitted in parsing errors, and ensure those values are correctly percent-encoded. Restrict read access to application logs and error displays that may contain connection-string parsing errors.
How can you determine whether secrets may already have been exposed?
Review application logs and error-reporting locations for MongoDB Go driver connection-string parse errors related to invalid percent encodings. Check whether affected raw option values contained secrets, and treat any such values visible to low-privileged readers as potentially disclosed.