CVE-2026-97045 Affecting cluster-autoscaler-1.33 package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.2% (11th 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-CLUSTERAUTOSCALER133-21787382
  • published29 Oct 2026
  • disclosed27 Oct 2026

Introduced: 27 Oct 2026

NewCVE-2026-97045  (opens in a new tab)

How to fix?

There is no fixed version for Minimos:latest cluster-autoscaler-1.33.

NVD Description

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

In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found. However, that integration point may itself be a descendant of an element that was foster-parented into a foreign namespace (such as <mglyph> or <malignmark> fostered under <mtext>), causing a parser to resolve the subtree in a different foreign namespace upon re-parsing the rendered output. Continue walking the full ancestor chain and verify that every transition from a non-empty namespace occurs at an HTML integration point before emitting literal text.