What is GHSA-C3M8-X3CG-QM2C?

GHSA-C3M8-X3CG-QM2C is a medium-severity security vulnerability in helmet-csp (npm), affecting versions >= 1.2.2, < 2.9.1. It is fixed in 2.9.1.

How severe is GHSA-C3M8-X3CG-QM2C?

GHSA-C3M8-X3CG-QM2C has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of helmet-csp are affected by GHSA-C3M8-X3CG-QM2C?

helmet-csp (npm) versions >= 1.2.2, < 2.9.1 is affected.

Is there a fix for GHSA-C3M8-X3CG-QM2C?

Yes. GHSA-C3M8-X3CG-QM2C is fixed in 2.9.1. Upgrade to this version or later.

Is GHSA-C3M8-X3CG-QM2C exploitable, and should I be worried?

Whether GHSA-C3M8-X3CG-QM2C 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-C3M8-X3CG-QM2C 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-C3M8-X3CG-QM2C?

Upgrade helmet-csp to 2.9.1 or later.

GHSA-C3M8-X3CG-QM2C in helmet-csp

Q: How severe is GHSA-C3M8-X3CG-QM2C?

GHSA-C3M8-X3CG-QM2C has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of helmet-csp are affected by GHSA-C3M8-X3CG-QM2C?

helmet-csp (npm) versions >= 1.2.2, < 2.9.1 is affected.

Q: Is there a fix for GHSA-C3M8-X3CG-QM2C?

Yes. GHSA-C3M8-X3CG-QM2C is fixed in 2.9.1. Upgrade to this version or later.

Q: Is GHSA-C3M8-X3CG-QM2C exploitable, and should I be worried?

Whether GHSA-C3M8-X3CG-QM2C 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-C3M8-X3CG-QM2C 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-C3M8-X3CG-QM2C?

Upgrade helmet-csp to 2.9.1 or later.

Summary

Configuration Override in helmet-csp

Versions of helmet-csp before to 2.9.1 are vulnerable to a Configuration Override affecting the application's Content Security Policy (CSP). The package's browser sniffing for Firefox deletes the default-src CSP policy, which is the fallback policy. This allows an attacker to remove an application's default CSP, possibly rendering the application vulnerable to Cross-Site Scripting.

Impact

GHSA-C3M8-X3CG-QM2C has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.9.1); upgrading removes the vulnerable code path.

Affected versions

helmet-csp (>= 1.2.2, < 2.9.1)

Security releases

helmet-csp → 2.9.1 (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

Upgrade to version 2.9.1 or later. Setting the browserSniff configuration to false in vulnerable versions also mitigates the issue.

Frequently Asked Questions

What is GHSA-C3M8-X3CG-QM2C? GHSA-C3M8-X3CG-QM2C is a medium-severity security vulnerability in helmet-csp (npm), affecting versions >= 1.2.2, < 2.9.1. It is fixed in 2.9.1.
How severe is GHSA-C3M8-X3CG-QM2C? GHSA-C3M8-X3CG-QM2C has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of helmet-csp are affected by GHSA-C3M8-X3CG-QM2C? helmet-csp (npm) versions >= 1.2.2, < 2.9.1 is affected.
Is there a fix for GHSA-C3M8-X3CG-QM2C? Yes. GHSA-C3M8-X3CG-QM2C is fixed in 2.9.1. Upgrade to this version or later.
Is GHSA-C3M8-X3CG-QM2C exploitable, and should I be worried? Whether GHSA-C3M8-X3CG-QM2C 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-C3M8-X3CG-QM2C 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-C3M8-X3CG-QM2C? Upgrade helmet-csp to 2.9.1 or later.