hulumi up to 1.3.1 baseline insufficient logging

Summaryinfo

A vulnerability was found in hulumi up to 1.3.1 and classified as problematic. This vulnerability affects unknown code of the component baseline. Such manipulation leads to insufficient logging. This vulnerability is listed as CVE-2026-82863. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability was found in hulumi up to 1.3.1. It has been rated as problematic. Affected by this issue is an unknown code of the component baseline. The manipulation with an unknown input leads to a insufficient logging vulnerability. Using CWE to declare the problem leads to CWE-778. When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it. Impacted is confidentiality, integrity, and availability. CVE summarizes:

@hulumi/baseline versions before 1.3.2 fail to fully detect CloudTrail selector tampering events, reducing audit logging configuration change coverage. Attackers can modify CloudTrail event selectors without complete detection, potentially evading audit trail monitoring.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-82863 since 08/31/2026. The exploitation is known to be easy. The attack may be launched remotely. Additional levels of successful authentication are necessary for exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1562.002.

Upgrading to version 1.3.2 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• hulumi

Version

• 1.3.0
• 1.3.1

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion