CLEANSTART-2026-EY66530: In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found

Published Nov 14, 2026
·
Updated

CVE-2026-97045 affects multiple packages. In childTextNodesAreLiteral, walking up the tree previously stopped at the nearest foreign ancestor once an HTML integration point was found. See references for individual vulnerability details.

Affected Software

5 affected componentsFixes available
cleanstart/loki<3.5.12-r9
3.5.12-r9
cleanstart/yunikorn-k8shim<1.8.0-r3
1.8.0-r3
cleanstart/yunikorn-k8shim<1.9.0-r1
1.9.0-r1
cleanstart/prometheus-node-exporter<1.11.1-r6
1.11.1-r6
cleanstart/prometheus-node-exporter<1.9.1-r7
1.9.1-r7

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade cleanstart/loki to a version that resolves this vulnerability.

    Fixed in 3.5.12-r9
  2. Upgrade

    Upgrade cleanstart/yunikorn-k8shim to a version that resolves this vulnerability.

    Fixed in 1.8.0-r3
  3. Upgrade

    Upgrade cleanstart/yunikorn-k8shim to a version that resolves this vulnerability.

    Fixed in 1.9.0-r1
  4. Upgrade

    Upgrade cleanstart/prometheus-node-exporter to a version that resolves this vulnerability.

    Fixed in 1.11.1-r6
  5. Upgrade

    Upgrade cleanstart/prometheus-node-exporter to a version that resolves this vulnerability.

    Fixed in 1.9.1-r7

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which deployments should be prioritized for review?

Review deployments of cleanstart/yunikorn-k8shim, cleanstart/prometheus-node-exporter, and cleanstart/loki. The provided data states that CVE-2026-97045 affects multiple packages but does not identify affected versions or configurations.

2

What level of attacker access is indicated by the severity vector?

The vector indicates network-reachable exploitation with low attack complexity, no required privileges, and required user interaction. It also indicates low confidentiality and integrity impact, no availability impact, and a changed scope.

3

Can the provided information confirm whether a default installation is affected?

No. The available data does not state whether default configurations are affected or describe any configuration prerequisites.

4

How can I determine whether a deployment is affected?

Confirm whether the deployment uses one of the listed packages, then consult the referenced individual vulnerability details for affected-version information. The provided advisory summary does not include version ranges or detection criteria.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203