This page was not yet optimized for use on mobile devices.
CVE-2026-32879
Data
| Vulnerability ID | CVE-2026-32879 |
|---|---|
| Published on | 23.03.2026 20:16 |
| Severity | MEDIUM |
Vulnerable configurations
-
cpe:2.3:a:newapi:new_api:0.10.0:-:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.0:alpha1:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.0:alpha2:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.0:alpha3:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.1:-:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.1:alpha1:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.1:alpha2:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.1:alpha3:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.1:alpha4:*:*:*:*:*:*,
cpe:2.3:a:newapi:new_api:0.10.1:alpha5:*:*:*:*:*:*,
…
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.