CVE-2026-82861
Policy bypass in @hulumi/policies lets spoofed SecureBucket evidence skip validation.
Is CVE-2026-82861 being exploited?
Not confirmed. CVE-2026-82861 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-82861?
CVE-2026-82861 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-82861?
Yes. A fix has been recorded for CVE-2026-82861. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-82861 affect?
CVE-2026-82861 affects @hulumi/policies < 1.3.2, Hulumi/Pulumi policy validators, CI/CD pipelines using hulumi policies. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-82861?
Upgrade to @hulumi/policies v1.3.2 immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attackers can submit spoofed SecureBucket parent evidence to bypass policy checks, allowing unsafe bucket configurations to pass validation and expose data.
Patch when possible
- affected< 1.3.2
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.