Is CVE-2026-82855 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82855 being exploited in the wild.

How severe is CVE-2026-82855?

Critical severity, with a CVSS score of 9.8, published 31 August 2026.

Which products and versions are affected?

Hulumi Policies < 1.3.2; @hulumi/policies (npm) SEMVER:introduced=0,fixed=1.3.2.

Is there a fix for CVE-2026-82855?

Yes. @hulumi/policies (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-82855 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-82855?

Check whether you run Hulumi Policies or @hulumi/policies (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.

CVE-2026-82855: @hulumi/policies protection mechanism bypass in validators

Q: Which products and versions are affected?

Hulumi Policies < 1.3.2; @hulumi/policies (npm) SEMVER:introduced=0,fixed=1.3.2.

Q: Is there a fix for CVE-2026-82855?

Yes. @hulumi/policies (npm): upgrade to 1.3.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-82855 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-82855?

Check whether you run Hulumi Policies or @hulumi/policies (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.

CVE-2026-82855 · Severity: critical · CVSS 9.8 · Published 2026-08-31

@hulumi/policies is a governance library that enforces compliance rules for Cloudflare configurations and deployment practices. Versions before 1.3.2 had a flaw where unrelated compliance evidence from one resource could suppress security violations in different resources within the same deployment stack, allowing attackers to bypass critical guardrails. This could allow non-compliant configurations to pass validation checks.

Technologies: @hulumi/policies (npm). Vendors: npm.

Quick answers

Is CVE-2026-82855 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82855 being exploited in the wild.
How severe is CVE-2026-82855?: Critical severity, with a CVSS score of 9.8, published 31 August 2026.
Which products and versions are affected?: Hulumi Policies < 1.3.2; @hulumi/policies (npm) SEMVER:introduced=0,fixed=1.3.2.
Is there a fix for CVE-2026-82855?: Yes. @hulumi/policies (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-82855 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-82855?: Check whether you run Hulumi Policies or @hulumi/policies (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/policies (npm): upgrade to 1.3.2 or later
```
npm install @hulumi/policies@1.3.2
```

Technical details

@hulumi/policies is a governance validation library for Cloudflare and deployment configurations. The vulnerability is a protection mechanism failure (CWE-693) in which validators incorrectly use stack-wide evidence caching to validate compliance. When checking if evidence exists for a violation, the library uses shortcuts that do not correlate evidence to the specific protected resource (zone, hostname, origin, or repository). An attacker can submit compliant-looking evidence for one resource to suppress violations reported for a different, unrelated resource in the same deployment stack. This allows non-compliant configurations to bypass governance guardrails. The flaw requires no authentication or user interaction, as it operates at the validator layer. Patched in version 1.3.2, which correlates evidence to specific resources and includes regression tests.

Affected products

hulumi @hulumi/policies < 1.3.2

Identifiers

CVE-2026-82855
GHSA-59f3-7227-wmh4

Timeline

2026-05-21: disclosed: Advisory GHSA-59f3-7227-wmh4 published
2026-05-21: patched: Version 1.3.2 released with fix

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.