What is GHSA-JCGR-9698-82JX?

GHSA-JCGR-9698-82JX is a low-severity command injection vulnerability in @floffah/build (npm), affecting versions < 1.0.0. It is fixed in 1.0.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.

Which versions of @floffah/build are affected by GHSA-JCGR-9698-82JX?

@floffah/build (npm) versions < 1.0.0 is affected.

Is there a fix for GHSA-JCGR-9698-82JX?

Yes. GHSA-JCGR-9698-82JX is fixed in 1.0.0. Upgrade to this version or later.

Is GHSA-JCGR-9698-82JX exploitable, and should I be worried?

Whether GHSA-JCGR-9698-82JX 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-JCGR-9698-82JX 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-JCGR-9698-82JX?

Upgrade @floffah/build to 1.0.0 or later.

GHSA-JCGR-9698-82JX in @floffah/build

Q: Which versions of @floffah/build are affected by GHSA-JCGR-9698-82JX?

@floffah/build (npm) versions < 1.0.0 is affected.

Q: Is there a fix for GHSA-JCGR-9698-82JX?

Yes. GHSA-JCGR-9698-82JX is fixed in 1.0.0. Upgrade to this version or later.

Q: Is GHSA-JCGR-9698-82JX exploitable, and should I be worried?

Whether GHSA-JCGR-9698-82JX 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-JCGR-9698-82JX 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-JCGR-9698-82JX?

Upgrade @floffah/build to 1.0.0 or later.

Summary

Improper Neutralization of Special Elements used in a Command ('Command Injection') in @floffah/build

Workarounds

There is no work around. You should update asap.

Notes

This notice is mainly just to make sure people update to the latest version. This isn't that bad, but should encourage you to update.

Impact

If you are using the esbuild target or command you are at risk of code/option injection. Attackers can use the command line option to maliciously change your settings in order to damage your project.

Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command. Typical impact: arbitrary command execution in the application's environment.

Affected versions

@floffah/build (< 1.0.0)

Security releases

@floffah/build → 1.0.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 patched in v1.0.0 as it uses a proper method to pass configs to esbuild/estrella.

Frequently Asked Questions

What is GHSA-JCGR-9698-82JX? GHSA-JCGR-9698-82JX is a low-severity command injection vulnerability in @floffah/build (npm), affecting versions < 1.0.0. It is fixed in 1.0.0. Untrusted input is inserted into a command that is later executed by the application, allowing the attacker to alter the intent of that command.
Which versions of @floffah/build are affected by GHSA-JCGR-9698-82JX? @floffah/build (npm) versions < 1.0.0 is affected.
Is there a fix for GHSA-JCGR-9698-82JX? Yes. GHSA-JCGR-9698-82JX is fixed in 1.0.0. Upgrade to this version or later.
Is GHSA-JCGR-9698-82JX exploitable, and should I be worried? Whether GHSA-JCGR-9698-82JX 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-JCGR-9698-82JX 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-JCGR-9698-82JX? Upgrade @floffah/build to 1.0.0 or later.