CVE-2026-39821 Affecting velero-plugin-for-microsoft-azure package, versions <1.14.1-r2


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.69% (51st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-MINIMOSLATEST-VELEROPLUGINFORMICROSOFTAZURE-17219717
  • published7 Jun 2026
  • disclosed22 May 2026

Introduced: 22 May 2026

CVE-2026-39821  (opens in a new tab)

How to fix?

Upgrade Minimos:latest velero-plugin-for-microsoft-azure to version 1.14.1-r2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream velero-plugin-for-microsoft-azure package and not the velero-plugin-for-microsoft-azure package as distributed by Minimos. See How to fix? for Minimos:latest relevant fixed versions and status.

The ToASCII and ToUnicode functions incorrectly accept Punycode-encoded labels that decode to an ASCII-only label. For example, ToUnicode("xn--example-.com") incorrectly returns the name "example.com" rather than an error. This behavior can lead to privilege escalation in programs using the idna package. For example, a program which performs privilege checks on the ASCII hostname may reject "example.com" but permit "xn--example-.com". If that program subsequently converts the ASCII hostname to Unicode, it will inadvertently permits access to the Unicode name "example.com".

References

CVSS Base Scores

version 3.1