What is GHSA-2MVQ-XP48-4C77?

GHSA-2MVQ-XP48-4C77 is a high-severity uncontrolled resource consumption vulnerability in subtext (npm), affecting versions >= 0.0.0. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.

Which versions of subtext are affected by GHSA-2MVQ-XP48-4C77?

subtext (npm) versions >= 0.0.0 is affected.

Is there a fix for GHSA-2MVQ-XP48-4C77?

No fixed version is listed for GHSA-2MVQ-XP48-4C77 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is GHSA-2MVQ-XP48-4C77 exploitable, and should I be worried?

Whether GHSA-2MVQ-XP48-4C77 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-2MVQ-XP48-4C77 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-2MVQ-XP48-4C77?

No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.

GHSA-2MVQ-XP48-4C77 in subtext

Summary

Denial of Service in subtext

All versions of subtext are vulnerable to Denial of Service (DoS). The package fails to enforce the maxBytes configuration for payloads with chunked encoding that are written to the file system. This allows attackers to send requests with arbitrary payload sizes, which may exhaust system resources leading to Denial of Service.

Impact

Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service. Typical impact: denial of service.

Affected versions

subtext (>= 0.0.0)

Security releases

Not available

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

This package is not actively maintained and has been moved to @hapi/subtext where version 6.1.2.

Frequently Asked Questions

What is GHSA-2MVQ-XP48-4C77? GHSA-2MVQ-XP48-4C77 is a high-severity uncontrolled resource consumption vulnerability in subtext (npm), affecting versions >= 0.0.0. No fixed version is listed yet. Crafted input forces the application to consume excessive CPU, memory, or other resources, degrading or denying service.
Which versions of subtext are affected by GHSA-2MVQ-XP48-4C77? subtext (npm) versions >= 0.0.0 is affected.
Is there a fix for GHSA-2MVQ-XP48-4C77? No fixed version is listed for GHSA-2MVQ-XP48-4C77 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is GHSA-2MVQ-XP48-4C77 exploitable, and should I be worried? Whether GHSA-2MVQ-XP48-4C77 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-2MVQ-XP48-4C77 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-2MVQ-XP48-4C77? No fixed version is listed yet. In the interim: Apply input size limits and request rate limiting. Reject input that exceeds reasonable bounds before processing begins.