CVE-2026-82856

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-31. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

@hulumi/policies versions before 1.3.2 fail to properly validate set-qualified AWS IAM condition operators in GitHub OIDC trust policies. Attackers can use ForAnyValue:StringLike operators to hide wildcard GitHub Actions OIDC subject conditions from security guardrails.

CVSS v3
9.8
EG Score
9.8(high)
EG Risk
59(Track)
EG Risk 59/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

August 31, 2026

Last Modified

September 2, 2026

Advisory Details (2)

Auto-updated Sep 16, 2026
Patch available. Sources: github.
generic

@hulumi/policies before 1.3.2 OIDC Trust Policy Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hulumi-policies-before-1.3.2-oidc-trust-policy-bypass
github Patch Available

GitHub OIDC trust policy bypass via AWS set-qualified condition operators · Advisory · kerberosmansour/hulumi · GitHub

Affected: 1.3.2: the AWS trust-policy inspector now evaluates set-qualified string operator

https://github.com/kerberosmansour/hulumi/security/advisories/GHSA-q2f7-m237-v562

Vendor Advisories for CVE-2026-82856(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFixed inDependents
@hulumi/policies—1.3.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 53× in last 7d / 155× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 155 total refreshes for this CVE.

  1. 2026-09-19 18:06 UTCEG score recompute
  2. 2026-09-19 18:06 UTCGHSA enrichment
  3. 2026-09-19 14:08 UTCGHSA enrichment
  4. 2026-09-19 10:00 UTCGHSA enrichment
  5. 2026-09-19 05:20 UTCGHSA enrichment
  6. 2026-09-19 01:24 UTCGHSA enrichment
  7. 2026-09-18 21:26 UTCEG score recompute
  8. 2026-09-18 21:26 UTCGHSA enrichment
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-18 16:33 UTCGHSA enrichment
  11. 2026-09-18 12:36 UTCGHSA enrichment
  12. 2026-09-18 08:39 UTCGHSA enrichment
  13. 2026-09-18 04:42 UTCGHSA enrichment
  14. 2026-09-18 00:45 UTCGHSA enrichment
  15. 2026-09-17 20:48 UTCEG score recompute
  16. 2026-09-17 20:48 UTCGHSA enrichment
  17. 2026-09-17 14:59 UTCGHSA enrichment
  18. 2026-09-17 11:02 UTCGHSA enrichment
  19. 2026-09-17 07:05 UTCGHSA enrichment
  20. 2026-09-17 03:08 UTCGHSA enrichment
  21. 2026-09-16 23:11 UTCGHSA enrichment
  22. 2026-09-16 19:13 UTCGHSA enrichment
  23. 2026-09-16 15:15 UTCEG score recompute
  24. 2026-09-16 15:15 UTCGHSA enrichment
  25. 2026-09-16 14:08 UTCEPSS rescore
Show 75 more
  1. 2026-09-16 11:17 UTCGHSA enrichment
  2. 2026-09-16 07:21 UTCEG score recompute
  3. 2026-09-16 07:21 UTCGHSA enrichment
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-16 03:24 UTCGHSA enrichment
  6. 2026-09-15 23:27 UTCGHSA enrichment
  7. 2026-09-15 19:03 UTCGHSA enrichment
  8. 2026-09-15 15:06 UTCGHSA enrichment
  9. 2026-09-15 11:03 UTCGHSA enrichment
  10. 2026-09-15 06:40 UTCEG score recompute
  11. 2026-09-15 06:40 UTCGHSA enrichment
  12. 2026-09-15 03:12 UTCEPSS rescore
  13. 2026-09-15 03:12 UTCEPSS rescore
  14. 2026-09-15 02:42 UTCGHSA enrichment
  15. 2026-09-14 22:45 UTCGHSA enrichment
  16. 2026-09-14 18:48 UTCGHSA enrichment
  17. 2026-09-14 14:51 UTCGHSA enrichment
  18. 2026-09-14 10:54 UTCGHSA enrichment
  19. 2026-09-14 06:58 UTCGHSA enrichment
  20. 2026-09-14 03:01 UTCGHSA enrichment
  21. 2026-09-13 23:04 UTCGHSA enrichment
  22. 2026-09-13 19:08 UTCEG score recompute
  23. 2026-09-13 19:08 UTCGHSA enrichment
  24. 2026-09-13 15:11 UTCGHSA enrichment
  25. 2026-09-13 11:13 UTCGHSA enrichment
  26. 2026-09-13 07:16 UTCGHSA enrichment
  27. 2026-09-13 03:20 UTCGHSA enrichment
  28. 2026-09-12 23:23 UTCGHSA enrichment
  29. 2026-09-12 19:25 UTCGHSA enrichment
  30. 2026-09-12 15:28 UTCEG score recompute
  31. 2026-09-12 15:28 UTCGHSA enrichment
  32. 2026-09-12 11:31 UTCGHSA enrichment
  33. 2026-09-12 07:33 UTCGHSA enrichment
  34. 2026-09-12 03:35 UTCGHSA enrichment
  35. 2026-09-11 23:38 UTCGHSA enrichment
  36. 2026-09-11 19:41 UTCGHSA enrichment
  37. 2026-09-11 15:44 UTCEG score recompute
  38. 2026-09-11 15:44 UTCGHSA enrichment
  39. 2026-09-11 14:53 UTCEPSS rescore
  40. 2026-09-11 14:53 UTCEPSS rescore
  41. 2026-09-11 11:47 UTCEG score recompute
  42. 2026-09-11 11:47 UTCGHSA enrichment
  43. 2026-09-11 07:49 UTCGHSA enrichment
  44. 2026-09-11 03:52 UTCGHSA enrichment
  45. 2026-09-10 23:55 UTCGHSA enrichment
  46. 2026-09-10 19:35 UTCGHSA enrichment
  47. 2026-09-10 15:38 UTCGHSA enrichment
  48. 2026-09-10 11:41 UTCEG score recompute
  49. 2026-09-10 11:41 UTCGHSA enrichment
  50. 2026-09-10 07:39 UTCGHSA enrichment
  51. 2026-09-10 03:42 UTCGHSA enrichment
  52. 2026-09-09 23:45 UTCGHSA enrichment
  53. 2026-09-09 19:16 UTCGHSA enrichment
  54. 2026-09-09 15:19 UTCGHSA enrichment
  55. 2026-09-09 11:23 UTCGHSA enrichment
  56. 2026-09-09 07:25 UTCGHSA enrichment
  57. 2026-09-09 03:28 UTCGHSA enrichment
  58. 2026-09-08 23:31 UTCEG score recompute
  59. 2026-09-08 23:31 UTCGHSA enrichment
  60. 2026-09-08 22:01 UTCEPSS rescore
  61. 2026-09-08 11:53 UTCGHSA enrichment
  62. 2026-09-08 07:53 UTCGHSA enrichment
  63. 2026-09-08 03:55 UTCGHSA enrichment
  64. 2026-09-07 23:58 UTCGHSA enrichment
  65. 2026-09-07 20:01 UTCGHSA enrichment
  66. 2026-09-07 16:04 UTCEG score recompute
  67. 2026-09-07 16:04 UTCGHSA enrichment
  68. 2026-09-07 12:06 UTCGHSA enrichment
  69. 2026-09-07 08:09 UTCGHSA enrichment
  70. 2026-09-07 04:12 UTCGHSA enrichment
  71. 2026-09-07 00:09 UTCGHSA enrichment
  72. 2026-09-06 20:09 UTCGHSA enrichment
  73. 2026-09-06 16:12 UTCEG score recompute
  74. 2026-09-06 16:12 UTCGHSA enrichment
  75. 2026-09-06 13:48 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-82856?
CVE-2026-82856 is a critical vulnerability published on August 31, 2026. @hulumi/policies versions before 1.3.2 fail to properly validate set-qualified AWS IAM condition operators in GitHub OIDC trust policies. Attackers can use ForAnyValue:StringLike operators to hide wildcard GitHub Actions OIDC subject conditions from security guardrails.
When was CVE-2026-82856 disclosed?
CVE-2026-82856 was first published in the National Vulnerability Database on August 31, 2026, with the most recent update on September 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82856 actively exploited?
CVE-2026-82856 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 78.8% of all scored CVEs.
What is the CVSS score of CVE-2026-82856?
CVE-2026-82856 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-82856?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82856, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82856

Explore →

Is Your Infrastructure Affected by CVE-2026-82856?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs