Skip to content
CVE-2026-130870: Verify ClearFlask 2.7.3 charts and running images

CVE-2026-130870: Verify ClearFlask 2.7.3 charts and running images

November 19, 2026

ClearFlask versions before 2.7.3 are affected by CVE-2026-130870. The maintainer disclosed the issue on November 15, 2026; the 2.7.3 release was published on November 14.

The maintainer labels the issue High. VulnCheck’s CNA record, published November 17, assigns CVSS 4.0 score 9.1, Critical, and CVSS 3.1 score 7.4, High. Include the source and scoring version when recording these ratings.

Identify the deployed application

For a self-managed deployment, record the ClearFlask application version and running image identities. Include every replica and the deployment configuration used to recreate it. For a hosted service, request the provider’s confirmation that the deployment includes the fix; a locally downloaded package does not describe the hosted service.

The official release asset clearflask-2.7.3.tgz is a Helm chart. Its Chart.yaml declares chart version 2.7.3 and appVersion 2.7.3. The packaged defaults select tag 2.7.3 for both the server and Connect images. Those declarations describe the chart defaults, not the images currently running in your cluster.

Review overrides before upgrading

Choose 2.7.3 or a later supported release containing the fix. Review the release package and preserve the deployment’s approved configuration and secrets through the normal upgrade process.

For Helm installations, inspect the effective values for server.image and connect.image. Existing overrides can retain an older image even when the chart version changes. Check that the selected image references are available from the publisher before rollout; the chart archive alone does not establish registry availability.

Back up the deployment configuration and application data using the established recovery procedure. Apply the update through the deployment system and wait for the normal readiness checks to pass.

Check the running replicas

Compare each running server and Connect image with the approved references and record its resolved digest. Confirm that old replicas have stopped and that the next deployment will use the same approved versions.

Finish with an ordinary authorized sign-in, a read-only view of an existing project and a review of normal startup logs. Retain the chart version, effective image settings and running digests together so that an updated chart cannot conceal an unchanged application image.

Acknowledgements

This post was created with assistance from AI.

Last updated on