This page was not yet optimized for use on mobile devices.
CVE-2026-44230
Data
| Vulnerability ID | CVE-2026-44230 |
|---|---|
| Published on | 20.07.2026 20:16 |
| Severity | MEDIUM |
Vulnerable configurations
- cpe:2.3:a:bestpractical:request_tracker:5.0.4:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.5:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.6:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.7:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.8:*:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:5.0.9:*:*:*:*:*:*:*
- cpe:2.3:a:bestpractical:request_tracker:6.0.0:-:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:6.0.0:beta1:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:6.0.0:beta2:*:*:*:*:*:*, cpe:2.3:a:bestpractical:request_tracker:6.0.2:*:*:*:*:*:*:*
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.