Skip to main content
VulnerabilityPublished Updated

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

Affects modalSource GCVE Database

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

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

Data as of 18 Nov 2026, 18:20 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.6.2
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 17 Nov 2026.

What to do

Upgrade modal to 1.6.2.

Affected software

ProductAffectedFixed in
Homebrewmodalpkg:brew/modalOther threatsAffected
  • >=1.5.3 <1.6.2
Fixed in
  • 1.6.2

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

AI-suggested

A fix is available in AIOHTTP version 1.6.2; upgrading to this version or later is recommended. As a temporary mitigation, deploying a Web Application Firewall (WAF) rule to reject absolute-form HTTP requests can reduce risk, since such requests are typically only legitimate when used by proxies.

Description

AIOHTTP versions 1.5.3 up to but not including 1.6.2 contain a vulnerability where an attacker can send an absolute-form HTTP request to spoof the Request.scheme attribute. This can mislead applications relying on this attribute for security decisions, potentially causing them to misinterpret whether a connection is encrypted. The issue is fixed in version 1.6.2. A workaround involves using a WAF rule to block absolute-form requests, which are typically only legitimate for proxy use.

References

Community reviews

Loading reviews…