libmongocrypt - Debian Package Tracker

general

source: libmongocrypt (main)
version: 1.21.1-1
maintainer: Mongo C Driver Team (DMD)
uploaders: Roberto C. Sanchez [DMD] – Kevin Albertson [DMD]
arch: any
std-ver: 4.7.4
VCS: Git (Browse, QA)

versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]

[pool directory]

o-o-stable: 1.1.0-1
oldstable: 1.7.2-1
stable: 1.13.2-1
testing: 1.21.0-1
unstable: 1.21.1-1

versioned links

1.1.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.7.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.13.2-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.21.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
1.21.1-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

libmongocrypt-dev
libmongocrypt0

action needed

1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:

CVE-2026-114655: libmongocrypt builds requests to external key management services (AWS, Azure and GCP) by inserting values from key vault documents, KMS provider configuration and KMS responses into request lines, headers and signed request bodies without validating or encoding them for each context. A user with write access to the key vault collection can alter the structure of these requests, including adding members to request bodies and token claims that the library then signs with the application's credentials. This may result in key management operations being performed with parameters the application did not intend.

Created: 2026-10-23 Last update: 2026-10-27 00:30

7 security issues in bookworm high

There are 7 open security issues in bookworm.

4 important issues:

CVE-2026-106429: An integer underflow in the KMS endpoint-parsing logic of MongoDB libmongocrypt can cause an allocation failure that terminates the application process. This can occur when an authenticated user modifies a key document in the key vault collection, or when an application accepts a KMS endpoint containing a colon after its path or query during key creation. The issue does not access memory outside its allocated bounds.
CVE-2026-106433: Improper state management in MongoDB libmongocrypt can cause provider-specific data to be treated as an incompatible type when cleaning up a key document containing duplicate masterKey fields. An authenticated actor who can modify key vault documents, or a server that returns such a key document, can cause invalid memory access and invalid frees in the client process. This can terminate the application or corrupt process memory.
CVE-2026-106434: The explicit decryption component of MongoDB libmongocrypt can return an unrecognized encrypted payload unchanged instead of returning a decryption error. An actor who can modify stored encrypted fields, such as a database writer, server, or network intermediary, can cause an affected application to process the supplied bytes as decrypted plaintext.
CVE-2026-114655: libmongocrypt builds requests to external key management services (AWS, Azure and GCP) by inserting values from key vault documents, KMS provider configuration and KMS responses into request lines, headers and signed request bodies without validating or encoding them for each context. A user with write access to the key vault collection can alter the structure of these requests, including adding members to request bodies and token claims that the library then signs with the application's credentials. This may result in key management operations being performed with parameters the application did not intend.

3 issues postponed or untriaged:

CVE-2026-81523: (postponed; to be fixed through a stable update) A missing input-validation issue in MongoDB libmongocrypt's automatic-encryption context setup allows a caller-supplied database identifier to be accepted without sanitization. The resulting impact is limited to incorrect schema selection, which may lead to limited disclosure or modification of information handled by the application.
CVE-2026-84962: (postponed; to be fixed through a stable update) An unauthorized user with key vault write access may cause an authorized client to issue arbitrary authenticated Google Cloud KMS API calls under the authorized user's identity, escalating database-level access into cloud key control and defeating client-side encryption.
CVE-2026-84971: (postponed; to be fixed through a stable update) Improper handling of an unexpected value size in the decryption path of a client-side encryption library can cause a failed internal check that terminates the process using the library. A party able to place a suitably formed encrypted value where an application will decrypt it, or able to control the responses the application receives, may cause that application to stop running.

Created: 2026-10-09 Last update: 2026-10-27 00:30

Failed to analyze the VCS repository. Please troubleshoot and fix the issue. high

vcswatch reports that there is an error with this package's VCS, or the debian/changelog file inside it. Please check the error shown below and try to fix it. You might have to update the VCS URL in the debian/control file to point to the correct repository.

debian/changelog not found in any branch (tried master, debian, debian/master, debian/sid, debian/latest, debian/experimental, master)

Created: 2024-06-27 Last update: 2026-10-27 00:02

Problems while searching for a new upstream version high

uscan had problems while searching for a new upstream version:

In watchfile debian/watch, reading webpage
  https://github.com/mongodb/libmongocrypt/tags failed: 500 Header line too long (limit is 8192)

Created: 2026-10-24 Last update: 2026-10-26 23:30

1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:

CVE-2026-81523: A missing input-validation issue in MongoDB libmongocrypt's automatic-encryption context setup allows a caller-supplied database identifier to be accepted without sanitization. The resulting impact is limited to incorrect schema selection, which may lead to limited disclosure or modification of information handled by the application.

Created: 2026-08-28 Last update: 2026-08-30 08:30

6 low-priority security issues in trixie low

There are 6 open security issues in trixie.

6 issues left for the package maintainer to handle:

