This page was not yet optimized for use on mobile devices.
CVE-2026-4202
Data
| Vulnerability ID | CVE-2026-4202 |
|---|---|
| Published on | 17.03.2026 09:16 |
| Severity | MEDIUM |
Vulnerable configurations
- cpe:2.3:a:ayacoo:redirect_tab:1.0.0:*:*:*:*:typo3:*:*, cpe:2.3:a:ayacoo:redirect_tab:1.1.0:*:*:*:*:typo3:*:*, cpe:2.3:a:ayacoo:redirect_tab:2.0.0:*:*:*:*:typo3:*:*, cpe:2.3:a:ayacoo:redirect_tab:2.0.1:*:*:*:*:typo3:*:*, cpe:2.3:a:ayacoo:redirect_tab:2.1.0:*:*:*:*:typo3:*:*, cpe:2.3:a:ayacoo:redirect_tab:2.1.1:*:*:*:*:typo3:*:*
-
cpe:2.3:a:ayacoo:redirect_tab:3.0.0:*:*:*:*:typo3:*:*,
cpe:2.3:a:ayacoo:redirect_tab:3.0.1:*:*:*:*:typo3:*:*,
cpe:2.3:a:ayacoo:redirect_tab:3.1.0:*:*:*:*:typo3:*:*,
cpe:2.3:a:ayacoo:redirect_tab:3.1.1:*:*:*:*:typo3:*:*,
…
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.