CVE-2026-111748 aio-libs CVE debrief

Who should care

Python developers and security teams using AIOHTTP should assess exposure and apply version 3.14.4 or later. This includes reviewing current AIOHTTP deployments, assessing potential impact, and implementing necessary updates or mitigations. Security teams should also monitor for potential security implications and verify that security decisions are not solely based on Request.scheme.

Why it matters

CVE-2026-111748 AIOHTTP vulnerability requires attention from Python developers and security teams to prevent potential security implications.

• Spoofing of Request.scheme could lead to incorrect security decisions
• Potential for treating unencrypted connections as encrypted or vice versa
• Need for verification of AIOHTTP version and potential exposure

Technical summary

AIOHTTP vulnerability allows an attacker to spoof Request.scheme, potentially tricking applications into treating an unencrypted connection as encrypted or vice versa. This issue arises from AIOHTTP's handling of absolute-form request targets. Applications using Request.scheme for security decisions can be affected. The vulnerability is fixed in AIOHTTP version 3.14.4. Developers should update to this version or later to mitigate the issue. The vulnerability has a CVSS score of 6.3 and is classified as MEDIUM severity.

Defensive priority

Medium priority for Python developers and security teams using AIOHTTP

Recommended defensive actions

• Review and apply AIOHTTP version 3.14.4 or later
• Assess and update affected systems
• Monitor for potential security implications
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and source item provide details on the vulnerability in AIOHTTP. The NVD entry is currently UNVERIFIED. Evidence from the CVE Program and NVD suggests that AIOHTTP versions prior to 3.14.4 are affected. Developers should verify their AIOHTTP versions and update to 3.14.4 or later. Additional verification steps include reviewing system configurations and ensuring that security decisions are not solely based on Request.scheme.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.