← Search results
CVE-LINKED INVENTORY46 SECURITY RECORDS
aio-libs
aiohttp
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-69244 | 3 Aug 2026 | < 3.14.3 | 3.14.3. | Update reference ↗ |
| CVE-2026-69243 | 3 Aug 2026 | < 3.14.2 | 3.14.2. | Update reference ↗ |
| CVE-2026-59881 | 30 Jul 2026 | < 3.14.2 | 3.14.2. | Update reference ↗ |
| CVE-2026-54273 | 22 Jun 2026 | < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54280 | 22 Jun 2026 | aiohttp: < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54278 | 22 Jun 2026 | < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54277 | 22 Jun 2026 | < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54276 | 22 Jun 2026 | aiohttp: < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54275 | 22 Jun 2026 | < 3.14.1 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-54274 | 22 Jun 2026 | < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-54279 | 22 Jun 2026 | < 3.14.1 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-50269 | 22 Jun 2026 | < 3.14.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-47265 | 2 Jun 2026 | < 3.14.0 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34993 | 2 Jun 2026 | aiohttp: < 3.14.0 | RHSA-2026:59135: Red Hat Ansible Automation Platform 2.5 for RHEL 8, Red Hat Ansible Automation Platform 2.5 for RHEL 9 | Update reference ↗ |
| CVE-2026-34525 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34520 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34519 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34518 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34517 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34516 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34515 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34514 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-22815 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34513 | 1 Apr 2026 | < 3.13.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-69230 | 5 Jan 2026 | aiohttp: < 3.13.3 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2025-69229 | 5 Jan 2026 | aiohttp: < 3.13.3 | 3.13.3. | Update reference ↗ |
| CVE-2025-69228 | 5 Jan 2026 | aiohttp: < 3.13.3 | 3.13.3. | Update reference ↗ |
| CVE-2025-69227 | 5 Jan 2026 | aiohttp: < 3.13.3 | 3.13.3. | Update reference ↗ |
| CVE-2025-69225 | 5 Jan 2026 | aiohttp: < 3.13.3 | 3.13.3. | Update reference ↗ |
| CVE-2025-69226 | 5 Jan 2026 | aiohttp: < 3.13.3 | 3.13.3. | Update reference ↗ |
| CVE-2025-69224 | 5 Jan 2026 | aiohttp: < 3.13.3 | 3.13.3. | Update reference ↗ |
| CVE-2025-69223 | 5 Jan 2026 | aiohttp: < 3.13.3 | RHSA-2026:1497: Red Hat Ansible Automation Platform 2.4 for RHEL 8, Red Hat Ansible Automation Platform 2.4 for RHEL 9 | Update reference ↗ |
| CVE-2025-53643 | 14 Jul 2025 | < 3.12.14 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2024-52304 | 18 Nov 2024 | < 3.10.11 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2024-52303 | 18 Nov 2024 | >= 3.10.6, < 3.10.11 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-42367 | 9 Aug 2024 | >= 3.10.0b1, < 3.10.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-30251 | 2 May 2024 | < 3.9.4 | 3.9.4. | Update reference ↗ |
| CVE-2024-27306 | 18 Apr 2024 | < 3.9.4 | For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 For the update to take effect, all applications using Jinja2 must be restarted. | Update reference ↗ |
| CVE-2024-23334 | 29 Jan 2024 | < 3.9.2 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2024-23829 | 29 Jan 2024 | < 3.9.2 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2023-49081 | 30 Nov 2023 | < 3.9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-49082 | 29 Nov 2023 | < 3.9.0 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2023-47627 | 14 Nov 2023 | < 3.8.6 | Red Hat Ansible Automation Platform | Update reference ↗ |
| CVE-2023-47641 | 14 Nov 2023 | < 3.8.0 | 3.8.0 | Update reference ↗ |
| CVE-2023-37276 | 19 Jul 2023 | < 3.8.5 | 3.8.5. | Update reference ↗ |
| CVE-2021-21330 | 26 Feb 2021 | < 3.7.4 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.