CVE-2026-92945

Description

A flaw was found in vm2. This vulnerability allows an attacker to bypass the module allowlist, a security feature designed to restrict access to certain software modules. The flaw occurs due to an incorrect string comparison method used in the isPathAllowedForModule function. By exploiting this, an attacker can load and interact with modules that should be inaccessible, potentially leading to information disclosure or the execution of unintended code.

Statement

Moderate impact. This vulnerability in the vm2 component, present in Red Hat Ansible Automation Platform and Red Hat Developer Hub, allows for a module allowlist bypass. Exploitation requires an attacker to perform relative module imports from an already allowlisted package when transitive loading is disabled, leading to access to restricted packages.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Common Vulnerability Scoring System (CVSS) Score Details

Info alert:Important note

CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).

The following CVSS metrics and score provided are preliminary and subject to review.

CVSS v3 Score Breakdown

Red HatNVDcve.org
Base Score4.2N/A4.2
Attack VectorNetworkN/ANetwork
Attack ComplexityHighN/AHigh
Privileges RequiredLowN/ALow
User InteractionNoneN/ANone
ScopeUnchangedN/AUnchanged
ConfidentialityLowN/ALow
Integrity ImpactLowN/ALow
Availability ImpactNoneN/ANone

Vector

Red Hat: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

cve.org: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Understanding the Weakness (CWE)

Other

Technical Impact: Varies by Context

This can lead to incorrect results and resultant weaknesses. For example, the code might inadvertently compare references to objects, instead of the relevant contents of those objects, causing two "equal" objects to be considered unequal.

Frequently Asked Questions

Want to get errata notifications? Sign up here.