Release v3.16.7 (2026-10-28)
Last updated: October 28, 2026
Update Notes
Some changes may require action before updating to this version. Visit the Guidance on Updating section before beginning the update process.
What's Changed
(14277): Added an optional
include_inherited_policiesquery parameter toGET /v4/project-cloud-access-role. Setting it tofalseomits inherited cloud rule policies from the response and greatly improves response time for large environments. Defaults totrue.(14330): Added “Last 60 Days” and “Last 90 Days” as time-frame options in the date range picker.
(14348): The Billing Reports Status column within System Diagnostics can now be sorted.
Bug Fixes
(13055): Fixed an issue where importing a compliance program’s Managed Resources omitted GCP compliance checks, leaving GCP-only programs without a compliance standard and multi-cloud programs incomplete. Previously imported programs are corrected on the next import of Managed Resources. See this page for more information on loading Managed Resources.
(14137): Fixed an issue that omitted historical spend from spend reports for users with project-scoped financials permissions after an account was moved to a new billing source.
(14338): Fixed an issue where users with project level permissions were unable to view all account level data under the project financials section
(14399): Fixed an issue where the financials poller could repeatedly crash and stop importing billing data when an AWS Detailed Billing Report (DBR) contained line items with blank usage dates while daily cost granularity was enabled.
(14468): Fixed an issue that omitted inactive accounts from the project account list for users with project-scoped financials permissions.
(14494): Fixed an issue that caused the wrong total count to be returned from the V4
project-cloud-access-roleAPI and the V4ou-cloud-access-roleAPI when using pagination.(14496): Fixed an issue that caused incorrect AWS Session Tag information from being attributed to the project in the V4
project-cloud-access-roleAPI.(14480): Upgraded to Go 1.26.10 to address GO-2026-6809 / CVE-2026-111943, ensuring Kion rejects certificates issued by compromised eMudhra intermediate certificate authorities, even when the host’s trust store is outdated.
(13652, 14514, 14425): Updated dependencies to resolve vulnerabilities.
Update Files
Different types of deployments require different update files. For information on which files you need for your deployment type, see Updating Kion.