This page was not yet optimized for use on mobile devices.
CVE-2026-41432
Data
| Vulnerability ID | CVE-2026-41432 |
|---|---|
| Published on | 08.05.2026 23:16 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:newapi:new_api:0.0.4:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.0.5:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.0.6:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.0.7:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.0.8:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.1.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.1.1:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.1.2:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.1.3:*:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.1.3.1:*:*:*:*:*:*:*,
…
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.