Secuno
ENNL
Book demo

CVE-2026-81522

8.1 HIGHEPSS 0.27%
  1. Published27 Aug 2026

Description

A weakness in the MongoDB C++ Driver's handling of caller-supplied namespace identifiers allows special characters embedded in those identifiers. An application that builds a namespace identifier from untrusted input without validating it may therefore have its operation directed at a different target than intended. This can result in limited unauthorized read and write access to data belonging to another logical tenant of the affected application.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityNone
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-136849.8
An improper encoding or escaping of output vulnerability in SCGI in Synology…
CVE-2026-541828.1
backpack/crud provides Create, Read, Update & Delete (CRUD) functions for Backpack, a…
CVE-2026-546949.6
SkillTree is a micro-learning gamification platform. Prior to version 4.4.2, two…
CVE-2026-618248.2
Defuddle cleans up HTML pages. Prior to 0.19.1, site extractors interpolate…
CVE-2026-613989.1
Improper Encoding or Escaping of Output vulnerability in Apache CloudStack's UI while…
CVE-2025-516779.1
An issue was discovered in openRISC OR1200 commit 83ac6b. An output mismatch between…

Frequently asked

Is CVE-2026-81522 being actively exploited?

CVE-2026-81522 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.27%.

How severe is CVE-2026-81522?

CVE-2026-81522 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.27% probability of exploitation.

How do I fix CVE-2026-81522?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-81522 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.