Skip to main content
VulnerabilityPublished

CVE-2026-111748: AIOHTTP · Absolute-form request targets can spoof Request.scheme

Affects lexiconSource GCVE Database

0
Compare
Authoritative record:CVE-2026-111748· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 3.25.2_5 when convenient.

Data as of 30 Oct 2026, 07:44 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.25.2_5
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade lexicon to 3.25.2_5.

Affected software

ProductAffectedFixed in
Homebrewlexiconpkg:brew/lexiconOther threatsAffected
  • >=3.25.2_3 <3.25.2_5
Fixed in
  • 3.25.2_5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

An official patch is available in aiohttp version 3.25.2_5 and should be applied to remediate this vulnerability. As a temporary workaround, deploying a Web Application Firewall (WAF) rule to reject absolute-form HTTP requests can help mitigate the risk, since legitimate requests typically do not use this form except for proxy scenarios.

Description

CVE-2026-111748 is a vulnerability in aiohttp where an attacker can spoof the Request.scheme attribute by sending an absolute-form HTTP request. This can mislead applications relying on this attribute for security decisions, such as determining whether a connection is encrypted. The issue affects versions >=3.25.2_3 and <3.25.2_5. A fix is available in version 3.25.2_5. A workaround is to use a WAF rule to block absolute-form requests, which are typically only legitimate for proxy usage.

References

Community reviews

Loading reviews…