Skip to content

← Actionable
Low, CVSS 3.7amended

string-math's string-math.js vulnerability can cause Regex Denial of Service (ReDoS)

CVE-2025-45143GHSA-994j-5c83-r424

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • npm string-math

    Affected
    <= 1.2.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.7 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS
  • CVE-2025-45143: 0.43% estimated exploitation activity in the next 30 days; percentile 37.20 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

string-math v1.2.2 was discovered to contain a Regex Denial of Service (ReDoS) which is exploited via a crafted input.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-994j-5c83-r424

  2. Revision 1 · created ·

    Published from osv record GHSA-994j-5c83-r424

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-45143

Advisory: string-math's string-math.js vulnerability can cause Regex Denial of Service (ReDoS)
IDs: CVE-2025-45143, GHSA-994j-5c83-r424
Record: https://patchnext.com/advisories/cve-2025-45143 (revision 2, source checked 26 Oct 2026, 12:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm string-math: affected <= 1.2.2

## Suggested inspection (read-only)
- `npm ls string-math --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on string-math.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-994j-5c83-r424 (OSV record GHSA-994j-5c83-r424 lists affected ranges: npm string-math >=0 <=1.2.2)
- Verified: https://github.com/advisories/GHSA-994j-5c83-r424 (GitHub-reviewed advisory GHSA-994j-5c83-r424 lists affected ranges: npm string-math >=0 <=1.2.2)

Commands are suggestions: review each one before running it.

Loading voting…