This page was not yet optimized for use on mobile devices.
CVE-2026-44166
Data
| Vulnerability ID | CVE-2026-44166 |
|---|---|
| Published on | 12.05.2026 18:17 |
| Severity | HIGH |
Vulnerable configurations
-
cpe:2.3:a:pocketbase:pocketbase:0.1.0:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.1.1:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.1.2:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.0:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.1:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.2:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.3:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.4:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.5:*:*:*:*:go:*:*,
cpe:2.3:a:pocketbase:pocketbase:0.2.6:*:*:*:*:go:*:*,
…
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.