This page was not yet optimized for use on mobile devices.
CVE-2026-42221
Data
| Vulnerability ID | CVE-2026-42221 |
|---|---|
| Published on | 04.05.2026 21:16 |
| Severity | CRITICAL |
Vulnerable configurations
-
cpe:2.3:a:nginxui:nginx_ui:2.0.0:-:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta1:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta10:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta10_patch:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta11:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta12:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta13:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta13_patch:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta13-patch:*:*:*:*:*:*,
cpe:2.3:a:nginxui:nginx_ui:2.0.0:beta14:*:*:*:*:*:*,
…
Vulnerable certificates
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.