CVE-2026-84962: (needs triaging) An unauthorized user with key vault write access may cause an authorized client to issue arbitrary authenticated Google Cloud KMS API calls under the authorized user's identity, escalating database-level access into cloud key control and defeating client-side encryption.
CVE-2026-84971: (needs triaging) Improper handling of an unexpected value size in the decryption path of a client-side encryption library can cause a failed internal check that terminates the process using the library. A party able to place a suitably formed encrypted value where an application will decrypt it, or able to control the responses the application receives, may cause that application to stop running.
CVE-2026-106429: (needs triaging) An integer underflow in the KMS endpoint-parsing logic of MongoDB libmongocrypt can cause an allocation failure that terminates the application process. This can occur when an authenticated user modifies a key document in the key vault collection, or when an application accepts a KMS endpoint containing a colon after its path or query during key creation. The issue does not access memory outside its allocated bounds.
CVE-2026-106433: (needs triaging) Improper state management in MongoDB libmongocrypt can cause provider-specific data to be treated as an incompatible type when cleaning up a key document containing duplicate masterKey fields. An authenticated actor who can modify key vault documents, or a server that returns such a key document, can cause invalid memory access and invalid frees in the client process. This can terminate the application or corrupt process memory.
CVE-2026-106434: (needs triaging) The explicit decryption component of MongoDB libmongocrypt can return an unrecognized encrypted payload unchanged instead of returning a decryption error. An actor who can modify stored encrypted fields, such as a database writer, server, or network intermediary, can cause an affected application to process the supplied bytes as decrypted plaintext.
CVE-2026-114655: (needs triaging) libmongocrypt builds requests to external key management services (AWS, Azure and GCP) by inserting values from key vault documents, KMS provider configuration and KMS responses into request lines, headers and signed request bodies without validating or encoding them for each context. A user with write access to the key vault collection can alter the structure of these requests, including adding members to request bodies and token claims that the library then signs with the application's credentials. This may result in key management operations being performed with parameters the application did not intend.

You can find information about how to handle these issues in the security team's documentation.

Created: 2026-09-04 Last update: 2026-10-27 00:30

testing migrations

This package will soon be part of the auto-openssl transition. You might want to ensure that your package is ready for it. You can probably find supplementary information in the debian-release archives or in the corresponding release.debian.org bug.
excuses:
- Migration status for libmongocrypt (1.21.0-1 to 1.21.1-1): Waiting for test results or another package, or too young (no action required now - check later)
- Issues preventing migration:
- ∙ ∙ Too young, only 4 of 5 days old
- Additional info (not blocking):
- ∙ ∙ Piuparts tested OK - https://piuparts.debian.org/sid/source/libm/libmongocrypt.html
- ∙ ∙ Reproduced on amd64 - info
- ∙ ∙ Reproduced on arm64 - info
- ∙ ∙ Reproduced on armhf - info
- ∙ ∙ Reproduced on i386 - info
- Not considered

news

[rss feed]

[2026-10-22] Accepted libmongocrypt 1.21.1-1 (source) into unstable (Roberto C. Sanchez)
[2026-10-21] libmongocrypt 1.21.0-1 MIGRATED to testing (Debian testing watch)
[2026-10-15] Accepted libmongocrypt 1.21.0-1 (source) into unstable (Roberto C. Sanchez)
[2026-10-14] libmongocrypt 1.20.5-1 MIGRATED to testing (Debian testing watch)
[2026-10-08] Accepted libmongocrypt 1.20.5-1 (source) into unstable (Roberto C. Sanchez)
[2026-09-09] libmongocrypt 1.20.4-1 MIGRATED to testing (Debian testing watch)
[2026-09-04] Accepted libmongocrypt 1.13.2-1+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Roberto C. Sanchez)
[2026-09-03] Accepted libmongocrypt 1.20.4-1 (source) into unstable (Roberto C. Sanchez)
[2026-09-02] libmongocrypt 1.20.3-1 MIGRATED to testing (Debian testing watch)
[2026-08-28] libmongocrypt 1.20.2-1 MIGRATED to testing (Debian testing watch)
[2026-08-27] Accepted libmongocrypt 1.20.3-1 (source) into unstable (Roberto C. Sanchez)
[2026-08-18] Accepted libmongocrypt 1.20.2-1 (source) into unstable (Roberto C. Sanchez)
[2026-07-23] libmongocrypt 1.20.1-1 MIGRATED to testing (Debian testing watch)
[2026-07-17] Accepted libmongocrypt 1.20.1-1 (source) into unstable (Roberto C. Sanchez)
[2026-07-07] libmongocrypt 1.20.0-1 MIGRATED to testing (Debian testing watch)
[2026-06-30] Accepted libmongocrypt 1.20.0-1 (source) into unstable (Roberto C. Sanchez)
[2026-06-24] libmongocrypt 1.19.1-1 MIGRATED to testing (Debian testing watch)
[2026-06-18] Accepted libmongocrypt 1.19.1-1 (source) into unstable (Roberto C. Sanchez)
[2026-06-12] libmongocrypt 1.19.0-1 MIGRATED to testing (Debian testing watch)
[2026-06-06] Accepted libmongocrypt 1.19.0-1 (source) into unstable (Roberto C. Sanchez)
[2026-05-29] libmongocrypt 1.18.2-1 MIGRATED to testing (Debian testing watch)
[2026-05-23] Accepted libmongocrypt 1.18.2-1 (source) into unstable (Roberto C. Sanchez)
[2026-05-20] libmongocrypt 1.18.1-1 MIGRATED to testing (Debian testing watch)
[2026-05-14] Accepted libmongocrypt 1.18.1-1 (source) into unstable (Roberto C. Sanchez)
[2026-04-15] libmongocrypt 1.17.3-1 MIGRATED to testing (Debian testing watch)
[2026-04-09] Accepted libmongocrypt 1.17.3-1 (source) into unstable (Roberto C. Sanchez)
[2025-12-01] libmongocrypt 1.17.0-1 MIGRATED to testing (Debian testing watch)
[2025-11-25] Accepted libmongocrypt 1.17.0-1 (source) into unstable (Roberto C. Sanchez)
[2025-10-07] libmongocrypt 1.16.0-1 MIGRATED to testing (Debian testing watch)
[2025-10-02] Accepted libmongocrypt 1.16.0-1 (source) into unstable (Roberto C. Sanchez)

bugs [bug history graph]

all: 0

links

homepage
lintian
buildd: logs, reproducibility, cross
popcon
browse source code
other distros
security tracker

ubuntu

[Information about Ubuntu for Debian Developers]

version: 1.20.2-1