What is GHSA-G9R4-XPMJ-MJ65?

GHSA-G9R4-XPMJ-MJ65 is a high-severity security vulnerability in handlebars (npm), affecting versions < 3.0.8. It is fixed in 3.0.8, 4.5.3.

Which versions of handlebars are affected by GHSA-G9R4-XPMJ-MJ65?

handlebars (npm) versions < 3.0.8 is affected.

Is there a fix for GHSA-G9R4-XPMJ-MJ65?

Yes. GHSA-G9R4-XPMJ-MJ65 is fixed in 3.0.8, 4.5.3. Upgrade to this version or later.

Is GHSA-G9R4-XPMJ-MJ65 exploitable, and should I be worried?

Whether GHSA-G9R4-XPMJ-MJ65 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 GHSA-G9R4-XPMJ-MJ65 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 GHSA-G9R4-XPMJ-MJ65?

Upgrade: handlebars to 3.0.8 or later, handlebars to 4.5.3 or later.

GHSA-G9R4-XPMJ-MJ65 in handlebars | Intelligent Application Security

Q: Which versions of handlebars are affected by GHSA-G9R4-XPMJ-MJ65?

handlebars (npm) versions < 3.0.8 is affected.

Q: Is there a fix for GHSA-G9R4-XPMJ-MJ65?

Yes. GHSA-G9R4-XPMJ-MJ65 is fixed in 3.0.8, 4.5.3. Upgrade to this version or later.

Q: Is GHSA-G9R4-XPMJ-MJ65 exploitable, and should I be worried?

Whether GHSA-G9R4-XPMJ-MJ65 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 GHSA-G9R4-XPMJ-MJ65 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 GHSA-G9R4-XPMJ-MJ65?

Upgrade: handlebars to 3.0.8 or later, handlebars to 4.5.3 or later.

Summary

Versions of handlebars prior to 3.0.8 or 4.5.3 are vulnerable to prototype pollution. It is possible to add or modify properties to the Object prototype through a malicious template. This may allow attackers to crash the application or execute Arbitrary Code in specific conditions.

Impact

Affected versions

handlebars (< 3.0.8) handlebars (>= 4.0.0, < 4.5.3)

Security releases

handlebars → 3.0.8 (npm) handlebars → 4.5.3 (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.

See it in your environment

Remediation advice

Upgrade to version 3.0.8, 4.5.3 or later.

Frequently Asked Questions

What is GHSA-G9R4-XPMJ-MJ65? GHSA-G9R4-XPMJ-MJ65 is a high-severity security vulnerability in handlebars (npm), affecting versions < 3.0.8. It is fixed in 3.0.8, 4.5.3.
Which versions of handlebars are affected by GHSA-G9R4-XPMJ-MJ65? handlebars (npm) versions < 3.0.8 is affected.
Is there a fix for GHSA-G9R4-XPMJ-MJ65? Yes. GHSA-G9R4-XPMJ-MJ65 is fixed in 3.0.8, 4.5.3. Upgrade to this version or later.
Is GHSA-G9R4-XPMJ-MJ65 exploitable, and should I be worried? Whether GHSA-G9R4-XPMJ-MJ65 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 GHSA-G9R4-XPMJ-MJ65 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 GHSA-G9R4-XPMJ-MJ65?
- Upgrade handlebars to 3.0.8 or later
- Upgrade handlebars to 4.5.3 or later

Other vulnerabilities in handlebars

CVE-2026-33940 CVE-2026-33939 CVE-2026-33938 CVE-2026-33937 CVE-2026-33916