Quick answers
- Is CVE-2026-82863 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-82863 being exploited in the wild.
- How severe is CVE-2026-82863?
- Medium severity, with a CVSS score of 4, published 31 August 2026.
- Which products and versions are affected?
- @hulumi/baseline (npm) SEMVER:introduced=0,fixed=1.3.2.
- Is there a fix for CVE-2026-82863?
- Yes. @hulumi/baseline (npm): upgrade to 1.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-82863 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-82863?
- Check whether you run @hulumi/baseline (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- @hulumi/baseline (npm): upgrade to 1.3.2 or later
npm install @hulumi/baseline@1.3.2
Technical details
The vulnerability is an insufficient logging issue (CWE-778) where @hulumi/baseline versions before 1.3.2 failed to detect all CloudTrail event-selector tampering evidence. This reduced security coverage for changes to critical audit logging configurations. The root cause lies in incomplete detection logic that missed certain tampering patterns. An attacker with permissions to modify CloudTrail configuration could exploit this to disable or modify event selectors while evading detection. The vulnerability requires network access to AWS CloudTrail APIs and appropriate AWS credentials. The fix was applied in version 1.3.2, which expanded detection coverage and added regression tests.
Affected products
- @hulumi baseline before 1.3.2
Identifiers
- CVE-2026-82863
- GHSA-gfp8-mp24-5vxg
Timeline
- 2026-05-21: disclosed
- 2026-05-21: patched: Version 1.3.2 released