How severe is GHSA-gfp8-mp24-5vxg?

No CVSS score has been assigned to GHSA-gfp8-mp24-5vxg yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-gfp8-mp24-5vxg?

GHSA-gfp8-mp24-5vxg affects the following packages: @hulumi/baseline (npm). Ecosystems affected: npm.

How do I fix GHSA-gfp8-mp24-5vxg?

Update @hulumi/baseline to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gfp8-mp24-5vxg is resolved across your whole dependency graph.

How do I detect GHSA-gfp8-mp24-5vxg in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hulumi/baseline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-gfp8-mp24-5vxg if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-gfp8-mp24-5vxg actively exploited in the wild?

No public exploit code has been indexed for GHSA-gfp8-mp24-5vxg yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-gfp8-mp24-5vxg?

GHSA-gfp8-mp24-5vxg has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 14th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-gfp8-mp24-5vxg?

GHSA-gfp8-mp24-5vxg is classified as CWE-778 (CWE-778). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-gfp8-mp24-5vxg published, and has it been updated?

GHSA-gfp8-mp24-5vxg was published on May 21, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

GHSA-gfp8-mp24-5vxg — @hulumi/baseline

GHSA-gfp8-mp24-5vxg is a CWE-778 vulnerability in @hulumi/baseline. A fix is available for @hulumi/baseline — see the affected versions and patch details below.

@hulumi/baseline: CloudTrail selector tampering events were not fully detected

Also known asCVE-2026-82863

Published

May 21, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 27, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-gfp8-mp24-5vxg.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

1other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@hulumi/baselinenpm

836downloads / week

Description

Impact: @hulumi/baseline versions before 1.3.2 could miss some CloudTrail event-selector tampering evidence, reducing coverage for changes to audit logging configuration.

Patched in 1.3.2: detection coverage and regression tests were expanded.

Remediation: upgrade @hulumi/baseline to 1.3.2 or later and rerun affected previews/checks.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@hulumi/baseline`	all versions	1.3.2`npm install @hulumi/baseline@1.3.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @hulumi/baseline, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @hulumi/baseline to 1.3.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gfp8-mp24-5vxg is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Impact: @hulumi/baseline versions before 1.3.2 could miss some CloudTrail event-selector tampering evidence, reducing coverage for changes to audit logging configuration. Patched in 1.3.2: detection coverage and regression tests were expanded. Remediation: upgrade @hulumi/baseline to 1.3.2 or later and rerun affected previews/checks.

O3 Security · Impact-Aware SCA

Is GHSA-gfp8-mp24-5vxg in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works