Which versions of azle are affected by CVE-2025-29776?

azle (npm) versions >= 0.27.0, < 0.30.0 is affected.

Is there a fix for CVE-2025-29776?

Yes. CVE-2025-29776 is fixed in 0.30.0. Upgrade to this version or later.

Is CVE-2025-29776 exploitable, and should I be worried?

Whether CVE-2025-29776 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-29776 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-29776?

Upgrade azle to 0.30.0 or later.

CVE-2025-29776 in azle

Q: What is CVE-2025-29776?

CVE-2025-29776 is a high-severity security vulnerability in azle (npm), affecting versions >= 0.27.0, < 0.30.0. It is fixed in 0.30.0.

Q: Is there a fix for CVE-2025-29776?

Yes. CVE-2025-29776 is fixed in 0.30.0. Upgrade to this version or later.

Q: Is CVE-2025-29776 exploitable, and should I be worried?

Whether CVE-2025-29776 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-29776 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-29776?

Upgrade azle to 0.30.0 or later.

CVE-2025-29776

CVE-2025-29776 is a high-severity security vulnerability in azle (npm), affecting versions >= 0.27.0, < 0.30.0. It is fixed in 0.30.0.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

In Azle, calling setTimer causes infinite loop of timers

Workarounds

If a canister is caught in this infinite loop after calling setTimer, the canister can be upgraded and the timers will all be cleared, thus ending the loop.

Impact

Calling setTimer in Azle versions 0.27.0, 0.28.0, and 0.29.0 causes an immediate infinite loop of timers to be executed on the canister, each timer attempting to clean up the global state of the previous timer.

The infinite loop will occur with any valid invocation of setTimer.

Affected versions

azle (>= 0.27.0, < 0.30.0)

Security releases

azle → 0.30.0 (npm)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

The problem has been fixed as of Azle version 0.30.0.

Frequently Asked Questions

What is CVE-2025-29776? CVE-2025-29776 is a high-severity security vulnerability in azle (npm), affecting versions >= 0.27.0, < 0.30.0. It is fixed in 0.30.0.
Which versions of azle are affected by CVE-2025-29776? azle (npm) versions >= 0.27.0, < 0.30.0 is affected.
Is there a fix for CVE-2025-29776? Yes. CVE-2025-29776 is fixed in 0.30.0. Upgrade to this version or later.
Is CVE-2025-29776 exploitable, and should I be worried? Whether CVE-2025-29776 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-29776 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-29776? Upgrade azle to 0.30.0 or later.