GHSA-x5rw-q4pp-hg5g: devalue StringifyAsync Can Cause An Unhandled Vulnerability

HIGH
CWE-755 CWE-248
Published
Advisory Summary

GHSA-x5rw-q4pp-hg5g is a HIGH stringifyasync can cause an unhandled vulnerability (CWE-755: Improper Handling of Exceptional Conditions) affecting devalue libraries in the npm ecosystem. The issue involves stringifyasync can cause an unhandled rejection despite a caught returned promise. Remediation is available by upgrading affected packages to version 5.9.3.

GHSA-x5rw-q4pp-hg5g at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-x5rw-q4pp-hg5g
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-755: Improper Handling of Exceptional Conditions
Affected Product devalue
Package Ecosystem npm
Published Date
Last Updated

How to Fix GHSA-x5rw-q4pp-hg5g

To remediate this vulnerability, upgrade all affected devalue dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

devalue fixed: 5.9.3
npm install devalue@5.9.3
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls devalue

How to Check if You Are Affected

To determine whether your Node.js application is affected by GHSA-x5rw-q4pp-hg5g, inspect your project dependencies using npm:

npm ls devalue

Analyze the terminal output to locate any version of devalue in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.9.3), your application is affected.

Note: The npm ls devalue command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-755: Improper Handling of Exceptional Conditions, where the product does not handle or incorrectly handles an exceptional condition. In devalue, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned `stringifyAsync` promise. Under Node's default unhandled-rejection behavior this can terminate the process. Applications whose asynchronous failures/timing can be influenced by requests are potentially exposed. This is essentially impossible to exploit, and is much more likely to surface as a developer-introduced bug.

GHSA-x5rw-q4pp-hg5g Affected devalue Versions

1 component(s)
Fixed Versions:
5.9.3
Product / Package Ecosystem Affected Versions Fixed Version
devalue
npm
≥ 5.8.0
< 5.9.3
5.9.3

References

Frequently Asked Questions

What is GHSA-x5rw-q4pp-hg5g?
GHSA-x5rw-q4pp-hg5g is a security vulnerability in devalue involving stringifyAsync can cause an unhandled rejection despite a caught returned promise under CWE-755: Improper Handling of Exceptional Conditions.
Which devalue versions are affected?
Affected versions include releases prior to 5.9.3 across affected packages: devalue.
What version fixes GHSA-x5rw-q4pp-hg5g?
Upgrading to 5.9.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is devalue affected?
Yes, devalue is affected in releases prior to 5.9.3. Upgrade your dependency to 5.9.3 or later.
What CWE is associated with GHSA-x5rw-q4pp-hg5g?
GHSA-x5rw-q4pp-hg5g is classified under CWE-755: Improper Handling of Exceptional Conditions (The product does not handle or incorrectly handles an exceptional condition.).
How can I check npm dependencies for GHSA-x5rw-q4pp-hg5g?
Run the dependency tree command: 'npm ls devalue'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-x5rw-q4pp-hg5g",
  "modified" : "2026-10-01T15:15:13Z",
  "published" : "2026-10-01T15:15:13Z",
  "aliases" : [ ],
  "summary" : "devalue: stringifyAsync can cause an unhandled rejection despite a caught returned promise",
  "details" : "When serializing multiple promises, a later promise can reject before an earlier one settles. An internal rejected promise remains unhandled even if the caller catches the returned `stringifyAsync` promise. Under Node's default unhandled-rejection behavior this can terminate the process. Applications whose asynchronous failures/timing can be influenced by requests are potentially exposed.\n\nThis is essentially impossible to exploit, and is much more likely to surface as a developer-introduced bug.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "devalue"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.8.0"
      }, {
        "fixed" : "5.9.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.9.2"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/sveltejs/devalue/security/advisories/GHSA-x5rw-q4pp-hg5g"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sveltejs/devalue/commit/dae8153e9d7541b975cc4018138d6cebec6c1199"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/sveltejs/devalue"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/sveltejs/devalue/releases/tag/v5.9.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-248", "CWE-755" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-01T15:15:13Z",
    "nvd_published_at" : null
  }
}