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
9.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.1Exploit: NoneExposed: 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
38.5%
KEV
Not listed

Published

May 12, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated May 12, 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 / 51× 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 207 total refreshes for this CVE.

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

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 June 19, 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 38.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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