CVE-2026-41709:详情

CVE-2026-41709

2.7
/
低危
2026-07-30
14h16 +00:00
A09-Security Log./Monit. Failures
Network
2026-10-29
17h29 +00:00
指定 CVE 通知
随时了解指定 CVE 的变更。
管理通知

CVE 描述

VMware ESX contains an insufficient logging vulnerability. A malicious administrator could exploit this issue to perform certain operations without them being logged.

CVE 信息

相关弱点

CWE-ID 弱点名称 来源
CWE-778 Insufficient Logging
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.

指标

指标 评分 严重程度 CVSS 向量 来源
V3.1 2.7 LOW CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Network

The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

High

The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable component allowing access to component-wide settings and files.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

None

There is no loss of confidentiality within the impacted component.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

Low

Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

security@vmware.com

CISA KEV(已知被利用漏洞)

漏洞名称 : Broadcom VMWare ESX Insufficient Logging Vulnerability

必要措施 : Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

已被用于勒索软件攻击活动 : Unknown

添加日期 : 2026-10-28 00h00 +00:00

截止日期 : 2026-11-11 00h00 +00:00

重要信息
根据 CISA KEV(已知被利用漏洞目录),此 CVE 被认定为存在漏洞且构成活跃威胁。CISA 已将该漏洞列为正被网络犯罪分子积极利用,并强调必须立即采取措施修复。请优先更新和修复此 CVE,以保护系统免遭潜在网络攻击。

相关产品

配置 0

Vmware>>Esxi >> Version 从(含) 9.0.0 至(不含) 9.0.2.0100

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Esxi >> Version 8.0

Vmware>>Cloud_foundation >> Version 从(含) 5.0 至(不含) 5.2.4

Vmware>>Telco_cloud_platform >> Version 从(含) 5.0 至(不含) 5.2

Vmware>>Vsphere_foundation >> Version -

参考资料