# CVE-2026-111063: AIOHTTP: Secure attribute not enforced for shared cookie

> Attackers can force secure cookies to be sent over unencrypted connections, exposing sensitive session data to interception.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Oct 2026
- **Updated:** 22 Oct 2026
- **Also known as:** AZL-109878, DEBIAN-CVE-2026-111063, ECHO-4123-2474-2218, GHSA-494j-54xm-rwp3, MINI-4rq8-273p-mvpf, MINI-f7j4-7rw4-8q6h, MINI-x2j9-v4c9-3hmg, UBUNTU-CVE-2026-111063

## What is CVE-2026-111063?

CVE-2026-111063 is a medium-severity vulnerability in aio-libs aiohttp, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the Secure attribute for a shared cookie is not enforced. An attacker can consequently cause a shared cookie marked Secure to be sent with an unencrypted request. This issue is fixed in version 3.14.4.

Weakness: CWE-311 (Missing Encryption of Sensitive Data), CWE-1004 (Sensitive Cookie Without 'HttpOnly' Flag)

## Which versions are affected by CVE-2026-111063?

2 open source packages ship an affected version, including aiohttp.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aiohttp` | PyPI | All versions | 3.14.4 |
| `aiohttp` | PyPI | All versions | 3.14.4 |

## How do I fix CVE-2026-111063?

Upgrade aiohttp to 3.14.4 or later.

## Is CVE-2026-111063 being exploited?

There is no known exploitation of CVE-2026-111063 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-111063 and fix it if it is affected.

What it is: CVE-2026-111063 is a medium-severity vulnerability in aio-libs aiohttp, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-111063 in the wild and no public exploit code.

Affected packages and fixed versions:
- aiohttp (PyPI): affected all versions; fixed in 3.14.4
- aiohttp (PyPI): affected all versions; fixed in 3.14.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-111063/ (Markdown: https://insights.sbomify.com/CVE-2026-111063/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-111063
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-111063
- OSV: https://osv.dev/vulnerability/CVE-2026-111063

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-111063/
Summaries are generated and may contain mistakes; the official description above is the record.