Skip to main content
VulnerabilityPublished Updated

CVE-2026-54279: aiohttp · Host-Only Cookies Become Domain Cookies After CookieJar Persistence

Affects twtxtSource GCVE Database

0
Compare
Authoritative record:CVE-2026-54279· Low 1.3

Not known to be exploited · CVSS 1.3 Low : upgrade to 1.3.1_10 when convenient.

Data as of 4 Nov 2026, 06:59 UTC

CVSS 4.0 base score
1.3Low
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.3.1_10
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:N/SC:L/SI:N/SA:N/E:U

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Jun 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 3 Nov 2026.

What to do

Upgrade twtxt to 1.3.1_10.

Affected software

ProductAffectedFixed in
Homebrewtwtxtpkg:brew/twtxtOther threatsAffected
  • >=1.2.1 <1.3.1_10
Fixed in
  • 1.3.1_10

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

AI-suggested

Upgrade aiohttp to version 1.3.1_10 or later where this issue is fixed. Applying the official patch resolves the loss of host-only status on persisted cookies. No other mitigation is required as the patch fully addresses the vulnerability.

Description

A vulnerability in aiohttp's CookieJar causes host-only cookies saved to disk and later restored to lose their host-only status. This results in these cookies being sent to subdomains where they should not be sent, potentially exposing sensitive cookie data. The issue affects versions from 1.2.1 up to but not including 1.3.1_10. A patch is available in version 1.3.1_10 that addresses this flaw.

References

Community reviews

Loading reviews…