OpenResty ↗
Summary iPlain-English security verdict for OpenResty, generated from its current health score, actively-exploited vulnerabilities, and latest supported version.
OpenResty currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2023-44487. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
Disclosure trend iNew CVEs published for OpenResty each year (NVD). A higher bar means more disclosures that year — more scrutiny, not necessarily less safe.
Patch priority — what to act on iThe issues to fix first — actively exploited (CISA KEV) first, then by exploitation probability (EPSS), then severity. Each row's "→ fixed in" is the earliest version that patches it; "see advisory" means no fixed version is published.
Most urgent first — actively exploited, then likeliest to be exploited.
CVE-2023-44487 HIGH exploited Uncontrolled resource consumption EPSS 100% → fixed in 1.21.4.3Get alerted about OpenResty
Be emailed the moment OpenResty gets a newly exploited vulnerability (CISA KEV) or a release reaches end of life. Free · double opt-in · unsubscribe anytime.
We email only on real events for OpenResty — no marketing, no sharing, and we never know what you run. Track your whole stack →
Frequently asked
Is OpenResty safe and patched?
OpenResty currently scores 20/100 — critical, with active exploitation. 1 of its known vulnerability is being actively exploited in the wild (CISA KEV), including CVE-2023-44487. Upgrade immediately and review your exposure to the actively-exploited CVEs below.
What should I do about OpenResty now?
Review the patch-priority list, apply the available fixes (or move to the latest release), and confirm against OpenResty's official advisory. Some issues are under active exploitation, so treat this as urgent.
lifecycle unknown — needs latest supported version
Informational only, from public data (NVD · CISA KEV · EPSS · endoflife.date), and can lag or miss vendor-specific fixes. Always confirm against OpenResty's official advisory before you patch or upgrade — OpenResty official site ↗