jsx-slack insufficient patch for CVE-2021-43838 ReDoS
CVE-2021-43843GHSA-hp68-xhvj-x6j6
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (jsx-slack 4.5.2), redeploy, then verify what is actually installed.
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 jsx-slack
- Affected
- < 4.5.2
- Fixed in
- 4.5.2
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-hp68-xhvj-x6j6 lists affected ranges: npm jsx-slack >=0 <4.5.2 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-hp68-xhvj-x6j6 lists affected ranges: npm jsx-slack >=0 <4.5.2
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 5.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- EPSS
- CVE-2021-43843: 1.98% estimated exploitation activity in the next 30 days; percentile 80.56 (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.
We found the patch for CVE-2021-43838 in jsx-slack v4.5.1 is insufficient to save from Regular Expression Denial of Service (ReDoS) attack. This vulnerability affects to jsx-slack v4.5.1 and earlier versions. Impact If attacker can put a lot of JSX elements into <blockquote tag with including multibyte characters, an internal regular expression for escaping characters may consume an excessive amount of computing resources. v4.5.1 has released by passing the test against ASCII characters but missed the case of multibyte characters. https://github.com/yhatt/jsx-slack/security/advisories/GHSA-55xv-f85c-248q Patches jsx-slack v4.5.2 has updated regular expressions for escaping blockquote characters to prevent catastrophic backtracking. It is also including an updated test case to confirm rendering multiple tags in <blockquote with multibyte characters. References - https://github.com/yhatt/jsx-slack/commit/46bc88391d89d5fda4ce689e18ca080bcdd29ecc Credits Thanks to @hieki for finding out…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-hp68-xhvj-x6j6
- Revision 1 · created ·
Published from osv record GHSA-hp68-xhvj-x6j6
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-2021-43843 Advisory: jsx-slack insufficient patch for CVE-2021-43838 ReDoS IDs: CVE-2021-43843, GHSA-hp68-xhvj-x6j6 Record: https://patchnext.com/advisories/cve-2021-43843 (revision 2, source checked 26 Oct 2026, 12:17 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: jsx-slack 4.5.2. A vendor fix does not mean a deployment is fixed. ## Affected components - npm jsx-slack: affected < 4.5.2; fixed in 4.5.2 ## Suggested inspection (read-only) - `npm ls jsx-slack --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on jsx-slack. - 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-hp68-xhvj-x6j6 (OSV record GHSA-hp68-xhvj-x6j6 lists affected ranges: npm jsx-slack >=0 <4.5.2 (fixed)) - Verified: https://github.com/advisories/GHSA-hp68-xhvj-x6j6 (GitHub-reviewed advisory GHSA-hp68-xhvj-x6j6 lists affected ranges: npm jsx-slack >=0 <4.5.2) Commands are suggestions: review each one before running it.
Loading voting…