npm package report

Is async-h1 safe?

1 known vulnerability, worst severity MODERATE.

cvss
5.0

how bad it is if exploited, out of 10

epss
0.80%

chance of exploitation in the next 30 days

xyz score
not scored

CyberXYZ composite, out of 10

fig. 01 — GHSA-c8rq-crxj-mj9m, the advisory selected below

// advisories

GHSA-c8rq-crxj-mj9m

MODERATECVE-2020-36202

This vulnerability affects any webserver that uses async-h1 behind a reverse proxy, including all such Tide applications.

Affected
>=0, <2.3.0
Fixed in
2.3.0
Weakness
CWE-444
Published
2022-05-24
Source
github

GHSANVDMITRE

// dependencies

0 direct

Sign in for dependency paths and remediation

// ai model usage

Tracked for PyPI packages. HuggingFace models declare Python dependencies, so npm packages are not covered.

Checked 2026-09-22 at 01:44 UTC. The most recent advisory here was published 2022-05-24. Updated continuously from NVD, GHSA, OSV and CNA feeds.

Think a verdict here is wrong? Tell us — we respond within 2 business days.
Is async-h1 safe? npm package security report | CyberXYZ