Regular Expression Denial of Service in jadedown

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

• CVE-2016-10520: 1.13% estimated exploitation activity in the next 30 days; percentile 66.50 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The jadedown package is affected by a regular expression denial of service vulnerability when certain types of user input are passed in. Proof of concept Results demonstrating blocking for 5 seconds using only 48 characters. Timeline - October 24, 2015 - Vulnerability Identified - October 24, 2015 - Maintainers Notified - October 25, 2015 - Response from Maintainers with intent to fix - January 5, 2016 - Advisory Published - January 11, 2016 - CVE Requested Recommendation This package is not actively maintained, and has not seen an update since 2011. The package also provides unique functionality in the form of a templating language that is not available elsewhere. If this package is used to process user input, the best available mitigation is to refactor the dependent application to not make use of this module.

Published by the source

18 Feb 2019, 23:38 UTC

Last modified by the source

8 Nov 2023, 03:58 UTC

Source last checked

26 Oct 2026, 12:26 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-6354-6mhv-mvv5

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-6354-6mhv-mvv5

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

# Patch Next advisory brief: CVE-2016-10520

Advisory: Regular Expression Denial of Service in jadedown
IDs: CVE-2016-10520, GHSA-6354-6mhv-mvv5
Record: https://patchnext.com/advisories/cve-2016-10520 (revision 2, source checked 26 Oct 2026, 12:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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 jadedown: affected <= 0.0.3

## Suggested inspection (read-only)
- `npm ls jadedown --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 jadedown.
- 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-6354-6mhv-mvv5 (OSV record GHSA-6354-6mhv-mvv5 lists affected ranges: npm jadedown >=0 <=0.0.3)
- Verified: https://github.com/advisories/GHSA-6354-6mhv-mvv5 (GitHub-reviewed advisory GHSA-6354-6mhv-mvv5 lists affected ranges: npm jadedown >=0 <=0.0.3)

Commands are suggestions: review each one before running it.