CVE-2026-33117

CRITICALPre-NVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

Score 9.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-12. the CNA's CVSS baseline 9.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:microsoft, epss, ghsa
Trending — 3 sources updated this week
9.1EG
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.1Exploit: None knownExposed: 0

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

The Java Key Vault Keys library in the Azure SDK for Java contains an issue in the local cryptographic verification path where authentication tag comparison was implemented incorrectly. In affected applications that use the vulnerable local cryptography path, specially crafted encrypted input may bypass integrity verification checks. Operations delegated to the Key Vault service are not affected. The issue is addressed in version 4.10.6.

CVSS v3
9.1
EG Score
9.1(medium)
EG Risk
56(Track)
EG Risk 56/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
Severity91% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

May 12, 2026

Last Modified

August 10, 2026

Advisory Details (1)

Auto-updated Aug 1, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33117

Vendor Advisories for CVE-2026-33117(2)

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)
Maven(1)
PackageVulnerable rangeFixed inDependents
com.azure:azure-security-keyvault-keys4.0.0 ... 4.9.4 (92 versions)4.10.6—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 95× 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 309 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-33117?
CVE-2026-33117 is a critical vulnerability published on May 12, 2026. The Java Key Vault Keys library in the Azure SDK for Java contains an issue in the local cryptographic verification path where authentication tag comparison was implemented incorrectly. In affected applications that use the vulnerable local cryptography path, specially crafted encrypted input may…
When was CVE-2026-33117 disclosed?
CVE-2026-33117 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on August 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33117 actively exploited?
CVE-2026-33117 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 60.7% of all scored CVEs.
What is the CVSS score of CVE-2026-33117?
CVE-2026-33117 has a CVSS v4.0 base score of 9.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-33117?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33117, 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-33117

Explore →

Is Your Infrastructure Affected by CVE-2026-33117?

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

Start Free Scan →Browse All CVEs