High [CVE-2026-81521] Write redirection via unvalidated database name in Client.BulkWrite
This high-severity Red Hat Linux advisory covers CVE-2026-81521 affecting OpenShift Pipelines, Pen Drive Powered by Red Hat Lightspeed, Red Hat 3scale API Management Platform 2.
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.
Summary
The MongoDB Go Driver's client-level bulk write operation may accept a caller-supplied database name containing a reserved separator character without escaping it before the name is used to build the target namespace for the operation.
An application that passes untrusted input as a database name could therefore have the write directed at a database and collection other than the ones it intended. Only the Client.
BulkWrite API is affected. BulkWrite` operation does not properly validate database names, allowing a specially crafted name with reserved characters to redirect write operations.
This vulnerability could enable an attacker to modify or corrupt data in unintended databases and collections. Red Hat severity: Important — CVSS 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).
Weakness: CWE-791. Affected Red Hat products: OpenShift Pipelines; Pen Drive Powered by Red Hat Lightspeed; Red Hat 3scale API Management Platform 2; Red Hat Edge Manager 1; Red Hat OpenShift Dev Spaces; Red Hat OpenShift GitOps; Red Hat Trusted Artifact Signer.
Will not fix / out of support: Red Hat 3scale API Management Platform 2. Red Hat does not currently list a fixing RHSA for this CVE.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source
Mitigation
The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.
Official advisory · medium-confidence parse· fetched 1 hour ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.