Skip to main content

Solutions

Law firms

Tax, audit & accounting firms

Corporations

Governments

Products

Legal

Trade & supply

Tax, audit & accounting

Corporate tax

Risk & fraud

Books

Recommended products

Questions? We are here to help.
Contact us

Purchase

Buy solutions

Buy books

Contact sales

Questions? We are here to help.

Resources

Insights

Events

Product training

Product communities

Developers

Determination Anywhere

Determination Anywhere 2026.01 hot fix release notes

Please review this release note in conjunction with the Determination – Enterprise Cloud (EC) release notes, which outline key updates to the core application. These include enhancements to the tax engine logic, regulatory compliance improvements, UI feature upgrades, and may also highlight defect resolutions and known issues – all of which directly impact the tax engine's functionality within Determination Anywhere (DA).

Release highlights

This patch resolves few critical issues identified in the Determination Enterprise Cloud and Determination Anywhere applications.

Fixes

The topics below highlight high‑risk issues uncovered during UAT that necessitated a patch in this release.
Critical security vulnerabilities (4895388)
Critical security vulnerabilities identified in the Determination Anywhere (DA) client-side application components have been resolved in this patch release.
  • Tax calculation component tied to the tax engine – CVE-2022-0839. Please note that CVE-2024-1597 will be addressed in an upcoming release.
  • PostgreSQL database bitnami components – CVE-2025-22871, CVE-2024-24790, CVE-2025-22248, CVE-2024-40896. The fixes are included in the image tags. For
    postgresql-repmgr
     it should be 17.7.0; for
    pgpool
    , it should be 4.6.0. Please note that the database must be rebuilt to deploy the new images.
Config sync timeout with SDI (TDSS) (4972385)
An Out‑of‑Memory error was identified in the full data sync process using the SDI mechanism within DA. When this occurred, the underlying database connection was left open, causing the same connection thread to be reused for subsequent scheduled sync runs. As a result, all future sync attempts failed until the application was restarted. After several hours – or within a day – the full SDI sync operation would consistently fail with a
transactionTimedOutException
, showing identical deadline timestamps across runs.
This issue has been resolved by adding explicit
OutOfMemoryError
 handling within the application to catch and manage these exceptions gracefully,

This article applies to:

  • Product: ONESOURCE Determination

Related Content