Secuno
ENNL
Book demo

CVE-2026-93765

9.1 CRITICAL
  1. Published18 Sept 2026

Description

Mongoid contains an unsafe reflection weakness in the document persistence layer of its object-document mapping code. Input whose keys are passed through from an unauthenticated party by an embedding application can cause unintended internal method invocation instead of the intended array field update. This may result in unintended removal of stored records and in the embedding application becoming unresponsive.

CVSS 3.1 breakdown

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

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-937629.8
Mongoid contains an unsafe reflection weakness in the query path used for embedded…
CVE-2026-768258.4
RestrictedPython is a tool that helps define a subset of the Python language for…
CVE-2026-867928.8
Apache Airflow Apache Kafka provider versions 1.15.0 before 2.0.0 resolve dotted-path…
CVE-2026-623799.8
Open Access Management (OpenAM) is an access management solution. Prior to 16.1.2, the…
CVE-2026-799878.8
A remote, authenticated, non-admin Craft CMS Control Panel user with only the accessCp…
CVE-2026-418719.8
Missing Authorization, Use of Externally-Controlled Input to Select Classes or Code…

Frequently asked

Is CVE-2026-93765 being actively exploited?

CVE-2026-93765 is not in the CISA KEV catalog.

How severe is CVE-2026-93765?

CVE-2026-93765 has a CVSS 3.1 base score of 9.1, rated critical.

How do I fix CVE-2026-93765?

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-93765 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.