react-11.11.4.tgz: 2 vulnerabilities (highest severity is: 6.2)

[mend-bolt-for-github]

Vulnerable Library - react-11.11.4.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (react version)	Remediation Possible**
CVE-2025-27789	Medium	6.2	runtime-7.24.5.tgz	Transitive	11.12.0	❌
CVE-2026-33532	Medium	4.3	yaml-1.10.2.tgz	Transitive	N/A*	❌

*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2025-27789

Vulnerable Library - runtime-7.24.5.tgz

Library home page: https://registry.npmjs.org/@babel/runtime/-/runtime-7.24.5.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• react-11.11.4.tgz (Root Library)
  • ❌ runtime-7.24.5.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

Babel is a compiler for writing next generation JavaScript. When using versions of Babel prior to 7.26.10 and 8.0.0-alpha.17 to compile regular expression named capturing groups, Babel will generate a polyfill for the ".replace" method that has quadratic complexity on some specific replacement pattern strings (i.e. the second argument passed to ".replace"). Generated code is vulnerable if all the following conditions are true: Using Babel to compile regular expression named capturing groups, using the ".replace" method on a regular expression that contains named capturing groups, and the code using untrusted strings as the second argument of ".replace". This problem has been fixed in "@babel/helpers" and "@babel/runtime" 7.26.10 and 8.0.0-alpha.17. It's likely that individual users do not directly depend on "@babel/helpers", and instead depend on "@babel/core" (which itself depends on "@babel/helpers"). Upgrading to "@babel/core" 7.26.10 is not required, but it guarantees use of a new enough "@babel/helpers" version. Note that just updating Babel dependencies is not enough; one will also need to re-compile the code. No known workarounds are available.

Publish Date: 2025-03-11

URL: CVE-2025-27789

CVSS 3 Score Details (6.2)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: Low
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-968p-4wvh-cqc8

Release Date: 2025-03-11

Fix Resolution (@babel/runtime): 7.26.10

Direct dependency fix Resolution (@emotion/react): 11.12.0

Step up your Open Source Security Game with Mend here

CVE-2026-33532

Vulnerable Library - yaml-1.10.2.tgz

JavaScript parser and stringifier for YAML

Library home page: https://registry.npmjs.org/yaml/-/yaml-1.10.2.tgz

Path to dependency file: /client/package.json

Path to vulnerable library: /client/package.json

Dependency Hierarchy:

• react-11.11.4.tgz (Root Library)
  • babel-plugin-11.11.0.tgz
    • babel-plugin-macros-3.1.0.tgz
      • cosmiconfig-7.1.0.tgz
        • ❌ yaml-1.10.2.tgz (Vulnerable Library)

Found in HEAD commit: 8233eb35f209c5b712ecc7d96645a2de905e8282

Found in base branch: main

Vulnerability Details

"yaml" is a YAML parser and serialiser for JavaScript. Parsing a YAML document with a version of "yaml" on the 1.x branch prior to 1.10.3 or on the 2.x branch prior to 2.8.3 may throw a RangeError due to a stack overflow. The node resolution/composition phase uses recursive function calls without a depth bound. An attacker who can supply YAML for parsing can trigger a "RangeError: Maximum call stack size exceeded" with a small payload (~2–10 KB). The "RangeError" is not a "YAMLParseError", so applications that only catch YAML-specific errors will encounter an unexpected exception type. Depending on the host application's exception handling, this can fail requests or terminate the Node.js process. Flow sequences allow deep nesting with minimal bytes (2 bytes per level: one "[" and one "]"). On the default Node.js stack, approximately 1,000–5,000 levels of nesting (2–10 KB input) exhaust the call stack. The exact threshold is environment-dependent (Node.js version, stack size, call stack depth at invocation). Note: the library's "Parser" (CST phase) uses a stack-based iterative approach and is not affected. Only the compose/resolve phase uses actual call-stack recursion. All three public parsing APIs are affected: "YAML.parse()", "YAML.parseDocument()", and "YAML.parseAllDocuments()". Versions 1.10.3 and 2.8.3 contain a patch.

Publish Date: 2026-03-26

URL: CVE-2026-33532

CVSS 3 Score Details (4.3)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: None
  • Availability Impact: Low

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-03-25

Fix Resolution: https://github.com/eemeli/yaml.git - v1.10.3,https://github.com/eemeli/yaml.git - v2.8.3

Step up your Open Source Security Game with Mend here