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

Published Nov 20, 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

46 affected componentsFixes available
cleanstart/prometheus-node-exporter<1.12.1-r3
1.12.1-r3
cleanstart/rabbitmq-cluster-operator<2.22.5-r1
2.22.5-r1
cleanstart/rabbitmq-messaging-topology-operator<1.19.3-r10
1.19.3-r10
cleanstart/argo-workflows<3.7.18-r2
3.7.18-r2
cleanstart/grafana<13.1.10-r0
13.1.10-r0
cleanstart/prometheus-statsd-exporter<0.29.0-r6
0.29.0-r6
cleanstart/prometheus-statsd-exporter<0.31.0-r3
0.31.0-r3
cleanstart/kyverno<1.15.3-r5
1.15.3-r5
cleanstart/tempo<2.9.5-r3
2.9.5-r3
cleanstart/openbao<2.5.5-r2
2.5.5-r2
cleanstart/kubernetes<1.35.7-r4
1.35.7-r4
cleanstart/prometheus-alertmanager<0.32.2-r2
0.32.2-r2
cleanstart/trust-manager<0.24.0-r6
0.24.0-r6
cleanstart/trust-manager<0.21.1-r4
0.21.1-r4
cleanstart/opentelemetry-collector-contrib<0.163.0-r0
0.163.0-r0
cleanstart/prometheus-operator<0.91.0-r12
0.91.0-r12
cleanstart/argo-cd<3.5.6-r3
3.5.6-r3
cleanstart/argo-cd<3.4.12-r1
3.4.12-r1
cleanstart/mongodb<8.1.3-r8
8.1.3-r8
cleanstart/argo-cd<3.3.18-r1
3.3.18-r1
cleanstart/argo-cd<3.2.12-r12
3.2.12-r12
cleanstart/argo-cd<3.3.19-r1
3.3.19-r1
cleanstart/argo-cd<3.3.19-r4
3.3.19-r4
cleanstart/vault<1.19.5-r9
1.19.5-r9
cleanstart/external-dns<0.21.0-r8
0.21.0-r8
cleanstart/nfs-subdir-external-provisioner<4.0.18-r6
4.0.18-r6
cleanstart/memcached-exporter<0.18.0-r1
0.18.0-r1
cleanstart/openbao<2.6.4-r2
2.6.4-r2
cleanstart/rabbitmq-messaging-topology-operator<1.17.4-r4
1.17.4-r4
cleanstart/rabbitmq-messaging-topology-operator<1.18.3-r7
1.18.3-r7
cleanstart/prometheus-mysqld-exporter<0.20.0-r6
0.20.0-r6
cleanstart/prometheus-operator<0.90.1-r7
0.90.1-r7
cleanstart/prometheus-mysqld-exporter<0.18.0-r11
0.18.0-r11
cleanstart/opentelemetry-collector-contrib<0.161.0-r2
0.161.0-r2
cleanstart/prometheus-mysqld-exporter<0.17.2-r13
0.17.2-r13
cleanstart/opentelemetry-collector-contrib<0.160.0-r9
0.160.0-r9
cleanstart/stakater-reloader<1.1.0-r11
1.1.0-r11
cleanstart/stakater-reloader<1.3.0-r12
1.3.0-r12
cleanstart/rclone<1.73.5-r10
1.73.5-r10
cleanstart/rclone<1.74.4-r5
1.74.4-r5
cleanstart/prometheus-statsd-exporter<0.28.0-r8
0.28.0-r8
cleanstart/prometheus-node-exporter-fips<1.9.1-r4
1.9.1-r4
cleanstart/prometheus<3.14.0-r3
3.14.0-r3
cleanstart/prometheus-alertmanager<0.31.1-r1
0.31.1-r1
cleanstart/prometheus-node-exporter<1.10.2-r8
1.10.2-r8
cleanstart/grafana<13.2.5-r1
13.2.5-r1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 1.12.1-r3
  2. Upgrade

    Upgrade cleanstart/rabbitmq-cluster-operator to a version that resolves this vulnerability.

    Fixed in 2.22.5-r1
  3. Upgrade

    Upgrade cleanstart/rabbitmq-messaging-topology-operator to a version that resolves this vulnerability.

    Fixed in 1.19.3-r10
  4. Upgrade

    Upgrade cleanstart/argo-workflows to a version that resolves this vulnerability.

    Fixed in 3.7.18-r2
  5. Upgrade

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

    Fixed in 13.1.10-r0
  6. Upgrade

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

    Fixed in 0.29.0-r6
  7. Upgrade

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

    Fixed in 0.31.0-r3
  8. Upgrade

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

    Fixed in 1.15.3-r5
  9. Upgrade

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

    Fixed in 1.15.3-r6
  10. Upgrade

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

    Fixed in 2.9.5-r3
  11. Upgrade

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

    Fixed in 2.5.5-r2
  12. Upgrade

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

    Fixed in 1.35.7-r4
  13. Upgrade

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

    Fixed in 1.35.7-r5
  14. Upgrade

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

    Fixed in 1.35.7-r7
  15. Upgrade

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

    Fixed in 0.32.2-r2
  16. Upgrade

    Upgrade cleanstart/trust-manager to a version that resolves this vulnerability.

    Fixed in 0.24.0-r6
  17. Upgrade

    Upgrade cleanstart/trust-manager to a version that resolves this vulnerability.

    Fixed in 0.21.1-r4
  18. Upgrade

    Upgrade cleanstart/opentelemetry-collector-contrib to a version that resolves this vulnerability.

    Fixed in 0.163.0-r0
  19. Upgrade

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

    Fixed in 0.91.0-r12
  20. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.5.6-r3
  21. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.4.12-r1
  22. Upgrade

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

    Fixed in 8.1.3-r8
  23. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.3.18-r1
  24. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.2.12-r12
  25. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.3.19-r1
  26. Upgrade

    Upgrade cleanstart/argo-cd to a version that resolves this vulnerability.

    Fixed in 3.3.19-r4
  27. Upgrade

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

    Fixed in 1.19.5-r9
  28. Upgrade

    Upgrade cleanstart/external-dns to a version that resolves this vulnerability.

    Fixed in 0.21.0-r8
  29. Upgrade

    Upgrade cleanstart/nfs-subdir-external-provisioner to a version that resolves this vulnerability.

    Fixed in 4.0.18-r6
  30. Upgrade

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

    Fixed in 0.18.0-r1
  31. Upgrade

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

    Fixed in 0.18.0-r2
  32. Upgrade

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

    Fixed in 2.6.4-r2
  33. Upgrade

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

    Fixed in 2.6.4-r3
  34. Upgrade

    Upgrade cleanstart/rabbitmq-messaging-topology-operator to a version that resolves this vulnerability.

    Fixed in 1.17.4-r4
  35. Upgrade

    Upgrade cleanstart/rabbitmq-messaging-topology-operator to a version that resolves this vulnerability.

    Fixed in 1.18.3-r7
  36. Upgrade

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

    Fixed in 0.20.0-r6
  37. Upgrade

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

    Fixed in 0.90.1-r7
  38. Upgrade

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

    Fixed in 0.18.0-r11
  39. Upgrade

    Upgrade cleanstart/opentelemetry-collector-contrib to a version that resolves this vulnerability.

    Fixed in 0.161.0-r2
  40. Upgrade

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

    Fixed in 0.17.2-r13
  41. Upgrade

    Upgrade cleanstart/opentelemetry-collector-contrib to a version that resolves this vulnerability.

    Fixed in 0.160.0-r9
  42. Upgrade

    Upgrade cleanstart/stakater-reloader to a version that resolves this vulnerability.

    Fixed in 1.1.0-r11
  43. Upgrade

    Upgrade cleanstart/stakater-reloader to a version that resolves this vulnerability.

    Fixed in 1.3.0-r12
  44. Upgrade

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

    Fixed in 1.73.5-r10
  45. Upgrade

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

    Fixed in 1.74.4-r5
  46. Upgrade

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

    Fixed in 0.28.0-r8
  47. Upgrade

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

    Fixed in 1.9.1-r4
  48. Upgrade

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

    Fixed in 3.14.0-r3
  49. Upgrade

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

    Fixed in 0.31.1-r1
  50. Upgrade

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

    Fixed in 1.10.2-r8
  51. Upgrade

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

    Fixed in 13.2.5-r1
  52. Upgrade

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

    Fixed in 13.2.5-r2

Child vulnerabilities

Contains the following vulnerabilities.

Frequently Asked Questions

1

Which deployments should be investigated for exposure?

Review deployments using cleanstart/argo-cd, cleanstart/rabbitmq-messaging-topology-operator, cleanstart/prometheus-statsd-exporter, cleanstart/opentelemetry-collector-contrib, cleanstart/prometheus-mysqld-exporter, cleanstart/prometheus-node-exporter, cleanstart/grafana, or cleanstart/openbao. The advisory states that CVE-2026-97045 affects multiple packages, but does not provide affected version ranges.

2

Does an attacker need credentials or direct local access to exploit this issue?

The supplied vector indicates network access is sufficient and no privileges are required. However, user interaction is required.

3

What is the stated security impact if exploitation succeeds?

The vector indicates low confidentiality and integrity impact, no availability impact, and a changed scope. The supplied data does not describe the specific data exposure or modification scenario.

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