fix(deps): update security fixes [security] #111

Open
renovate-bot wants to merge 1 commit from renovate/security into main
Collaborator

This PR contains the following updates:

Package Change Age Confidence
aiohttp ==3.14.3 → ==3.14.4 age confidence
pygments (changelog) ==2.19.1 → ==2.20.0 age confidence
unstructured ==0.24.0 → ==0.24.1 age confidence

AIOHTTP: Base64 multipart parts bypass client_max_size

CVE-2026-128127 / GHSA-24c4-3p7v-29cm / PYSEC-2026-4394

More information

Details

Summary

When reading a multipart part with Content-Transfer-Encoding: base64, BodyPartReader.read_chunk() kept reading until the chunk length was a multiple of 4, with no byte limit. A part with a short Content-Length, or a long run of whitespace, could cause the entire remaining body to be read into memory within a single call before any size check, or spin on the event loop.

Impact

An attacker could bypass client_max_size to cause excessive memory use, or block the event loop, with a specially crafted multipart request to any handler that reads multipart data.


Patch: github.com/aio-libs/aiohttp@a555ab698e

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade

CVE-2026-128130 / GHSA-28qf-cpwq-vmc2

More information

Details

Summary

When the pipelined request queue was full, the pure-Python parser stored the unparsed remainder internally and also returned it to the caller. After a handler declined an upgrade request, the buffered data was re-fed, so the buffer grew with each handled request and already-handled requests were dispatched to the application again.

Impact

If users are using the Python parser (AIOHTTP_NO_EXTENSIONS, or not a standard wheel installed), an attacker could cause excessive memory use and cause pipelined requests to be processed more than once.

Workaround

Switch to the default C parser.


Patch: github.com/aio-libs/aiohttp@47babd8c23

Severity

  • CVSS Score: 8.3 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


aiohttp: Multiple instances of excessive or unbounded memory/CPU use

CVE-2026-123817 / GHSA-2g87-pp6c-29x5 / PYSEC-2026-4389

More information

Details

Summary

While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one bytes object per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory than max_msg_size allows.

Impact

An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments.

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: WebSocket max_msg_size bypass via integer overflow

CVE-2026-128128 / GHSA-3rp8-rxj8-mvjw / PYSEC-2026-4395

More information

Details

Summary

The max_msg_size check in the WebSocket reader added the declared frame length to the size of the partial message already buffered. In the C extension this addition is 64-bit arithmetic, so a declared length close to 2**63 overflowed and the check passed.

Impact

An attacker could bypass max_msg_size and cause unbounded memory use by streaming an oversized WebSocket message after a small non-final fragment.

Workaround

If unable to upgrade, the Python reader is unaffected and can be used with AIOHTTP_NO_EXTENSIONS=1.


Patch: github.com/aio-libs/aiohttp@8cfbe9abe5

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


CVE-2026-111063 / GHSA-494j-54xm-rwp3 / PYSEC-2026-4365

More information

Details

Summary

The Secure attribute was not being enforced for the shared cookie.

Impact

It may be possible to send a shared cookie marked Secure through an unencrypted request.

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: 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

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


CVE-2026-128125 / GHSA-5pv8-vvhc-h7jv / PYSEC-2026-4392

More information

Details

Summary

Set-Cookie parsing created additional cookies from unrecognised name=value attributes, and CookieJar had no limit on the number of cookies stored or sent. A server could make the client store a very large number of cookies and generate very large Cookie headers.

Impact

A malicious server could cause excessive memory and CPU use in a client, repeated on every redirect, and cause later requests to the same domain to build an excessively large Cookie header.


Patch: github.com/aio-libs/aiohttp@6963ee0bef

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: WebSocket receive queue limits bypassed by small or compressed messages

CVE-2026-128132 / GHSA-5rmc-48h2-hvcm

More information

Details

Summary

The WebSocket reader continued parsing frames already received after the receive queue had paused the transport, and empty messages were not counted towards the queue size. With permessage-deflate, a single read of compressed frames could add many megabytes of decompressed messages to the queue.

Impact

An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending many small or compressed messages faster than the application consumes them.


Patch: github.com/aio-libs/aiohttp@0ae507423f

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


aiohttp server lacks an initial request/header timeout

CVE-2026-111064 / GHSA-5wr8-gcqf-gqf3 / PYSEC-2026-4366

More information

Details

Summary

The keepalive timeout was not used during the initial portion of a request.

Impact

An attacker could keep an idle connection open indefinitely before sending any data.

Workaround

Use a reverse proxy (as recommended for all production deployments) with sensible keepalive limits.

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Connector pool exhaustion via Max-Age overflow

CVE-2026-111065 / GHSA-6cjc-53gc-5rqm / PYSEC-2026-4367

More information

Details

Summary

An overflow in Max-Age processing can skip closing a connection.

Impact

An attacker may be able to exhaust the connection pool temporarily, until garbage collection resolves the connections.

Severity

  • CVSS Score: 6.9 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: File descriptor exhaustion in multipart requests

CVE-2026-111066 / GHSA-9xw5-w5jj-pvcg / PYSEC-2026-4368

More information

Details

Summary

An attacker can exhaust file descriptors with specially crafted multipart requests.

Impact

If a handler uses Request.post(), it may be possible for an attacker to use an unlimited number of file descriptors, potentially resulting in resource exhaustion.

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Absolute-form request targets can spoof Request.scheme

CVE-2026-111748 / GHSA-f9xw-jh8m-3mwq / PYSEC-2026-4369

More information

Details

Summary

An attacker sending an absolute-form request can spoof the scheme used.

Impact

If user code depends on the Request.scheme attribute for anything security related, an attacker may be able to circumvent this logic, tricking the application into thinking a connection is encrypted when it is not, or vice versa.

Workaround

A WAF rule to reject absolute-form requests (legitimate requests should only use this form for proxies).

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: 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

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


CVE-2026-111749 / GHSA-gx76-c99x-2c96 / PYSEC-2026-4370

More information

Details

Summary

A subdomain can remove the Host-Only flag from an existing cookie to a parent domain.

Impact

A user accessing untrusted subdomains could see their Host-Only protections stripped from cookies. Given most usecases won't reflect these cookies to a browser, the impact is limited.

Severity

  • CVSS Score: 2.3 / 10 (Low)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Concatenated compressed streams cause excessive CPU use

CVE-2026-128131 / GHSA-h4cc-hm5h-fmm9

More information

Details

Summary

When decompressing a payload made up of many concatenated compressed members (gzip, deflate or zstd), each member was decoded by passing the entire remaining input to a new decompressor, resulting in quadratic CPU time. Empty members produce no output, so client_max_size and output backpressure did not limit the work.

Impact

An attacker could block the event loop of a server with a specially crafted compressed request body or WebSocket message. A malicious server could do the same to a client.


Patch: github.com/aio-libs/aiohttp@d925a80539

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Event loop stall in add_domain() wildcard matching

CVE-2026-128124 / GHSA-jm3w-gw2p-xjfj / PYSEC-2026-4391

More information

Details

Summary

Application.add_domain() compiled each * in a host mask to [^:]*. With two or more wildcards in a mask, matching a long Host header that does not match the mask took polynomial time on the event loop.

Impact

An attacker could stall a server that registers a domain mask with more than one wildcard by sending requests with a long Host header.

Workaround

Use at most one * in a domain mask.


Patch: github.com/aio-libs/aiohttp@c6ac0e44c3

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Pure-Python parser request smuggling

CVE-2026-111750 / GHSA-pqxq-w44r-73xw / PYSEC-2026-4371

More information

Details

Summary

The pure Python parser is vulnerable to an HTTP request smuggling attack.

Impact

If users are using the Python parser (AIOHTTP_NO_EXTENSIONS, or not a standard wheel installed), then an application may be vulnerable to a request smuggling attack.

Workaround

Switch to the default C parser.

Severity

  • CVSS Score: 6.3 / 10 (Medium)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Unbounded buffering of data received during an upgrade request

CVE-2026-128129 / GHSA-pw86-h8fm-j323

More information

Details

Summary

While a request flagged as an upgrade (e.g. a WebSocket handshake) was being handled, all further data received on the connection was buffered with no size limit or flow control until the handler completed.

Impact

An attacker could cause unbounded memory use by streaming data behind an upgrade request to any handler that does not immediately accept or reject the upgrade.


Patch: github.com/aio-libs/aiohttp@3d850ee9b9

Severity

  • CVSS Score: 8.2 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


AIOHTTP: Too many URL-encoded form fields block the event loop

CVE-2026-128126 / GHSA-xgw8-8ccx-rmqh / PYSEC-2026-4393

More information

Details

Summary

Request.post() had no limit on the number of fields in a URL-encoded form body. Inserting a large number of repeated keys into a MultiDict took quadratic time on the event loop.

Impact

An attacker could block the event loop with a form POST within the default client_max_size to any handler that calls Request.post().


Patch: github.com/aio-libs/aiohttp@615fec3d4f

Severity

  • CVSS Score: 8.7 / 10 (High)
  • Vector String: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


CVE-2026-111063 / GHSA-494j-54xm-rwp3 / PYSEC-2026-4365

More information

Details

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.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-111064 / GHSA-5wr8-gcqf-gqf3 / PYSEC-2026-4366

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, keepalive timeout handling is absent during the initial portion of a request. An attacker can keep an idle connection open indefinitely before sending any request data, consuming server connection capacity. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-111065 / GHSA-6cjc-53gc-5rqm / PYSEC-2026-4367

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Max-Age processing can overflow and skip closing a connection. An attacker can consequently exhaust the connection pool temporarily until garbage collection resolves the connections. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-111066 / GHSA-9xw5-w5jj-pvcg / PYSEC-2026-4368

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. From 2.0.0 until 3.14.4, multipart request processing can retain an unbounded number of open file descriptors. An unauthenticated attacker can consequently exhaust file descriptors with specially crafted multipart requests when a handler uses Request.post(). This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-111748 / GHSA-f9xw-jh8m-3mwq / PYSEC-2026-4369

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, an attacker can send an absolute-form request that causes Request.scheme to use attacker-controlled request-target scheme data instead of the connection protocol. Applications that use Request.scheme for security decisions can consequently be tricked into treating an unencrypted connection as encrypted or an encrypted connection as unencrypted. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 6.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-111749 / GHSA-gx76-c99x-2c96 / PYSEC-2026-4370

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Host-Only scope on an existing parent-domain cookie can be removed by a subdomain. A user who accesses an untrusted subdomain can consequently have host-only protections stripped from cookies, although impact is limited when applications do not reflect those cookies to a browser. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 5.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-111750 / GHSA-pqxq-w44r-73xw / PYSEC-2026-4371

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the pure Python parser accepts ambiguous HTTP request framing. An unauthenticated attacker can consequently smuggle requests when an application uses AIOHTTP_NO_EXTENSIONS or otherwise runs without a standard wheel and an intermediary interprets the framing differently. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 6.5 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-123817 / GHSA-2g87-pp6c-29x5 / PYSEC-2026-4389

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by max_msg_size. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-128124 / GHSA-jm3w-gw2p-xjfj / PYSEC-2026-4391

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Application.add_domain() converts every asterisk wildcard in a domain mask into a greedy regular-expression fragment, so a mask containing two or more wildcards can take polynomial time to reject a long Host header that does not match. A remote attacker can repeatedly send such headers to a server configured with a multi-wildcard domain mask and stall the event loop. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-128125 / GHSA-5pv8-vvhc-h7jv / PYSEC-2026-4392

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Set-Cookie parsing treats unrecognized name=value attributes as additional cookies, while CookieJar does not limit the number of cookies stored or sent. A malicious server can make an aiohttp client accumulate a very large cookie set, consume memory and CPU repeatedly across redirects, and construct an excessively large Cookie header for later requests to the same domain. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-128126 / GHSA-xgw8-8ccx-rmqh / PYSEC-2026-4393

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Request.post() does not limit the number of fields in a URL-encoded form body, and inserting many repeated keys into MultiDict takes quadratic time on the event loop. A remote attacker can send a form POST within client_max_size to a handler that calls Request.post() and block the event loop. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-128127 / GHSA-24c4-3p7v-29cm / PYSEC-2026-4394

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, BodyPartReader.read_chunk() processing a multipart part with Content-Transfer-Encoding set to base64 keeps reading until the chunk length is a multiple of four without enforcing a byte limit. A short Content-Length or a long run of whitespace can cause one call to read the remaining body into memory before the size check or spin on the event loop. A remote attacker can send such a multipart request to a handler that reads multipart data and bypass client_max_size. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


CVE-2026-128128 / GHSA-3rp8-rxj8-mvjw / PYSEC-2026-4395

More information

Details

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the C WebSocket reader adds a declared frame length to the size of an already buffered partial message using signed 64-bit arithmetic. A length near two to the power of 63 can overflow, allowing the max_msg_size check to pass. A remote peer can send a small non-final fragment followed by an oversized message and cause unbounded memory consumption. The Python WebSocket reader is unaffected. This issue is fixed in version 3.14.4.

Severity

  • CVSS Score: 7.5 / 10 (High)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching

CVE-2026-4539 / GHSA-5239-wwwm-4pmq / PYSEC-2026-2987

More information

Details

A security flaw has been discovered in pygments before 2.20.0. The impacted element is the function AdlLexer of the file pygments/lexers/archetype.py. The manipulation results in inefficient regular expression complexity. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Severity

  • CVSS Score: 1.9 / 10 (Low)
  • Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching

CVE-2026-4539 / GHSA-5239-wwwm-4pmq / PYSEC-2026-2987

More information

Details

A security flaw has been discovered in pygments before 2.20.0. The impacted element is the function AdlLexer of the file pygments/lexers/archetype.py. The manipulation results in inefficient regular expression complexity. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet.

Severity

  • CVSS Score: 1.9 / 10 (Low)
  • Vector String: CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P

References

This data is provided by OSV and the PyPI Advisory Database (CC-BY 4.0).


unstructured: Stored XSS via unescaped HTML generation

CVE-2026-104250 / GHSA-v5mq-3xhg-98m9

More information

Details

Summary

When unstructured parses an untrusted document and outputs the result as HTML, malicious markup contained in the document (e.g. <img src=x onerror=...>) is left in the output HTML without escaping. When that output is displayed in a browser, the script embedded in the document executes in the viewer's browser.

Details

partition_html(html_parser_version="v2") (and the VLM partitioner) preserve the input document's element tags, attributes, and text into metadata.text_as_html, and elements_to_html() outputs that as an HTML document.

The function that builds HTML on this path, to_html() in unstructured/documents/ontology.py, performs no escaping at all. As a result, event handlers such as onerror / onmouseover / onload originating from the input document are left in the output HTML as-is (literal <script> tags are stripped by the parser, but attribute-based vectors and javascript: URLs are not). In addition, link URLs are not scheme-filtered, so <a href="javascript:..."> is also emitted.

Relevant source: documents/ontology.py (to_html, _construct_attribute_string, _generate_final_html); partition/html/transformations.py (text_as_html = ontology_element.to_html()); partition/html/convert.py (elements_to_html).

PoC

Environment: downloads.unstructured.io/unstructured-io/unstructured:latest, unstructured 0.23.3.

from unstructured.partition.html import partition_html
from unstructured.partition.html.convert import elements_to_html

malicious = ('<body class="Document">'
             '<p class="Paragraph" onmouseover="alert(1)">hello'
             '<img src=x onerror="alert(document.domain)"></p>'
             '<a class="Hyperlink" href="javascript:alert(document.cookie)">click me</a>'
             '</body>')
els = partition_html(text=malicious, html_parser_version="v2")
open("xss_output.html", "w").write(elements_to_html(list(els), no_group_by_page=True))

elements_to_html() output body — the unescaped vectors survive:

<p class="NarrativeText" id="..." onmouseover="alert(1)">
  <p class="Paragraph">hello</p>
  <img class="Image" onerror="alert(document.domain)" src="x"/>
</p>
<a class="UncategorizedText" href="javascript:alert(document.cookie)" id="...">click me</a>

Opening xss_output.html in a browser fires alert automatically (via <img onerror>), with no interaction. Per-vector confirmation (each payload labelled, each verified in a browser):

Vector Trigger Cause
<img onerror> open file (auto) element text not escaped
<svg onload> (via title='"><svg ...>') open file (auto) attribute value not escaped (" breakout)
<a href=javascript:> click link URL scheme not filtered
onmouseover hover source attribute preserved as-is
Impact

Stored XSS caused by improper output encoding. Anyone who renders the HTML or text_as_html generated from an untrusted document is affected. In an ingestion pipeline where uploaded documents are parsed and a staff member reviews their contents in a web UI, a low-privileged or external submitter can inject malicious HTML; when a privileged reviewer later opens the parsed result, <img onerror> fires in their session with no interaction, leading to cross-record information disclosure and privileged actions.

Severity

  • CVSS Score: 6.1 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

aio-libs/aiohttp (aiohttp)

v3.14.4

Compare Source

===================

Features

  • Added :class:aiohttp.UploadTracker for observing a client request's upload progress -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13579.

  • Switched application/x-www-form-urlencoded parsing in
    :meth:~aiohttp.web.BaseRequest.post to the faster :func:yarl.query_to_pairs
    parser and added the client_max_fields argument to
    :class:~aiohttp.web.Application (default 1000) to cap the number of form
    fields accepted by :meth:~aiohttp.web.BaseRequest.post. Forms with more
    than 1000 fields now receive a 413 response unless the cap is raised;
    0 disables it -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13738.

  • Added constants to aiohttp.hdrs for widely used headers: those that
    browsers send on every request (Sec-Fetch-*, Sec-CH-UA*,
    Sec-GPC, Upgrade-Insecure-Requests, Priority), W3C trace context
    (traceparent, tracestate, baggage), response security, reporting
    and caching headers, the remaining RFC 9110 and RFC 9530 fields,
    Content-ID and common de facto proxy and application headers, and
    grouped the constants by where the header is defined. The C parser returns
    these names as the shared :class:~multidict.istr constants instead of new
    :class:str objects, which made parsing a typical browser request about
    9% cheaper -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13886.

Bug fixes

  • Remove overlapping slots in RequestHandler,
    fix broken slots inheritance in :py:class:~aiohttp.web.StreamResponse.

    Related issues and pull requests on GitHub:
    :issue:6547.

  • Fixed a segmentation fault in the C HTTP parser on Python 3.12 and newer when payload decompression raised an error while pending decompressed data was being drained, as seen with brotlicffi 1.2 -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13203, :issue:13249.

  • Rejected control characters in the request target in the pure-Python HTTP parser,
    matching the llhttp-backed parser, which already refuses them
    -- by :user:arshsmith1.

    Related issues and pull requests on GitHub:
    :issue:13212.

  • Stripped the trailing whitespace from header values in the C HTTP parser,
    so that it matches the pure-Python parser and :rfc:9110#section-5.5
    -- by :user:LuShadowX.

    Related issues and pull requests on GitHub:
    :issue:13246.

  • Fixed the WebSocket reader rejecting a compressed data frame with close code 1002 when a control frame arrived before the first data frame (regression in 3.14.2) -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13274.

  • Fixed internally retried requests sending a truncated body when the request
    data was a file object.

    Related issues and pull requests on GitHub:
    :issue:13329, :issue:13330.

  • Fixed event loop state possibly being corrupted on Python 3.12+ -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13346.

  • Fixed the HTTP parser raising :exc:~aiohttp.ClientPayloadError when a fully received Content-Length body was pending completion -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13348.

  • Bounded the per-read object overhead the WebSocket reader retains while reassembling a frame delivered across many small reads; the reads are joined once when the frame completes, and folded into a single buffer if they exceed a fragment cap, so a frame dribbled in tiny reads cannot pin unbounded per-read overhead -- by :user:Dreamsorcerer and :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13352, :issue:13488.

  • Fixed requests pipelined behind a request whose upgrade the handler declined
    going unanswered once there were more of them than the per-connection queue
    holds. With the pure-Python parser the same requests were also served more
    than once -- by :user:rodrigobnogueira.

    Related issues and pull requests on GitHub:
    :issue:13356.

  • Reduced CPU consumption when encountering many concatenated members in a compressed payload and rejected large amounts of members -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13362.

  • Fixed excessive memory consumption with small WebSocket messages -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13393.

  • Fixed an integer overflow on too large messages -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13415.

  • Switched multipart handling to use spooled temporary files to reduce number of file descriptors needed -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13426.

  • Fixed a limit on message tail after an upgrade request -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13501.

  • Fixed some edge case handling in multipart parts using base 64 encoding -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13509.

  • Fixed Cython 3.3.0 failing to compile the WebSocket reader: dropped the
    Final[...] annotation from ALLOWED_CLOSE_CODES and the int
    annotation from the local start_pos in WebSocketReader._feed_data,
    both of which conflicted with declarations in reader_c.pxd under
    Cython 3.3.0 -- by :user:Georgefifth.

    Related issues and pull requests on GitHub:
    :issue:13520.

  • Fixed the WebSocket reader accepting a new data frame injected between the
    fragments of an in-progress message; per :rfc:6455#section-5.4 every frame
    after the first fragment and before the FIN must be a continuation, and
    such a stream is now rejected as a protocol error -- by :user:arshsmith1.

    Related issues and pull requests on GitHub:
    :issue:13553.

  • Fixed a connection being eligible for reuse after its request was cancelled
    or failed while waiting for a 100 Continue response or finalizing the
    body; the request headers were already sent, so reusing the connection
    corrupted the next request on it -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13579.

  • Fixed BaseRequest.http_range not accepting case-insensitive range units -- by :user:Manny7717.

    Related issues and pull requests on GitHub:
    :issue:13580, :issue:13581.

  • Fixed CookieJar.update_cookies() to copy user-passed mutable Morsel objects -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13637.

  • Fixed unbounded memory growth on a client WebSocket connection. A frame
    protocol error detaches the reader but leaves the connection upgraded, so a
    peer could stream unlimited data into an internal buffer when the application
    never called :meth:~aiohttp.ClientWebSocketResponse.receive; that data is
    now discarded, since nothing can parse it. Data arriving before the reader is
    installed is bounded by read_bufsize, which now applies to this buffer as
    well as to :attr:~aiohttp.ClientResponse.content
    -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13655, :issue:13743.

  • Fixed pure-Python request parser not reading a body in a HEAD request -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13671.

  • Fixed host-only cookie state being lost on expiration -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13674.

  • Fixed a possible OverflowError on cookies and a connection not being closed properly -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13677.

  • The first-request deadline now also closes connections whose first request body stalls, while a body that is still arriving extends the deadline instead of being interrupted -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13681.

  • Fixed idle connections not being closed if no request was received -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13681.

  • Fixed :meth:~aiohttp.web.Application.add_domain not routing a request to
    its domain application when the Host header carried a port and the
    domain was registered without one, or, for a wildcard domain, uppercase
    letters -- by :user:rodrigobnogueira.

    Related issues and pull requests on GitHub:
    :issue:13693.

  • Added empty __slots__ to AbstractRouteDef so that RouteDef and
    StaticDef instances no longer carry an unused __dict__.

    Related issues and pull requests on GitHub:
    :issue:13716.

  • Fixed BaseConnector(keepalive_timeout=None) crashing on the second request to the same host with TypeError: '<=' not supported between instances of 'float' and 'NoneType' -- by :user:ishan-1010.

    Related issues and pull requests on GitHub:
    :issue:13756, :issue:13757.

  • Fixed a crash in :meth:~aiohttp.BodyPartReader.read_chunk on a body part
    with an explicit Content-Length: 0: the part fell through to the
    streaming read strategy, whose minimum chunk size assertion then failed for
    chunk sizes below the boundary length. Such parts now yield an immediate
    empty chunk, like any other part with a known length
    -- by :user:istoolsfox.

    Related issues and pull requests on GitHub:
    :issue:13758, :issue:13760.

  • Fixed Set-Cookie parsing treating unrecognized attributes as additional
    cookies. Each Set-Cookie header now sets exactly one cookie and
    unrecognized attributes are ignored, per :rfc:6265#section-5.2, preventing
    a malicious server from creating an attacker-selected number of cookie
    objects (and correspondingly large outgoing Cookie headers) from a
    bounded amount of response data. DummyCookieJar, and CookieJar in
    safe mode for IP-address origins, no longer parse Set-Cookie headers at
    all -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13800.

  • Fixed the web server trusting the scheme of an absolute-form request-target -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13821.

  • Fixed CookieJar.filter_cookies() sending shared cookies (cookies without a Domain attribute) marked Secure over unencrypted connections -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13830.

  • Fixed per-request cookies (the cookies argument of a request method) marked Secure not being sent to origins listed in CookieJar's treat_as_secure_origin -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13833.

  • Fixed the connection to an HTTP proxy staying open until garbage collection, and being reported as Unclosed connection, when sending the CONNECT request for an HTTPS tunnel failed -- by :user:Garbsener.

    Related issues and pull requests on GitHub:
    :issue:13841.

  • Resolved a redirect Location with the scheme of the current URL but
    without //, such as http:/path or http:path, against the
    current URL, as browsers do, instead of treating it as an absolute URL
    without a host
    -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13855.

  • Rejected absolute-form request targets without // or with an empty
    host, such as http:/example.com/ or http:///example.com/, before
    parsing them with yarl, which reads a host from them in its WHATWG mode;
    RFC 9110 requires a host for http and https. The invalid URL test
    data no longer uses http:///example.com, which such a yarl version
    parses as http://example.com/, as browsers do
    -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13858.

  • Fixed :py:meth:~aiohttp.StreamReader.readuntil not finding a multi-byte
    separator whose bytes arrived in different chunks, which made it return data
    past the separator -- by :user:andrewstellman.

    Related issues and pull requests on GitHub:
    :issue:13870.

  • Fixed mixed-case Content-Encoding values (for example Gzip)
    being accepted by the parser but failing decompression, a regression
    from the CVE-2025-69224 hardening -- by :user:muhammad-a-dev.

    Related issues and pull requests on GitHub:
    :issue:13894.

  • Added limits to client cookie parsing, :class:~aiohttp.CookieJar storage and
    generated Cookie headers, with Firefox-style eviction, and fixed a replaced cookie
    keeping the previous cookie's expiry when the new cookie has none
    -- by :user:iamibi and :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13930.

  • Improved performance in domain matching with Application.add_domain() -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13943.

Deprecations (removal in next major release)

  • Deprecated ClientResponse.output_size and ClientResponse.upload_complete;
    use aiohttp.UploadTracker instead -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13579.

Removals and backward incompatible breaking changes

  • The WebSocket receive queue now only holds a weak reference to the WebSocketReader while parsing is stalled; code constructing a reader directly and passing it to set_parser() must keep its own strong reference to it, or frames the reader stopped short of parsing are lost with it -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13393.

  • Removed the internal writer proxy used for upload progress accounting.
    AbstractStreamWriter gained an optional on_body_write callback that
    write() / write_eof() implementations must invoke with each accepted
    body chunk's byte length; custom writer implementations that do not call it
    will report Payload.bytes_written as 0 -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:13436.

  • Increased minimum yarl version to 1.25.1 -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13734.

  • Changed Set-Cookie parsing to create exactly one cookie per field, as RFC 6265
    and browsers do. Later name=value pairs and unknown attributes no longer create
    extra cookies, a leading pair such as Path=/ or $Version=1 is the cookie itself,
    and legacy $Path and $Domain attributes are ignored -- by :user:iamibi.

    Related issues and pull requests on GitHub:
    :issue:13930.

Improved documentation

  • Documented valid request URL forms when using :class:~aiohttp.UnixConnector, including base_url with an HTTP host -- by :user:muhammad-a-dev.

    Related issues and pull requests on GitHub:
    :issue:11324, :issue:13781.

  • Corrected the documented signature of :meth:~aiohttp.StreamReader.read_nowait,
    whose n parameter defaults to -1 rather than the None that was
    previously documented -- by :user:LALITH0110.

    Related issues and pull requests on GitHub:
    :issue:13295.

  • Added interlock-cb, an aiohttp client circuit breaker middleware, to the
    third-party libraries page -- by :user:bagowix.

    Related issues and pull requests on GitHub:
    :issue:13336.

  • Documented that max_redirects=0 means no limit and that allow_redirects=False disables redirects -- by :user:monasco.

    Related issues and pull requests on GitHub:
    :issue:13658.

  • Corrected the documented signature of :py:meth:~aiohttp.StreamReader.readuntil, which
    showed a str separator although the method takes bytes, and documented its
    keyword-only max_size argument -- by :user:hxperl.

    Related issues and pull requests on GitHub:
    :issue:13686.

  • Replaced most of the sphinx.ext.extlinks-based roles in the documentation
    with :pypi:sphinx-issues, which ships the
    :issue:, :pr:, :commit: and :user: roles out of the box.
    Pull request references are now captioned #N instead of PR #N, and
    commit references as abbreviated, @-prefixed hashes
    -- by :user:aiolibsbot.

    Related issues and pull requests on GitHub:
    :issue:13752.

  • Fixed the Content-ID example in the multipart docs, which used a
    constant missing from aiohttp.hdrs and a value that is not a valid
    message ID -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13886.

Packaging updates and notes for downstreams

  • Started publishing an additional pure-Python wheel alongside the existing
    per-platform binary wheels and the sdist -- by :user:webknjaz.

    This gives users on platforms without a working C compiler, or without a
    matching pre-built wheel, an installable fallback that does not require
    compilation.

    Related issues and pull requests on GitHub:
    :issue:7632, :issue:13388.

  • Removed the aiohttp/_websocket/reader_c.py symlink from the source tree; the aiohttp._websocket.reader_c extension is now compiled directly from reader_py.py using cython --module-name, so distributions no longer include a reader_c.py file that showed up as an uncovered module in coverage reports -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13457.

  • Adopted :pep:639 license metadata -- the license is now declared as the
    SPDX expression Apache-2.0 AND MIT and license-files moved to the
    [project] table, which raises the build-time requirement to
    setuptools >= 77.0. Built distributions now carry
    License-Expression instead of the legacy License field
    -- by :user:aiolibsbot.

    Related issues and pull requests on GitHub:
    :issue:13891.

Contributor-facing changes

  • The CI/CD is now in sync with the rest of the projects in terms of where
    the cibuildwheel workflow lives -- by :user:webknjaz.

    Related commits on GitHub:
    :commit:59c0123d.

  • Moved the pytest configuration from :file:setup.cfg to a dedicated
    :file:pytest.ini that follows the layout shared with propcache and
    other aio-libs projects. Compared to the old configuration,
    minversion is raised from 3.8.2 to 8.4; pytest-xdist
    (--numprocesses=auto) and pytest-cov (--cov,
    --cov-context=test, --no-cov-on-fail) are enabled by default
    again, so pass --numprocesses=0 and/or --no-cov to opt out, as
    the :file:Makefile targets and CI jobs now do where needed;
    --doctest-modules, --strict-markers and
    faulthandler_timeout = 30 are enabled; -v is no longer added;
    empty parameter sets are marked xfail instead of skipped;
    --junitxml reports use xunit1 with captured output and
    call-only durations; and norecursedirs skips more directories,
    including :file:tests/isolated/
    -- by :user:aiolibsbot.

    Related issues and pull requests on GitHub:
    :issue:12620, :issue:12621.

  • Added check that change fragment matches PR number -- by :user:Dreamsorcerer.

    Related issues and pull requests on GitHub:
    :issue:12788.

  • CI now builds the sdist (and a pure-Python wheel) once, in a new
    build-pure-python-dists job, and shares that build across test,
    autobahn, benchmark, build-wheels, test-mobile and the
    sdist-based half of linting, instead of every one of those jobs
    checking out the repository and running make cythonize on its own
    -- by :user:webknjaz.

    Linting is also now split into lint-from-git (the
    :file:requirements/runtime-deps.in sync check and docs spell-checking,
    which need real Git history) and lint-from-sdist (mypy,
    slotscheck, the changelog fragment check, and twine check, which
    build from the shared artifact instead), since an sdist tarball never
    contains :file:.git.

    Related issues and pull requests on GitHub:
    :issue:13363, :issue:13388.

  • Synchronized the coverage.py configuration (:file:.coveragerc.toml and
    :file:.coveragerc-cython.toml) with the pattern already established in
    :external+yarl:doc:yarl <index>, :external+multidict:doc:multidict <index>, frozenlist and other sibling projects
    -- by :user:webknjaz.

    Both files now anchor package discovery through source_pkgs instead of
    relying on a same-named directory happening to exist relative to the
    working directory, and add a [paths] mapping so coverage recorded
    against an installed copy of aiohttp still combines correctly with
    coverage recorded from the Git checkout. CI now lets pytest-cov write
    coverage.xml directly via --cov-report=xml instead of a separate
    coverage xml step, and the Autobahn testsuite's subprocess-based
    coverage collection (which uses coverage run --append, incompatible
    with parallel mode) now opts out per-invocation via a
    COVERAGE_PARALLEL_MODE environment variable instead of trying to
    override it on the command line.

    Related issues and pull requests on GitHub:
    :issue:13422.

  • Stopped the benchmark CI job from hanging in the CodSpeed runner's apt
    install by installing libc6-dbg up front with a bounded retry, and raised
    the job timeout from 15 to 30 minutes -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13489.

  • Added benchmarks for reading masked WebSocket messages and fixed the
    existing read benchmarks, which stopped measuring the parser after the
    eighth large frame due to the queue limit -- by :user:bdraco.

    Related issues and pull requests on GitHub:
    :issue:13561.

  • Removed stale filterwarnings ignores from the pytest configuration
    that are no longer triggered by aiohttp, the supported Python versions
    or the pinned test dependencies -- by :user:aiolibsbot.

    Related issues and pull requests on GitHub:
    :issue:13717.

  • Dropped the leftover PIP_USER setting and the pip --user PATH
    prefix from the CI workflow; both became dead once the test jobs started
    provisioning Python via astral-sh/setup-uv
    -- by :user:aiolibsbot.

    Related issues and pull requests on GitHub:
    :issue:13718, :issue:13721.

  • Changed the long host in the Host header tests to one that is not made
    only of digits, since yarl now parses such a host as an IP address in its
    default mode and rejects this one as out of range
    -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13861.

  • Fixed tools/gen.py dropping a header name from the generated C lookup
    when two names shared a prefix that differed only in letter case, such as
    Accept-CH and Accept-Charset, and made the generated code compile
    without warnings -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13886.

Miscellaneous internal changes

  • Avoided formatting an unused fallback Date header value when the response
    already has one -- by :user:marcus-campbell.

    Related issues and pull requests on GitHub:
    :issue:13299.

  • Improved header parsing performance in the C HTTP parser by reusing the
    :class:~multidict.istr built for a header name missing from
    aiohttp.hdrs the next time the same name arrives, from a bounded
    cache of up to 512 names of at most 64 bytes -- by :user:asvetlov.

    Related issues and pull requests on GitHub:
    :issue:13887.


pygments/pygments (pygments)

v2.20.0

Compare Source

(released March 29th, 2026)

v2.19.2

Compare Source

(released June 21st, 2025)

Unstructured-IO/unstructured (unstructured)

v0.24.1

Compare Source

Fixes
  • Fix stored XSS in v2 (ontology) HTML output (GHSA-v5mq-3xhg-98m9): partition_html(html_parser_version="v2"), elements_to_html(), and metadata.text_as_html previously emitted untrusted document markup without output encoding, allowing attacker-controlled content (on* handlers, javascript: links, tag/attribute breakout) to execute when the HTML was viewed. Output is now sanitized — text and attribute values are HTML-escaped, event-handler attributes are dropped, tags/attributes are allowlisted, and URL schemes are filtered (http/https/mailto/tel/relative preserved; data: limited to raster image MIME types on img[src]). Legitimate formatting is unaffected.

Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [aiohttp](https://github.com/aio-libs/aiohttp) | `==3.14.3` → `==3.14.4` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/aiohttp/3.14.4?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/aiohttp/3.14.3/3.14.4?slim=true) | | [pygments](https://github.com/pygments/pygments) ([changelog](https://github.com/pygments/pygments/blob/master/CHANGES)) | `==2.19.1` → `==2.20.0` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/pygments/2.20.0?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/pygments/2.19.1/2.20.0?slim=true) | | [unstructured](https://github.com/Unstructured-IO/unstructured) | `==0.24.0` → `==0.24.1` | ![age](https://developer.mend.io/api/mc/badges/age/pypi/unstructured/0.24.1?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/unstructured/0.24.0/0.24.1?slim=true) | --- ### AIOHTTP: Base64 multipart parts bypass client_max_size [CVE-2026-128127](https://nvd.nist.gov/vuln/detail/CVE-2026-128127) / [GHSA-24c4-3p7v-29cm](https://github.com/advisories/GHSA-24c4-3p7v-29cm) / PYSEC-2026-4394 <details> <summary>More information</summary> #### Details ##### Summary When reading a multipart part with `Content-Transfer-Encoding: base64`, `BodyPartReader.read_chunk()` kept reading until the chunk length was a multiple of 4, with no byte limit. A part with a short `Content-Length`, or a long run of whitespace, could cause the entire remaining body to be read into memory within a single call before any size check, or spin on the event loop. ##### Impact An attacker could bypass `client_max_size` to cause excessive memory use, or block the event loop, with a specially crafted multipart request to any handler that reads multipart data. --- Patch: https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd #### Severity - CVSS Score: 8.7 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-24c4-3p7v-29cm](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-24c4-3p7v-29cm) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128127](https://nvd.nist.gov/vuln/detail/CVE-2026-128127) - [https://github.com/aio-libs/aiohttp/pull/13509](https://github.com/aio-libs/aiohttp/pull/13509) - [https://github.com/aio-libs/aiohttp/pull/13513](https://github.com/aio-libs/aiohttp/pull/13513) - [https://github.com/aio-libs/aiohttp/commit/2d9c5c1062eff0034fb3ab120897a6c1b3ff7041](https://github.com/aio-libs/aiohttp/commit/2d9c5c1062eff0034fb3ab120897a6c1b3ff7041) - [https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd](https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-24c4-3p7v-29cm) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade [CVE-2026-128130](https://nvd.nist.gov/vuln/detail/CVE-2026-128130) / [GHSA-28qf-cpwq-vmc2](https://github.com/advisories/GHSA-28qf-cpwq-vmc2) <details> <summary>More information</summary> #### Details ##### Summary When the pipelined request queue was full, the pure-Python parser stored the unparsed remainder internally and also returned it to the caller. After a handler declined an upgrade request, the buffered data was re-fed, so the buffer grew with each handled request and already-handled requests were dispatched to the application again. ##### Impact If users are using the Python parser (`AIOHTTP_NO_EXTENSIONS`, or not a standard wheel installed), an attacker could cause excessive memory use and cause pipelined requests to be processed more than once. ##### Workaround Switch to the default C parser. --- Patch: https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7 #### Severity - CVSS Score: 8.3 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-28qf-cpwq-vmc2](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-28qf-cpwq-vmc2) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128130](https://nvd.nist.gov/vuln/detail/CVE-2026-128130) - [https://github.com/aio-libs/aiohttp/pull/13356](https://github.com/aio-libs/aiohttp/pull/13356) - [https://github.com/aio-libs/aiohttp/pull/13360](https://github.com/aio-libs/aiohttp/pull/13360) - [https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7](https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7) - [https://github.com/aio-libs/aiohttp/commit/72eaa429cf89b1e20212590f3e704444239569fb](https://github.com/aio-libs/aiohttp/commit/72eaa429cf89b1e20212590f3e704444239569fb) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-28qf-cpwq-vmc2) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### aiohttp: Multiple instances of excessive or unbounded memory/CPU use [CVE-2026-123817](https://nvd.nist.gov/vuln/detail/CVE-2026-123817) / [GHSA-2g87-pp6c-29x5](https://github.com/advisories/GHSA-2g87-pp6c-29x5) / PYSEC-2026-4389 <details> <summary>More information</summary> #### Details ##### Summary While reassembling a WebSocket frame that arrived across many small transport reads, the reader kept one `bytes` object per read with no bound on the count. The per-object overhead is many times larger than the payload bytes, so a frame delivered a few bytes at a time could use far more memory than `max_msg_size` allows. ##### Impact An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending a frame in a large number of tiny segments. #### Severity - CVSS Score: 8.7 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5) - [https://github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f](https://github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f) - [https://github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6](https://github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6) - [https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df](https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df) - [https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7](https://github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7) - [https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53](https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53) - [https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa](https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa) - [https://github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f](https://github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f) - [https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab](https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab) - [https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd](https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd) - [https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43](https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43) - [https://github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db](https://github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-2g87-pp6c-29x5) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: WebSocket max_msg_size bypass via integer overflow [CVE-2026-128128](https://nvd.nist.gov/vuln/detail/CVE-2026-128128) / [GHSA-3rp8-rxj8-mvjw](https://github.com/advisories/GHSA-3rp8-rxj8-mvjw) / PYSEC-2026-4395 <details> <summary>More information</summary> #### Details ##### Summary The `max_msg_size` check in the WebSocket reader added the declared frame length to the size of the partial message already buffered. In the C extension this addition is 64-bit arithmetic, so a declared length close to 2**63 overflowed and the check passed. ##### Impact An attacker could bypass `max_msg_size` and cause unbounded memory use by streaming an oversized WebSocket message after a small non-final fragment. ##### Workaround If unable to upgrade, the Python reader is unaffected and can be used with `AIOHTTP_NO_EXTENSIONS=1`. --- Patch: https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-3rp8-rxj8-mvjw](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-3rp8-rxj8-mvjw) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128128](https://nvd.nist.gov/vuln/detail/CVE-2026-128128) - [https://github.com/aio-libs/aiohttp/pull/13415](https://github.com/aio-libs/aiohttp/pull/13415) - [https://github.com/aio-libs/aiohttp/pull/13494](https://github.com/aio-libs/aiohttp/pull/13494) - [https://github.com/aio-libs/aiohttp/commit/8c8906a19f64e52ef6a7d44d65217eb3c5af413f](https://github.com/aio-libs/aiohttp/commit/8c8906a19f64e52ef6a7d44d65217eb3c5af413f) - [https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab](https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-3rp8-rxj8-mvjw) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Secure attribute not enforced for shared cookie [CVE-2026-111063](https://nvd.nist.gov/vuln/detail/CVE-2026-111063) / [GHSA-494j-54xm-rwp3](https://github.com/advisories/GHSA-494j-54xm-rwp3) / PYSEC-2026-4365 <details> <summary>More information</summary> #### Details ##### Summary The Secure attribute was not being enforced for the shared cookie. ##### Impact It may be possible to send a shared cookie marked Secure through an unencrypted request. #### Severity - CVSS Score: 6.3 / 10 (Medium) - Vector String: `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` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-494j-54xm-rwp3](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-494j-54xm-rwp3) - [https://nvd.nist.gov/vuln/detail/CVE-2026-111063](https://nvd.nist.gov/vuln/detail/CVE-2026-111063) - [https://github.com/aio-libs/aiohttp/commit/999c356d61e966faffa97b06ab0d0455226d36c5](https://github.com/aio-libs/aiohttp/commit/999c356d61e966faffa97b06ab0d0455226d36c5) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-494j-54xm-rwp3) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Unbounded cookie storage in client CookieJar [CVE-2026-128125](https://nvd.nist.gov/vuln/detail/CVE-2026-128125) / [GHSA-5pv8-vvhc-h7jv](https://github.com/advisories/GHSA-5pv8-vvhc-h7jv) / PYSEC-2026-4392 <details> <summary>More information</summary> #### Details ##### Summary `Set-Cookie` parsing created additional cookies from unrecognised `name=value` attributes, and `CookieJar` had no limit on the number of cookies stored or sent. A server could make the client store a very large number of cookies and generate very large `Cookie` headers. ##### Impact A malicious server could cause excessive memory and CPU use in a client, repeated on every redirect, and cause later requests to the same domain to build an excessively large `Cookie` header. --- Patch: https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa #### Severity - CVSS Score: 6.3 / 10 (Medium) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5pv8-vvhc-h7jv](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5pv8-vvhc-h7jv) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128125](https://nvd.nist.gov/vuln/detail/CVE-2026-128125) - [https://github.com/aio-libs/aiohttp/pull/13930](https://github.com/aio-libs/aiohttp/pull/13930) - [https://github.com/aio-libs/aiohttp/pull/13942](https://github.com/aio-libs/aiohttp/pull/13942) - [https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa](https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa) - [https://github.com/aio-libs/aiohttp/commit/b1f6c87b2bd3bd80f2b6c22ff46e11d00921e412](https://github.com/aio-libs/aiohttp/commit/b1f6c87b2bd3bd80f2b6c22ff46e11d00921e412) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-5pv8-vvhc-h7jv) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: WebSocket receive queue limits bypassed by small or compressed messages [CVE-2026-128132](https://nvd.nist.gov/vuln/detail/CVE-2026-128132) / [GHSA-5rmc-48h2-hvcm](https://github.com/advisories/GHSA-5rmc-48h2-hvcm) <details> <summary>More information</summary> #### Details ##### Summary The WebSocket reader continued parsing frames already received after the receive queue had paused the transport, and empty messages were not counted towards the queue size. With permessage-deflate, a single read of compressed frames could add many megabytes of decompressed messages to the queue. ##### Impact An attacker could cause excessive memory use in a WebSocket server, or a malicious server against a client, by sending many small or compressed messages faster than the application consumes them. --- Patch: https://github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6 #### Severity - CVSS Score: 8.7 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5rmc-48h2-hvcm](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5rmc-48h2-hvcm) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128132](https://nvd.nist.gov/vuln/detail/CVE-2026-128132) - [https://github.com/aio-libs/aiohttp/pull/13393](https://github.com/aio-libs/aiohttp/pull/13393) - [https://github.com/aio-libs/aiohttp/pull/13545](https://github.com/aio-libs/aiohttp/pull/13545) - [https://github.com/aio-libs/aiohttp/pull/13546](https://github.com/aio-libs/aiohttp/pull/13546) - [https://github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6](https://github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6) - [https://github.com/aio-libs/aiohttp/commit/5e54037933fa8422be5fa8a2002d118ed2d4e5e0](https://github.com/aio-libs/aiohttp/commit/5e54037933fa8422be5fa8a2002d118ed2d4e5e0) - [https://github.com/aio-libs/aiohttp/commit/b62321b6fa264a89f4aca084ad60fc38a59ffa51](https://github.com/aio-libs/aiohttp/commit/b62321b6fa264a89f4aca084ad60fc38a59ffa51) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-5rmc-48h2-hvcm) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### aiohttp server lacks an initial request/header timeout [CVE-2026-111064](https://nvd.nist.gov/vuln/detail/CVE-2026-111064) / [GHSA-5wr8-gcqf-gqf3](https://github.com/advisories/GHSA-5wr8-gcqf-gqf3) / PYSEC-2026-4366 <details> <summary>More information</summary> #### Details ##### Summary The keepalive timeout was not used during the initial portion of a request. ##### Impact An attacker could keep an idle connection open indefinitely before sending any data. ##### Workaround Use a reverse proxy (as recommended for all production deployments) with sensible keepalive limits. #### Severity - CVSS Score: 8.2 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5wr8-gcqf-gqf3](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5wr8-gcqf-gqf3) - [https://github.com/aio-libs/aiohttp/commit/be846822b4b3a5a54b6163e794b42dc06fba54a3](https://github.com/aio-libs/aiohttp/commit/be846822b4b3a5a54b6163e794b42dc06fba54a3) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-5wr8-gcqf-gqf3) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Connector pool exhaustion via Max-Age overflow [CVE-2026-111065](https://nvd.nist.gov/vuln/detail/CVE-2026-111065) / [GHSA-6cjc-53gc-5rqm](https://github.com/advisories/GHSA-6cjc-53gc-5rqm) / PYSEC-2026-4367 <details> <summary>More information</summary> #### Details ##### Summary An overflow in Max-Age processing can skip closing a connection. ##### Impact An attacker may be able to exhaust the connection pool temporarily, until garbage collection resolves the connections. #### Severity - CVSS Score: 6.9 / 10 (Medium) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-6cjc-53gc-5rqm](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-6cjc-53gc-5rqm) - [https://nvd.nist.gov/vuln/detail/CVE-2026-111065](https://nvd.nist.gov/vuln/detail/CVE-2026-111065) - [https://github.com/aio-libs/aiohttp/commit/9dd8eaf4e31f1237ef2c1574a8c82a739fca5805](https://github.com/aio-libs/aiohttp/commit/9dd8eaf4e31f1237ef2c1574a8c82a739fca5805) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-6cjc-53gc-5rqm) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: File descriptor exhaustion in multipart requests [CVE-2026-111066](https://nvd.nist.gov/vuln/detail/CVE-2026-111066) / [GHSA-9xw5-w5jj-pvcg](https://github.com/advisories/GHSA-9xw5-w5jj-pvcg) / PYSEC-2026-4368 <details> <summary>More information</summary> #### Details ##### Summary An attacker can exhaust file descriptors with specially crafted multipart requests. ##### Impact If a handler uses `Request.post()`, it may be possible for an attacker to use an unlimited number of file descriptors, potentially resulting in resource exhaustion. #### Severity - CVSS Score: 8.2 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9xw5-w5jj-pvcg](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9xw5-w5jj-pvcg) - [https://nvd.nist.gov/vuln/detail/CVE-2026-111066](https://nvd.nist.gov/vuln/detail/CVE-2026-111066) - [https://github.com/aio-libs/aiohttp/commit/2d94633b7f1b4c1ba07d647b629a8440652b2d09](https://github.com/aio-libs/aiohttp/commit/2d94633b7f1b4c1ba07d647b629a8440652b2d09) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-9xw5-w5jj-pvcg) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Absolute-form request targets can spoof Request.scheme [CVE-2026-111748](https://nvd.nist.gov/vuln/detail/CVE-2026-111748) / [GHSA-f9xw-jh8m-3mwq](https://github.com/advisories/GHSA-f9xw-jh8m-3mwq) / PYSEC-2026-4369 <details> <summary>More information</summary> #### Details ##### Summary An attacker sending an absolute-form request can spoof the scheme used. ##### Impact If user code depends on the `Request.scheme` attribute for anything security related, an attacker may be able to circumvent this logic, tricking the application into thinking a connection is encrypted when it is not, or vice versa. ##### Workaround A WAF rule to reject absolute-form requests (legitimate requests should only use this form for proxies). #### Severity - CVSS Score: 6.3 / 10 (Medium) - Vector String: `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` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-f9xw-jh8m-3mwq](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-f9xw-jh8m-3mwq) - [https://nvd.nist.gov/vuln/detail/CVE-2026-111748](https://nvd.nist.gov/vuln/detail/CVE-2026-111748) - [https://github.com/aio-libs/aiohttp/commit/6d4e7b01f9b951aa084a75d7356e907d4ee80411](https://github.com/aio-libs/aiohttp/commit/6d4e7b01f9b951aa084a75d7356e907d4ee80411) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-f9xw-jh8m-3mwq) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Cookie from subdomain can remove Host-Only Scope from existing cookies [CVE-2026-111749](https://nvd.nist.gov/vuln/detail/CVE-2026-111749) / [GHSA-gx76-c99x-2c96](https://github.com/advisories/GHSA-gx76-c99x-2c96) / PYSEC-2026-4370 <details> <summary>More information</summary> #### Details ##### Summary A subdomain can remove the Host-Only flag from an existing cookie to a parent domain. ##### Impact A user accessing untrusted subdomains could see their Host-Only protections stripped from cookies. Given most usecases won't reflect these cookies to a browser, the impact is limited. #### Severity - CVSS Score: 2.3 / 10 (Low) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gx76-c99x-2c96](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gx76-c99x-2c96) - [https://nvd.nist.gov/vuln/detail/CVE-2026-111749](https://nvd.nist.gov/vuln/detail/CVE-2026-111749) - [https://github.com/aio-libs/aiohttp/commit/6a07c171ef9f3be583e2907dcd1931372efca8d6](https://github.com/aio-libs/aiohttp/commit/6a07c171ef9f3be583e2907dcd1931372efca8d6) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-gx76-c99x-2c96) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Concatenated compressed streams cause excessive CPU use [CVE-2026-128131](https://nvd.nist.gov/vuln/detail/CVE-2026-128131) / [GHSA-h4cc-hm5h-fmm9](https://github.com/advisories/GHSA-h4cc-hm5h-fmm9) <details> <summary>More information</summary> #### Details ##### Summary When decompressing a payload made up of many concatenated compressed members (gzip, deflate or zstd), each member was decoded by passing the entire remaining input to a new decompressor, resulting in quadratic CPU time. Empty members produce no output, so `client_max_size` and output backpressure did not limit the work. ##### Impact An attacker could block the event loop of a server with a specially crafted compressed request body or WebSocket message. A malicious server could do the same to a client. --- Patch: https://github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db #### Severity - CVSS Score: 8.7 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-h4cc-hm5h-fmm9](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-h4cc-hm5h-fmm9) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128131](https://nvd.nist.gov/vuln/detail/CVE-2026-128131) - [https://github.com/aio-libs/aiohttp/pull/13362](https://github.com/aio-libs/aiohttp/pull/13362) - [https://github.com/aio-libs/aiohttp/pull/13391](https://github.com/aio-libs/aiohttp/pull/13391) - [https://github.com/aio-libs/aiohttp/commit/d041d4d0fd48c3f0832084d33be16cf1c4835f85](https://github.com/aio-libs/aiohttp/commit/d041d4d0fd48c3f0832084d33be16cf1c4835f85) - [https://github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db](https://github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-h4cc-hm5h-fmm9) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Event loop stall in add_domain() wildcard matching [CVE-2026-128124](https://nvd.nist.gov/vuln/detail/CVE-2026-128124) / [GHSA-jm3w-gw2p-xjfj](https://github.com/advisories/GHSA-jm3w-gw2p-xjfj) / PYSEC-2026-4391 <details> <summary>More information</summary> #### Details ##### Summary `Application.add_domain()` compiled each `*` in a host mask to `[^:]*`. With two or more wildcards in a mask, matching a long `Host` header that does not match the mask took polynomial time on the event loop. ##### Impact An attacker could stall a server that registers a domain mask with more than one wildcard by sending requests with a long `Host` header. ##### Workaround Use at most one `*` in a domain mask. --- Patch: https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43 #### Severity - CVSS Score: 8.2 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128124](https://nvd.nist.gov/vuln/detail/CVE-2026-128124) - [https://github.com/aio-libs/aiohttp/pull/13943](https://github.com/aio-libs/aiohttp/pull/13943) - [https://github.com/aio-libs/aiohttp/pull/13945](https://github.com/aio-libs/aiohttp/pull/13945) - [https://github.com/aio-libs/aiohttp/commit/766b882820da0651c84090e366a3b024b4a263c9](https://github.com/aio-libs/aiohttp/commit/766b882820da0651c84090e366a3b024b4a263c9) - [https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43](https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-jm3w-gw2p-xjfj) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Pure-Python parser request smuggling [CVE-2026-111750](https://nvd.nist.gov/vuln/detail/CVE-2026-111750) / [GHSA-pqxq-w44r-73xw](https://github.com/advisories/GHSA-pqxq-w44r-73xw) / PYSEC-2026-4371 <details> <summary>More information</summary> #### Details ##### Summary The pure Python parser is vulnerable to an HTTP request smuggling attack. ##### Impact If users are using the Python parser (`AIOHTTP_NO_EXTENSIONS`, or not a standard wheel installed), then an application may be vulnerable to a request smuggling attack. ##### Workaround Switch to the default C parser. #### Severity - CVSS Score: 6.3 / 10 (Medium) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:L/SA:L` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pqxq-w44r-73xw](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pqxq-w44r-73xw) - [https://nvd.nist.gov/vuln/detail/CVE-2026-111750](https://nvd.nist.gov/vuln/detail/CVE-2026-111750) - [https://github.com/aio-libs/aiohttp/commit/9b27347e61454d9f8ca2055f4c67a37dee336e83](https://github.com/aio-libs/aiohttp/commit/9b27347e61454d9f8ca2055f4c67a37dee336e83) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-pqxq-w44r-73xw) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Unbounded buffering of data received during an upgrade request [CVE-2026-128129](https://nvd.nist.gov/vuln/detail/CVE-2026-128129) / [GHSA-pw86-h8fm-j323](https://github.com/advisories/GHSA-pw86-h8fm-j323) <details> <summary>More information</summary> #### Details ##### Summary While a request flagged as an upgrade (e.g. a WebSocket handshake) was being handled, all further data received on the connection was buffered with no size limit or flow control until the handler completed. ##### Impact An attacker could cause unbounded memory use by streaming data behind an upgrade request to any handler that does not immediately accept or reject the upgrade. --- Patch: https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df #### Severity - CVSS Score: 8.2 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pw86-h8fm-j323](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pw86-h8fm-j323) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128129](https://nvd.nist.gov/vuln/detail/CVE-2026-128129) - [https://github.com/aio-libs/aiohttp/pull/13501](https://github.com/aio-libs/aiohttp/pull/13501) - [https://github.com/aio-libs/aiohttp/pull/13511](https://github.com/aio-libs/aiohttp/pull/13511) - [https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df](https://github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df) - [https://github.com/aio-libs/aiohttp/commit/c207cadb257e0959b192ffca0548eca8c71eb96a](https://github.com/aio-libs/aiohttp/commit/c207cadb257e0959b192ffca0548eca8c71eb96a) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-pw86-h8fm-j323) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### AIOHTTP: Too many URL-encoded form fields block the event loop [CVE-2026-128126](https://nvd.nist.gov/vuln/detail/CVE-2026-128126) / [GHSA-xgw8-8ccx-rmqh](https://github.com/advisories/GHSA-xgw8-8ccx-rmqh) / PYSEC-2026-4393 <details> <summary>More information</summary> #### Details ##### Summary `Request.post()` had no limit on the number of fields in a URL-encoded form body. Inserting a large number of repeated keys into a `MultiDict` took quadratic time on the event loop. ##### Impact An attacker could block the event loop with a form POST within the default `client_max_size` to any handler that calls `Request.post()`. --- Patch: https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53 #### Severity - CVSS Score: 8.7 / 10 (High) - Vector String: `CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N` #### References - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xgw8-8ccx-rmqh](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xgw8-8ccx-rmqh) - [https://nvd.nist.gov/vuln/detail/CVE-2026-128126](https://nvd.nist.gov/vuln/detail/CVE-2026-128126) - [https://github.com/aio-libs/aiohttp/pull/13738](https://github.com/aio-libs/aiohttp/pull/13738) - [https://github.com/aio-libs/aiohttp/pull/13741](https://github.com/aio-libs/aiohttp/pull/13741) - [https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53](https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53) - [https://github.com/aio-libs/aiohttp/commit/8b0100572936df28977b9de8a6cc7e464c0b521e](https://github.com/aio-libs/aiohttp/commit/8b0100572936df28977b9de8a6cc7e464c0b521e) - [https://github.com/aio-libs/aiohttp](https://github.com/aio-libs/aiohttp) - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-xgw8-8ccx-rmqh) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### [CVE-2026-111063](https://nvd.nist.gov/vuln/detail/CVE-2026-111063) / [GHSA-494j-54xm-rwp3](https://github.com/advisories/GHSA-494j-54xm-rwp3) / PYSEC-2026-4365 <details> <summary>More information</summary> #### Details 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. #### Severity - CVSS Score: 5.3 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/999c356d61e966faffa97b06ab0d0455226d36c5](https://github.com/aio-libs/aiohttp/commit/999c356d61e966faffa97b06ab0d0455226d36c5) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-494j-54xm-rwp3](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-494j-54xm-rwp3) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4365) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-111064](https://nvd.nist.gov/vuln/detail/CVE-2026-111064) / [GHSA-5wr8-gcqf-gqf3](https://github.com/advisories/GHSA-5wr8-gcqf-gqf3) / PYSEC-2026-4366 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, keepalive timeout handling is absent during the initial portion of a request. An attacker can keep an idle connection open indefinitely before sending any request data, consuming server connection capacity. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/be846822b4b3a5a54b6163e794b42dc06fba54a3](https://github.com/aio-libs/aiohttp/commit/be846822b4b3a5a54b6163e794b42dc06fba54a3) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5wr8-gcqf-gqf3](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5wr8-gcqf-gqf3) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4366) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-111065](https://nvd.nist.gov/vuln/detail/CVE-2026-111065) / [GHSA-6cjc-53gc-5rqm](https://github.com/advisories/GHSA-6cjc-53gc-5rqm) / PYSEC-2026-4367 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Max-Age processing can overflow and skip closing a connection. An attacker can consequently exhaust the connection pool temporarily until garbage collection resolves the connections. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 5.3 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/9dd8eaf4e31f1237ef2c1574a8c82a739fca5805](https://github.com/aio-libs/aiohttp/commit/9dd8eaf4e31f1237ef2c1574a8c82a739fca5805) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-6cjc-53gc-5rqm](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-6cjc-53gc-5rqm) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4367) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-111066](https://nvd.nist.gov/vuln/detail/CVE-2026-111066) / [GHSA-9xw5-w5jj-pvcg](https://github.com/advisories/GHSA-9xw5-w5jj-pvcg) / PYSEC-2026-4368 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. From 2.0.0 until 3.14.4, multipart request processing can retain an unbounded number of open file descriptors. An unauthenticated attacker can consequently exhaust file descriptors with specially crafted multipart requests when a handler uses Request.post(). This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/2d94633b7f1b4c1ba07d647b629a8440652b2d09](https://github.com/aio-libs/aiohttp/commit/2d94633b7f1b4c1ba07d647b629a8440652b2d09) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9xw5-w5jj-pvcg](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-9xw5-w5jj-pvcg) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4368) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-111748](https://nvd.nist.gov/vuln/detail/CVE-2026-111748) / [GHSA-f9xw-jh8m-3mwq](https://github.com/advisories/GHSA-f9xw-jh8m-3mwq) / PYSEC-2026-4369 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, an attacker can send an absolute-form request that causes Request.scheme to use attacker-controlled request-target scheme data instead of the connection protocol. Applications that use Request.scheme for security decisions can consequently be tricked into treating an unencrypted connection as encrypted or an encrypted connection as unencrypted. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 6.5 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/6d4e7b01f9b951aa084a75d7356e907d4ee80411](https://github.com/aio-libs/aiohttp/commit/6d4e7b01f9b951aa084a75d7356e907d4ee80411) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-f9xw-jh8m-3mwq](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-f9xw-jh8m-3mwq) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4369) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-111749](https://nvd.nist.gov/vuln/detail/CVE-2026-111749) / [GHSA-gx76-c99x-2c96](https://github.com/advisories/GHSA-gx76-c99x-2c96) / PYSEC-2026-4370 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Host-Only scope on an existing parent-domain cookie can be removed by a subdomain. A user who accesses an untrusted subdomain can consequently have host-only protections stripped from cookies, although impact is limited when applications do not reflect those cookies to a browser. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 5.4 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/6a07c171ef9f3be583e2907dcd1931372efca8d6](https://github.com/aio-libs/aiohttp/commit/6a07c171ef9f3be583e2907dcd1931372efca8d6) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gx76-c99x-2c96](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gx76-c99x-2c96) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4370) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-111750](https://nvd.nist.gov/vuln/detail/CVE-2026-111750) / [GHSA-pqxq-w44r-73xw](https://github.com/advisories/GHSA-pqxq-w44r-73xw) / PYSEC-2026-4371 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the pure Python parser accepts ambiguous HTTP request framing. An unauthenticated attacker can consequently smuggle requests when an application uses AIOHTTP_NO_EXTENSIONS or otherwise runs without a standard wheel and an intermediary interprets the framing differently. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 6.5 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/9b27347e61454d9f8ca2055f4c67a37dee336e83](https://github.com/aio-libs/aiohttp/commit/9b27347e61454d9f8ca2055f4c67a37dee336e83) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pqxq-w44r-73xw](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-pqxq-w44r-73xw) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4371) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-123817](https://nvd.nist.gov/vuln/detail/CVE-2026-123817) / [GHSA-2g87-pp6c-29x5](https://github.com/advisories/GHSA-2g87-pp6c-29x5) / PYSEC-2026-4389 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read while reassembling an incomplete frame. A malicious peer can split a frame into many tiny reads so per-object overhead substantially exceeds the payload bytes allowed by max_msg_size. The condition affects a server receiving frames from a malicious client and a client receiving frames from a malicious server, and can cause excessive memory consumption or denial of service. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f](https://github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f) - [https://github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f](https://github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f) - [https://github.com/aio-libs/aiohttp/pull/13352](https://github.com/aio-libs/aiohttp/pull/13352) - [https://github.com/aio-libs/aiohttp/pull/13612](https://github.com/aio-libs/aiohttp/pull/13612) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4389) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-128124](https://nvd.nist.gov/vuln/detail/CVE-2026-128124) / [GHSA-jm3w-gw2p-xjfj](https://github.com/advisories/GHSA-jm3w-gw2p-xjfj) / PYSEC-2026-4391 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Application.add_domain() converts every asterisk wildcard in a domain mask into a greedy regular-expression fragment, so a mask containing two or more wildcards can take polynomial time to reject a long Host header that does not match. A remote attacker can repeatedly send such headers to a server configured with a multi-wildcard domain mask and stall the event loop. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/766b882820da0651c84090e366a3b024b4a263c9](https://github.com/aio-libs/aiohttp/commit/766b882820da0651c84090e366a3b024b4a263c9) - [https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43](https://github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43) - [https://github.com/aio-libs/aiohttp/pull/13943](https://github.com/aio-libs/aiohttp/pull/13943) - [https://github.com/aio-libs/aiohttp/pull/13945](https://github.com/aio-libs/aiohttp/pull/13945) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-jm3w-gw2p-xjfj) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4391) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-128125](https://nvd.nist.gov/vuln/detail/CVE-2026-128125) / [GHSA-5pv8-vvhc-h7jv](https://github.com/advisories/GHSA-5pv8-vvhc-h7jv) / PYSEC-2026-4392 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Set-Cookie parsing treats unrecognized name=value attributes as additional cookies, while CookieJar does not limit the number of cookies stored or sent. A malicious server can make an aiohttp client accumulate a very large cookie set, consume memory and CPU repeatedly across redirects, and construct an excessively large Cookie header for later requests to the same domain. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 5.3 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa](https://github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa) - [https://github.com/aio-libs/aiohttp/commit/b1f6c87b2bd3bd80f2b6c22ff46e11d00921e412](https://github.com/aio-libs/aiohttp/commit/b1f6c87b2bd3bd80f2b6c22ff46e11d00921e412) - [https://github.com/aio-libs/aiohttp/pull/13930](https://github.com/aio-libs/aiohttp/pull/13930) - [https://github.com/aio-libs/aiohttp/pull/13942](https://github.com/aio-libs/aiohttp/pull/13942) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5pv8-vvhc-h7jv](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-5pv8-vvhc-h7jv) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4392) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-128126](https://nvd.nist.gov/vuln/detail/CVE-2026-128126) / [GHSA-xgw8-8ccx-rmqh](https://github.com/advisories/GHSA-xgw8-8ccx-rmqh) / PYSEC-2026-4393 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, Request.post() does not limit the number of fields in a URL-encoded form body, and inserting many repeated keys into MultiDict takes quadratic time on the event loop. A remote attacker can send a form POST within client_max_size to a handler that calls Request.post() and block the event loop. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53](https://github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53) - [https://github.com/aio-libs/aiohttp/commit/8b0100572936df28977b9de8a6cc7e464c0b521e](https://github.com/aio-libs/aiohttp/commit/8b0100572936df28977b9de8a6cc7e464c0b521e) - [https://github.com/aio-libs/aiohttp/pull/13738](https://github.com/aio-libs/aiohttp/pull/13738) - [https://github.com/aio-libs/aiohttp/pull/13741](https://github.com/aio-libs/aiohttp/pull/13741) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xgw8-8ccx-rmqh](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-xgw8-8ccx-rmqh) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4393) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-128127](https://nvd.nist.gov/vuln/detail/CVE-2026-128127) / [GHSA-24c4-3p7v-29cm](https://github.com/advisories/GHSA-24c4-3p7v-29cm) / PYSEC-2026-4394 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, BodyPartReader.read_chunk() processing a multipart part with Content-Transfer-Encoding set to base64 keeps reading until the chunk length is a multiple of four without enforcing a byte limit. A short Content-Length or a long run of whitespace can cause one call to read the remaining body into memory before the size check or spin on the event loop. A remote attacker can send such a multipart request to a handler that reads multipart data and bypass client_max_size. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/2d9c5c1062eff0034fb3ab120897a6c1b3ff7041](https://github.com/aio-libs/aiohttp/commit/2d9c5c1062eff0034fb3ab120897a6c1b3ff7041) - [https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd](https://github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd) - [https://github.com/aio-libs/aiohttp/pull/13509](https://github.com/aio-libs/aiohttp/pull/13509) - [https://github.com/aio-libs/aiohttp/pull/13513](https://github.com/aio-libs/aiohttp/pull/13513) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-24c4-3p7v-29cm](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-24c4-3p7v-29cm) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4394) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### [CVE-2026-128128](https://nvd.nist.gov/vuln/detail/CVE-2026-128128) / [GHSA-3rp8-rxj8-mvjw](https://github.com/advisories/GHSA-3rp8-rxj8-mvjw) / PYSEC-2026-4395 <details> <summary>More information</summary> #### Details AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Prior to 3.14.4, the C WebSocket reader adds a declared frame length to the size of an already buffered partial message using signed 64-bit arithmetic. A length near two to the power of 63 can overflow, allowing the max_msg_size check to pass. A remote peer can send a small non-final fragment followed by an oversized message and cause unbounded memory consumption. The Python WebSocket reader is unaffected. This issue is fixed in version 3.14.4. #### Severity - CVSS Score: 7.5 / 10 (High) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H` #### References - [https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4](https://github.com/aio-libs/aiohttp/releases/tag/v3.14.4) - [https://github.com/aio-libs/aiohttp/commit/8c8906a19f64e52ef6a7d44d65217eb3c5af413f](https://github.com/aio-libs/aiohttp/commit/8c8906a19f64e52ef6a7d44d65217eb3c5af413f) - [https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab](https://github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab) - [https://github.com/aio-libs/aiohttp/pull/13415](https://github.com/aio-libs/aiohttp/pull/13415) - [https://github.com/aio-libs/aiohttp/pull/13494](https://github.com/aio-libs/aiohttp/pull/13494) - [https://github.com/aio-libs/aiohttp/security/advisories/GHSA-3rp8-rxj8-mvjw](https://github.com/aio-libs/aiohttp/security/advisories/GHSA-3rp8-rxj8-mvjw) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-4395) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching [CVE-2026-4539](https://nvd.nist.gov/vuln/detail/CVE-2026-4539) / [GHSA-5239-wwwm-4pmq](https://github.com/advisories/GHSA-5239-wwwm-4pmq) / PYSEC-2026-2987 <details> <summary>More information</summary> #### Details A security flaw has been discovered in pygments before 2.20.0. The impacted element is the function AdlLexer of the file pygments/lexers/archetype.py. The manipulation results in inefficient regular expression complexity. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet. #### Severity - CVSS Score: 1.9 / 10 (Low) - Vector String: `CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P` #### References - [https://nvd.nist.gov/vuln/detail/CVE-2026-4539](https://nvd.nist.gov/vuln/detail/CVE-2026-4539) - [https://github.com/pygments/pygments/issues/3058](https://github.com/pygments/pygments/issues/3058) - [https://github.com/pygments/pygments/pull/3064](https://github.com/pygments/pygments/pull/3064) - [https://github.com/pygments/pygments/commit/24b8aa76c6cd6d70f39c6dd605cce319c98e2ccc](https://github.com/pygments/pygments/commit/24b8aa76c6cd6d70f39c6dd605cce319c98e2ccc) - [https://github.com/pygments/pygments](https://github.com/pygments/pygments) - [https://github.com/pygments/pygments/releases/tag/2.20.0](https://github.com/pygments/pygments/releases/tag/2.20.0) - [https://vuldb.com/?ctiid.352327](https://vuldb.com/?ctiid.352327) - [https://vuldb.com/?id.352327](https://vuldb.com/?id.352327) - [https://vuldb.com/?submit.774685](https://vuldb.com/?submit.774685) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-5239-wwwm-4pmq) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### Pygments has Regular Expression Denial of Service (ReDoS) due to Inefficient Regex for GUID Matching [CVE-2026-4539](https://nvd.nist.gov/vuln/detail/CVE-2026-4539) / [GHSA-5239-wwwm-4pmq](https://github.com/advisories/GHSA-5239-wwwm-4pmq) / PYSEC-2026-2987 <details> <summary>More information</summary> #### Details A security flaw has been discovered in pygments before 2.20.0. The impacted element is the function AdlLexer of the file pygments/lexers/archetype.py. The manipulation results in inefficient regular expression complexity. The attack is only possible with local access. The exploit has been released to the public and may be used for attacks. The project was informed of the problem early through an issue report but has not responded yet. #### Severity - CVSS Score: 1.9 / 10 (Low) - Vector String: `CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P` #### References - [https://nvd.nist.gov/vuln/detail/CVE-2026-4539](https://nvd.nist.gov/vuln/detail/CVE-2026-4539) - [https://github.com/pygments/pygments/issues/3058](https://github.com/pygments/pygments/issues/3058) - [https://github.com/pygments/pygments/pull/3064](https://github.com/pygments/pygments/pull/3064) - [https://github.com/pygments/pygments/commit/24b8aa76c6cd6d70f39c6dd605cce319c98e2ccc](https://github.com/pygments/pygments/commit/24b8aa76c6cd6d70f39c6dd605cce319c98e2ccc) - [https://github.com/pygments/pygments](https://github.com/pygments/pygments) - [https://github.com/pygments/pygments/releases/tag/2.20.0](https://github.com/pygments/pygments/releases/tag/2.20.0) - [https://vuldb.com/?ctiid.352327](https://vuldb.com/?ctiid.352327) - [https://vuldb.com/?id.352327](https://vuldb.com/?id.352327) - [https://vuldb.com/?submit.774685](https://vuldb.com/?submit.774685) - [https://pypi.org/project/pygments](https://pypi.org/project/pygments) - [https://github.com/advisories/GHSA-5239-wwwm-4pmq](https://github.com/advisories/GHSA-5239-wwwm-4pmq) This data is provided by [OSV](https://osv.dev/vulnerability/PYSEC-2026-2987) and the [PyPI Advisory Database](https://github.com/pypa/advisory-database) ([CC-BY 4.0](https://github.com/pypa/advisory-database/blob/main/LICENSE)). </details> --- ### unstructured: Stored XSS via unescaped HTML generation [CVE-2026-104250](https://nvd.nist.gov/vuln/detail/CVE-2026-104250) / [GHSA-v5mq-3xhg-98m9](https://github.com/advisories/GHSA-v5mq-3xhg-98m9) <details> <summary>More information</summary> #### Details ##### Summary When `unstructured` parses an untrusted document and outputs the result as HTML, malicious markup contained in the document (e.g. `<img src=x onerror=...>`) is left in the output HTML without escaping. When that output is displayed in a browser, the script embedded in the document executes in the viewer's browser. ##### Details `partition_html(html_parser_version="v2")` (and the VLM partitioner) preserve the input document's element tags, attributes, and text into `metadata.text_as_html`, and `elements_to_html()` outputs that as an HTML document. The function that builds HTML on this path, `to_html()` in `unstructured/documents/ontology.py`, performs no escaping at all. As a result, event handlers such as `onerror` / `onmouseover` / `onload` originating from the input document are left in the output HTML as-is (literal `<script>` tags are stripped by the parser, but attribute-based vectors and `javascript:` URLs are not). In addition, link URLs are not scheme-filtered, so `<a href="javascript:...">` is also emitted. Relevant source: `documents/ontology.py` (`to_html`, `_construct_attribute_string`, `_generate_final_html`); `partition/html/transformations.py` (`text_as_html = ontology_element.to_html()`); `partition/html/convert.py` (`elements_to_html`). ##### PoC Environment: `downloads.unstructured.io/unstructured-io/unstructured:latest`, `unstructured` 0.23.3. ```python from unstructured.partition.html import partition_html from unstructured.partition.html.convert import elements_to_html malicious = ('<body class="Document">' '<p class="Paragraph" onmouseover="alert(1)">hello' '<img src=x onerror="alert(document.domain)"></p>' '<a class="Hyperlink" href="javascript:alert(document.cookie)">click me</a>' '</body>') els = partition_html(text=malicious, html_parser_version="v2") open("xss_output.html", "w").write(elements_to_html(list(els), no_group_by_page=True)) ``` `elements_to_html()` output body — the unescaped vectors survive: ```html <p class="NarrativeText" id="..." onmouseover="alert(1)"> <p class="Paragraph">hello</p> <img class="Image" onerror="alert(document.domain)" src="x"/> </p> <a class="UncategorizedText" href="javascript:alert(document.cookie)" id="...">click me</a> ``` Opening `xss_output.html` in a browser fires `alert` automatically (via `<img onerror>`), with no interaction. Per-vector confirmation (each payload labelled, each verified in a browser): | Vector | Trigger | Cause | |---|---|---| | `<img onerror>` | open file (auto) | element `text` not escaped | | `<svg onload>` (via `title='"><svg ...>'`) | open file (auto) | attribute value not escaped (`"` breakout) | | `<a href=javascript:>` | click | link URL scheme not filtered | | `onmouseover` | hover | source attribute preserved as-is | ##### Impact Stored XSS caused by improper output encoding. Anyone who renders the HTML or `text_as_html` generated from an untrusted document is affected. In an ingestion pipeline where uploaded documents are parsed and a staff member reviews their contents in a web UI, a low-privileged or external submitter can inject malicious HTML; when a privileged reviewer later opens the parsed result, `<img onerror>` fires in their session with no interaction, leading to cross-record information disclosure and privileged actions. #### Severity - CVSS Score: 6.1 / 10 (Medium) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N` #### References - [https://github.com/Unstructured-IO/unstructured/security/advisories/GHSA-v5mq-3xhg-98m9](https://github.com/Unstructured-IO/unstructured/security/advisories/GHSA-v5mq-3xhg-98m9) - [https://nvd.nist.gov/vuln/detail/CVE-2026-104250](https://nvd.nist.gov/vuln/detail/CVE-2026-104250) - [https://github.com/Unstructured-IO/unstructured/pull/4394](https://github.com/Unstructured-IO/unstructured/pull/4394) - [https://github.com/Unstructured-IO/unstructured/commit/cda16b3f2170019be9c6ea5635946fb3eaa2d66f](https://github.com/Unstructured-IO/unstructured/commit/cda16b3f2170019be9c6ea5635946fb3eaa2d66f) - [https://github.com/Unstructured-IO/unstructured](https://github.com/Unstructured-IO/unstructured) - [https://github.com/Unstructured-IO/unstructured/releases/tag/0.24.1](https://github.com/Unstructured-IO/unstructured/releases/tag/0.24.1) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-v5mq-3xhg-98m9) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### Release Notes <details> <summary>aio-libs/aiohttp (aiohttp)</summary> ### [`v3.14.4`](https://github.com/aio-libs/aiohttp/blob/HEAD/CHANGES.rst#3144-2026-10-04) [Compare Source](https://github.com/aio-libs/aiohttp/compare/v3.14.3...v3.14.4) \=================== ## Features - Added :class:`aiohttp.UploadTracker` for observing a client request's upload progress -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13579`. - Switched `application/x-www-form-urlencoded` parsing in :meth:`~aiohttp.web.BaseRequest.post` to the faster :func:`yarl.query_to_pairs` parser and added the `client_max_fields` argument to :class:`~aiohttp.web.Application` (default `1000`) to cap the number of form fields accepted by :meth:`~aiohttp.web.BaseRequest.post`. Forms with more than 1000 fields now receive a `413` response unless the cap is raised; `0` disables it -- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13738`. - Added constants to `aiohttp.hdrs` for widely used headers: those that browsers send on every request (`Sec-Fetch-*`, `Sec-CH-UA*`, `Sec-GPC`, `Upgrade-Insecure-Requests`, `Priority`), W3C trace context (`traceparent`, `tracestate`, `baggage`), response security, reporting and caching headers, the remaining RFC 9110 and RFC 9530 fields, `Content-ID` and common de facto proxy and application headers, and grouped the constants by where the header is defined. The C parser returns these names as the shared :class:`~multidict.istr` constants instead of new :class:`str` objects, which made parsing a typical browser request about 9% cheaper -- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13886`. ## Bug fixes - Remove overlapping slots in `RequestHandler`, fix broken slots inheritance in :py:class:`~aiohttp.web.StreamResponse`. *Related issues and pull requests on GitHub:* :issue:`6547`. - Fixed a segmentation fault in the C HTTP parser on Python 3.12 and newer when payload decompression raised an error while pending decompressed data was being drained, as seen with `brotlicffi` 1.2 -- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13203`, :issue:`13249`. - Rejected control characters in the request target in the pure-Python HTTP parser, matching the llhttp-backed parser, which already refuses them \-- by :user:`arshsmith1`. *Related issues and pull requests on GitHub:* :issue:`13212`. - Stripped the trailing whitespace from header values in the C HTTP parser, so that it matches the pure-Python parser and :rfc:`9110#section-5.5` \-- by :user:`LuShadowX`. *Related issues and pull requests on GitHub:* :issue:`13246`. - Fixed the WebSocket reader rejecting a compressed data frame with close code 1002 when a control frame arrived before the first data frame (regression in 3.14.2) -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13274`. - Fixed internally retried requests sending a truncated body when the request data was a file object. *Related issues and pull requests on GitHub:* :issue:`13329`, :issue:`13330`. - Fixed event loop state possibly being corrupted on Python 3.12+ -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13346`. - Fixed the HTTP parser raising :exc:`~aiohttp.ClientPayloadError` when a fully received `Content-Length` body was pending completion -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13348`. - Bounded the per-read object overhead the WebSocket reader retains while reassembling a frame delivered across many small reads; the reads are joined once when the frame completes, and folded into a single buffer if they exceed a fragment cap, so a frame dribbled in tiny reads cannot pin unbounded per-read overhead -- by :user:`Dreamsorcerer` and :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13352`, :issue:`13488`. - Fixed requests pipelined behind a request whose upgrade the handler declined going unanswered once there were more of them than the per-connection queue holds. With the pure-Python parser the same requests were also served more than once -- by :user:`rodrigobnogueira`. *Related issues and pull requests on GitHub:* :issue:`13356`. - Reduced CPU consumption when encountering many concatenated members in a compressed payload and rejected large amounts of members -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13362`. - Fixed excessive memory consumption with small WebSocket messages -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13393`. - Fixed an integer overflow on too large messages -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13415`. - Switched multipart handling to use spooled temporary files to reduce number of file descriptors needed -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13426`. - Fixed a limit on message tail after an upgrade request -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13501`. - Fixed some edge case handling in multipart parts using base 64 encoding -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13509`. - Fixed Cython 3.3.0 failing to compile the WebSocket reader: dropped the `Final[...]` annotation from `ALLOWED_CLOSE_CODES` and the `int` annotation from the local `start_pos` in `WebSocketReader._feed_data`, both of which conflicted with declarations in `reader_c.pxd` under Cython 3.3.0 -- by :user:`Georgefifth`. *Related issues and pull requests on GitHub:* :issue:`13520`. - Fixed the WebSocket reader accepting a new data frame injected between the fragments of an in-progress message; per :rfc:`6455#section-5.4` every frame after the first fragment and before the `FIN` must be a continuation, and such a stream is now rejected as a protocol error -- by :user:`arshsmith1`. *Related issues and pull requests on GitHub:* :issue:`13553`. - Fixed a connection being eligible for reuse after its request was cancelled or failed while waiting for a `100 Continue` response or finalizing the body; the request headers were already sent, so reusing the connection corrupted the next request on it -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13579`. - Fixed `BaseRequest.http_range` not accepting case-insensitive range units -- by :user:`Manny7717`. *Related issues and pull requests on GitHub:* :issue:`13580`, :issue:`13581`. - Fixed `CookieJar.update_cookies()` to copy user-passed mutable `Morsel` objects -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13637`. - Fixed unbounded memory growth on a client WebSocket connection. A frame protocol error detaches the reader but leaves the connection upgraded, so a peer could stream unlimited data into an internal buffer when the application never called :meth:`~aiohttp.ClientWebSocketResponse.receive`; that data is now discarded, since nothing can parse it. Data arriving before the reader is installed is bounded by `read_bufsize`, which now applies to this buffer as well as to :attr:`~aiohttp.ClientResponse.content` \-- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13655`, :issue:`13743`. - Fixed pure-Python request parser not reading a body in a `HEAD` request -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13671`. - Fixed host-only cookie state being lost on expiration -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13674`. - Fixed a possible `OverflowError` on cookies and a connection not being closed properly -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13677`. - The first-request deadline now also closes connections whose first request body stalls, while a body that is still arriving extends the deadline instead of being interrupted -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13681`. - Fixed idle connections not being closed if no request was received -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13681`. - Fixed :meth:`~aiohttp.web.Application.add_domain` not routing a request to its domain application when the `Host` header carried a port and the domain was registered without one, or, for a wildcard domain, uppercase letters -- by :user:`rodrigobnogueira`. *Related issues and pull requests on GitHub:* :issue:`13693`. - Added empty `__slots__` to `AbstractRouteDef` so that `RouteDef` and `StaticDef` instances no longer carry an unused `__dict__`. *Related issues and pull requests on GitHub:* :issue:`13716`. - Fixed `BaseConnector(keepalive_timeout=None)` crashing on the second request to the same host with `TypeError: '<=' not supported between instances of 'float' and 'NoneType'` -- by :user:`ishan-1010`. *Related issues and pull requests on GitHub:* :issue:`13756`, :issue:`13757`. - Fixed a crash in :meth:`~aiohttp.BodyPartReader.read_chunk` on a body part with an explicit `Content-Length: 0`: the part fell through to the streaming read strategy, whose minimum chunk size assertion then failed for chunk sizes below the boundary length. Such parts now yield an immediate empty chunk, like any other part with a known length \-- by :user:`istoolsfox`. *Related issues and pull requests on GitHub:* :issue:`13758`, :issue:`13760`. - Fixed `Set-Cookie` parsing treating unrecognized attributes as additional cookies. Each `Set-Cookie` header now sets exactly one cookie and unrecognized attributes are ignored, per :rfc:`6265#section-5.2`, preventing a malicious server from creating an attacker-selected number of cookie objects (and correspondingly large outgoing `Cookie` headers) from a bounded amount of response data. `DummyCookieJar`, and `CookieJar` in safe mode for IP-address origins, no longer parse `Set-Cookie` headers at all -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13800`. - Fixed the web server trusting the scheme of an absolute-form request-target -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13821`. - Fixed `CookieJar.filter_cookies()` sending shared cookies (cookies without a `Domain` attribute) marked `Secure` over unencrypted connections -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13830`. - Fixed per-request cookies (the `cookies` argument of a request method) marked `Secure` not being sent to origins listed in `CookieJar`'s `treat_as_secure_origin` -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13833`. - Fixed the connection to an HTTP proxy staying open until garbage collection, and being reported as `Unclosed connection`, when sending the `CONNECT` request for an HTTPS tunnel failed -- by :user:`Garbsener`. *Related issues and pull requests on GitHub:* :issue:`13841`. - Resolved a redirect `Location` with the scheme of the current URL but without `//`, such as `http:/path` or `http:path`, against the current URL, as browsers do, instead of treating it as an absolute URL without a host \-- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13855`. - Rejected absolute-form request targets without `//` or with an empty host, such as `http:/example.com/` or `http:///example.com/`, before parsing them with yarl, which reads a host from them in its WHATWG mode; RFC 9110 requires a host for `http` and `https`. The invalid URL test data no longer uses `http:///example.com`, which such a yarl version parses as `http://example.com/`, as browsers do \-- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13858`. - Fixed :py:meth:`~aiohttp.StreamReader.readuntil` not finding a multi-byte separator whose bytes arrived in different chunks, which made it return data past the separator -- by :user:`andrewstellman`. *Related issues and pull requests on GitHub:* :issue:`13870`. - Fixed mixed-case `Content-Encoding` values (for example `Gzip`) being accepted by the parser but failing decompression, a regression from the CVE-2025-69224 hardening -- by :user:`muhammad-a-dev`. *Related issues and pull requests on GitHub:* :issue:`13894`. - Added limits to client cookie parsing, :class:`~aiohttp.CookieJar` storage and generated `Cookie` headers, with Firefox-style eviction, and fixed a replaced cookie keeping the previous cookie's expiry when the new cookie has none \-- by :user:`iamibi` and :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13930`. - Improved performance in domain matching with `Application.add_domain()` -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13943`. ## Deprecations (removal in next major release) - Deprecated `ClientResponse.output_size` and `ClientResponse.upload_complete`; use `aiohttp.UploadTracker` instead -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13579`. ## Removals and backward incompatible breaking changes - The WebSocket receive queue now only holds a weak reference to the `WebSocketReader` while parsing is stalled; code constructing a reader directly and passing it to `set_parser()` must keep its own strong reference to it, or frames the reader stopped short of parsing are lost with it -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13393`. - Removed the internal writer proxy used for upload progress accounting. `AbstractStreamWriter` gained an optional `on_body_write` callback that `write()` / `write_eof()` implementations must invoke with each accepted body chunk's byte length; custom writer implementations that do not call it will report `Payload.bytes_written` as `0` -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`13436`. - Increased minimum yarl version to 1.25.1 -- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13734`. - Changed `Set-Cookie` parsing to create exactly one cookie per field, as RFC 6265 and browsers do. Later `name=value` pairs and unknown attributes no longer create extra cookies, a leading pair such as `Path=/` or `$Version=1` is the cookie itself, and legacy `$Path` and `$Domain` attributes are ignored -- by :user:`iamibi`. *Related issues and pull requests on GitHub:* :issue:`13930`. ## Improved documentation - Documented valid request URL forms when using :class:`~aiohttp.UnixConnector`, including `base_url` with an HTTP host -- by :user:`muhammad-a-dev`. *Related issues and pull requests on GitHub:* :issue:`11324`, :issue:`13781`. - Corrected the documented signature of :meth:`~aiohttp.StreamReader.read_nowait`, whose `n` parameter defaults to `-1` rather than the `None` that was previously documented -- by :user:`LALITH0110`. *Related issues and pull requests on GitHub:* :issue:`13295`. - Added `interlock-cb`, an aiohttp client circuit breaker middleware, to the third-party libraries page -- by :user:`bagowix`. *Related issues and pull requests on GitHub:* :issue:`13336`. - Documented that `max_redirects=0` means no limit and that `allow_redirects=False` disables redirects -- by :user:`monasco`. *Related issues and pull requests on GitHub:* :issue:`13658`. - Corrected the documented signature of :py:meth:`~aiohttp.StreamReader.readuntil`, which showed a `str` separator although the method takes `bytes`, and documented its keyword-only `max_size` argument -- by :user:`hxperl`. *Related issues and pull requests on GitHub:* :issue:`13686`. - Replaced most of the `sphinx.ext.extlinks`-based roles in the documentation with :pypi:`sphinx-issues`, which ships the `:issue:`, `:pr:`, `:commit:` and `:user:` roles out of the box. Pull request references are now captioned `#N` instead of `PR #N`, and commit references as abbreviated, `@`-prefixed hashes \-- by :user:`aiolibsbot`. *Related issues and pull requests on GitHub:* :issue:`13752`. - Fixed the `Content-ID` example in the multipart docs, which used a constant missing from `aiohttp.hdrs` and a value that is not a valid message ID -- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13886`. ## Packaging updates and notes for downstreams - Started publishing an additional pure-Python wheel alongside the existing per-platform binary wheels and the `sdist` -- by :user:`webknjaz`. This gives users on platforms without a working C compiler, or without a matching pre-built wheel, an installable fallback that does not require compilation. *Related issues and pull requests on GitHub:* :issue:`7632`, :issue:`13388`. - Removed the `aiohttp/_websocket/reader_c.py` symlink from the source tree; the `aiohttp._websocket.reader_c` extension is now compiled directly from `reader_py.py` using `cython --module-name`, so distributions no longer include a `reader_c.py` file that showed up as an uncovered module in coverage reports -- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13457`. - Adopted :pep:`639` license metadata -- the license is now declared as the SPDX expression `Apache-2.0 AND MIT` and `license-files` moved to the `[project]` table, which raises the build-time requirement to `setuptools >= 77.0`. Built distributions now carry `License-Expression` instead of the legacy `License` field \-- by :user:`aiolibsbot`. *Related issues and pull requests on GitHub:* :issue:`13891`. ## Contributor-facing changes - The CI/CD is now in sync with the rest of the projects in terms of where the `cibuildwheel` workflow lives -- by :user:`webknjaz`. *Related commits on GitHub:* :commit:`59c0123d`. - Moved the pytest configuration from :file:`setup.cfg` to a dedicated :file:`pytest.ini` that follows the layout shared with `propcache` and other `aio-libs` projects. Compared to the old configuration, `minversion` is raised from `3.8.2` to `8.4`; `pytest-xdist` (`--numprocesses=auto`) and `pytest-cov` (`--cov`, `--cov-context=test`, `--no-cov-on-fail`) are enabled by default again, so pass `--numprocesses=0` and/or `--no-cov` to opt out, as the :file:`Makefile` targets and CI jobs now do where needed; `--doctest-modules`, `--strict-markers` and `faulthandler_timeout = 30` are enabled; `-v` is no longer added; empty parameter sets are marked `xfail` instead of skipped; `--junitxml` reports use `xunit1` with captured output and call-only durations; and `norecursedirs` skips more directories, including :file:`tests/isolated/` \-- by :user:`aiolibsbot`. *Related issues and pull requests on GitHub:* :issue:`12620`, :issue:`12621`. - Added check that change fragment matches PR number -- by :user:`Dreamsorcerer`. *Related issues and pull requests on GitHub:* :issue:`12788`. - CI now builds the `sdist` (and a pure-Python wheel) once, in a new `build-pure-python-dists` job, and shares that build across `test`, `autobahn`, `benchmark`, `build-wheels`, `test-mobile` and the `sdist`-based half of linting, instead of every one of those jobs checking out the repository and running `make cythonize` on its own \-- by :user:`webknjaz`. Linting is also now split into `lint-from-git` (the :file:`requirements/runtime-deps.in` sync check and docs spell-checking, which need real Git history) and `lint-from-sdist` (`mypy`, `slotscheck`, the changelog fragment check, and `twine check`, which build from the shared artifact instead), since an `sdist` tarball never contains :file:`.git`. *Related issues and pull requests on GitHub:* :issue:`13363`, :issue:`13388`. - Synchronized the `coverage.py` configuration (:file:`.coveragerc.toml` and :file:`.coveragerc-cython.toml`) with the pattern already established in :external+yarl:doc:`yarl <index>`, :external+multidict:doc:`multidict <index>`, `frozenlist` and other sibling projects \-- by :user:`webknjaz`. Both files now anchor package discovery through `source_pkgs` instead of relying on a same-named directory happening to exist relative to the working directory, and add a `[paths]` mapping so coverage recorded against an installed copy of `aiohttp` still combines correctly with coverage recorded from the Git checkout. CI now lets `pytest-cov` write `coverage.xml` directly via `--cov-report=xml` instead of a separate `coverage xml` step, and the Autobahn testsuite's subprocess-based coverage collection (which uses `coverage run --append`, incompatible with parallel mode) now opts out per-invocation via a `COVERAGE_PARALLEL_MODE` environment variable instead of trying to override it on the command line. *Related issues and pull requests on GitHub:* :issue:`13422`. - Stopped the benchmark CI job from hanging in the CodSpeed runner's apt install by installing `libc6-dbg` up front with a bounded retry, and raised the job timeout from 15 to 30 minutes -- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13489`. - Added benchmarks for reading masked WebSocket messages and fixed the existing read benchmarks, which stopped measuring the parser after the eighth large frame due to the queue limit -- by :user:`bdraco`. *Related issues and pull requests on GitHub:* :issue:`13561`. - Removed stale `filterwarnings` ignores from the pytest configuration that are no longer triggered by aiohttp, the supported Python versions or the pinned test dependencies -- by :user:`aiolibsbot`. *Related issues and pull requests on GitHub:* :issue:`13717`. - Dropped the leftover `PIP_USER` setting and the `pip --user` `PATH` prefix from the CI workflow; both became dead once the test jobs started provisioning Python via `astral-sh/setup-uv` \-- by :user:`aiolibsbot`. *Related issues and pull requests on GitHub:* :issue:`13718`, :issue:`13721`. - Changed the long host in the `Host` header tests to one that is not made only of digits, since yarl now parses such a host as an IP address in its default mode and rejects this one as out of range \-- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13861`. - Fixed `tools/gen.py` dropping a header name from the generated C lookup when two names shared a prefix that differed only in letter case, such as `Accept-CH` and `Accept-Charset`, and made the generated code compile without warnings -- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13886`. ## Miscellaneous internal changes - Avoided formatting an unused fallback `Date` header value when the response already has one -- by :user:`marcus-campbell`. *Related issues and pull requests on GitHub:* :issue:`13299`. - Improved header parsing performance in the C HTTP parser by reusing the :class:`~multidict.istr` built for a header name missing from `aiohttp.hdrs` the next time the same name arrives, from a bounded cache of up to 512 names of at most 64 bytes -- by :user:`asvetlov`. *Related issues and pull requests on GitHub:* :issue:`13887`. *** </details> <details> <summary>pygments/pygments (pygments)</summary> ### [`v2.20.0`](https://github.com/pygments/pygments/blob/HEAD/CHANGES#Version-2200) [Compare Source](https://github.com/pygments/pygments/compare/2.19.2...2.20.0) (released March 29th, 2026) - New lexers: - Rell ([#&#8203;2914](https://github.com/pygments/pygments/issues/2914)) - Updated lexers: - archetype: Fix catastrophic backtracking in GUID and ID patterns ([#&#8203;3064](https://github.com/pygments/pygments/issues/3064)) - ASN.1: Recognize minus sign and fix range operator ([#&#8203;3014](https://github.com/pygments/pygments/issues/3014), [#&#8203;3060](https://github.com/pygments/pygments/issues/3060)) - C++: Add C++26 keywords ([#&#8203;2955](https://github.com/pygments/pygments/issues/2955)), add integer literal suffixes ([#&#8203;2966](https://github.com/pygments/pygments/issues/2966)) - ComponentPascal: Fix `analyse_text` ([#&#8203;3028](https://github.com/pygments/pygments/issues/3028), [#&#8203;3032](https://github.com/pygments/pygments/issues/3032)) - Coq renamed to Rocq ([#&#8203;2883](https://github.com/pygments/pygments/issues/2883), [#&#8203;2908](https://github.com/pygments/pygments/issues/2908)) - Cython: Various improvements ([#&#8203;2932](https://github.com/pygments/pygments/issues/2932), [#&#8203;2933](https://github.com/pygments/pygments/issues/2933)) - Debian control: Improve architecture parsing ([#&#8203;3052](https://github.com/pygments/pygments/issues/3052)) - Devicetree: Add support for overlay/fragments ([#&#8203;3021](https://github.com/pygments/pygments/issues/3021)), add bytestring support ([#&#8203;3022](https://github.com/pygments/pygments/issues/3022)), fix catastrophic backtracking ([#&#8203;3057](https://github.com/pygments/pygments/issues/3057)) - Fennel: Various improvements ([#&#8203;2911](https://github.com/pygments/pygments/issues/2911)) - Haskell: Handle escape sequences in character literals ([#&#8203;3069](https://github.com/pygments/pygments/issues/3069), [#&#8203;1795](https://github.com/pygments/pygments/issues/1795)) - Java: Add module keywords ([#&#8203;2955](https://github.com/pygments/pygments/issues/2955)) - Lean4: Add operators `]'`, `]?`, `]!` ([#&#8203;2946](https://github.com/pygments/pygments/issues/2946)) - LESS: Support single-line comments ([#&#8203;3005](https://github.com/pygments/pygments/issues/3005)) - LilyPond: Update to 2.25.29 ([#&#8203;2974](https://github.com/pygments/pygments/issues/2974)) - LLVM: Support C-style comments ([#&#8203;3023](https://github.com/pygments/pygments/issues/3023), [#&#8203;2978](https://github.com/pygments/pygments/issues/2978)) - Lua(u): Fix catastrophic backtracking ([#&#8203;3047](https://github.com/pygments/pygments/issues/3047)) - Macaulay2: Update to 1.25.05 ([#&#8203;2893](https://github.com/pygments/pygments/issues/2893)), 1.25.11 ([#&#8203;2988](https://github.com/pygments/pygments/issues/2988)) - Mathematica: Various improvements ([#&#8203;2957](https://github.com/pygments/pygments/issues/2957)) - meson: Add additional operators ([#&#8203;2919](https://github.com/pygments/pygments/issues/2919)) - MySQL: Update keywords ([#&#8203;2970](https://github.com/pygments/pygments/issues/2970)) - org-Mode: Support both schedule and deadline ([#&#8203;2899](https://github.com/pygments/pygments/issues/2899)) - PHP: Add `__PROPERTY__` magic constant ([#&#8203;2924](https://github.com/pygments/pygments/issues/2924)), add reserved keywords ([#&#8203;3002](https://github.com/pygments/pygments/issues/3002)) - PostgreSQL: Add more keywords ([#&#8203;2985](https://github.com/pygments/pygments/issues/2985)) - protobuf: Fix namespace tokenization ([#&#8203;2929](https://github.com/pygments/pygments/issues/2929)) - Python: Add `t`-string support ([#&#8203;2973](https://github.com/pygments/pygments/issues/2973), [#&#8203;3009](https://github.com/pygments/pygments/issues/3009), [#&#8203;3010](https://github.com/pygments/pygments/issues/3010)) - Tablegen: Fix infinite loop ([#&#8203;2972](https://github.com/pygments/pygments/issues/2972), [#&#8203;2940](https://github.com/pygments/pygments/issues/2940)) - Tera Term macro: Add commands introduced in v5.3 through v5.6 ([#&#8203;2951](https://github.com/pygments/pygments/issues/2951)) - TOML: Support TOML 1.1.0 ([#&#8203;3026](https://github.com/pygments/pygments/issues/3026), [#&#8203;3027](https://github.com/pygments/pygments/issues/3027)) - Turtle: Allow empty comment lines ([#&#8203;2980](https://github.com/pygments/pygments/issues/2980)) - XML: Added `.xbrl` as file ending ([#&#8203;2890](https://github.com/pygments/pygments/issues/2890), [#&#8203;2891](https://github.com/pygments/pygments/issues/2891)) - Drop Python 3.8, and add Python 3.14 as a supported version ([#&#8203;2987](https://github.com/pygments/pygments/issues/2987), [#&#8203;3012](https://github.com/pygments/pygments/issues/3012)) - Various improvements to `autopygmentize` ([#&#8203;2894](https://github.com/pygments/pygments/issues/2894)) - Update `onedark` style to support more token types ([#&#8203;2977](https://github.com/pygments/pygments/issues/2977)) - Update `rtt` style to support more token types ([#&#8203;2895](https://github.com/pygments/pygments/issues/2895)) - Cache entry points to improve performance ([#&#8203;2979](https://github.com/pygments/pygments/issues/2979)) - Fix `xterm-256` color table ([#&#8203;3043](https://github.com/pygments/pygments/issues/3043)) - Fix `kwargs` dictionary getting mutated on each call ([#&#8203;3044](https://github.com/pygments/pygments/issues/3044)) ### [`v2.19.2`](https://github.com/pygments/pygments/blob/HEAD/CHANGES#Version-2192) [Compare Source](https://github.com/pygments/pygments/compare/2.19.1...2.19.2) (released June 21st, 2025) - Lua: Fix regression introduced in 2.19.0 ([#&#8203;2882](https://github.com/pygments/pygments/issues/2882), [#&#8203;2839](https://github.com/pygments/pygments/issues/2839)) </details> <details> <summary>Unstructured-IO/unstructured (unstructured)</summary> ### [`v0.24.1`](https://github.com/Unstructured-IO/unstructured/blob/HEAD/CHANGELOG.md#0241) [Compare Source](https://github.com/Unstructured-IO/unstructured/compare/0.24.0...0.24.1) ##### Fixes - **Fix stored XSS in v2 (ontology) HTML output** (GHSA-v5mq-3xhg-98m9): `partition_html(html_parser_version="v2")`, `elements_to_html()`, and `metadata.text_as_html` previously emitted untrusted document markup without output encoding, allowing attacker-controlled content (`on*` handlers, `javascript:` links, tag/attribute breakout) to execute when the HTML was viewed. Output is now sanitized — text and attribute values are HTML-escaped, event-handler attributes are dropped, tags/attributes are allowlisted, and URL schemes are filtered (`http`/`https`/`mailto`/`tel`/relative preserved; `data:` limited to raster image MIME types on `img[src]`). Legitimate formatting is unaffected. </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Berlin) - Branch creation - At any time (no schedule defined) - Automerge - At any time (no schedule defined) 🚦 **Automerge**: Disabled by config. Please merge this manually once you are satisfied. ♻ **Rebasing**: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox. 👻 **Immortal**: This PR will be recreated if closed unmerged. Get [config help](https://github.com/renovatebot/renovate/discussions) if that's undesired. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiI0NC4xNzguNSIsInVwZGF0ZWRJblZlciI6IjQ0LjI0MC4wIiwidGFyZ2V0QnJhbmNoIjoibWFpbiIsImxhYmVscyI6WyJkZXBlbmRlbmNpZXMiLCJzZWN1cml0eSJdfQ==-->
fix(deps): update security fixes [security]
All checks were successful
Test / test (pull_request) Successful in 3m23s
9667a9dfd1
renovate-bot force-pushed renovate/security from 9667a9dfd1
All checks were successful
Test / test (pull_request) Successful in 3m23s
to 27925fd09f
All checks were successful
Test / test (pull_request) Successful in 3m36s
2026-11-16 21:25:22 +00:00
Compare
All checks were successful
Test / test (pull_request) Successful in 3m36s
This pull request can be merged automatically.
This branch is out-of-date with the base branch
You are not authorized to merge this pull request.
View command line instructions

Checkout

From your project repository, check out a new branch and test the changes.
git fetch -u origin 'renovate/security:renovate/security'
git switch 'renovate/security'

Merge

Merge the changes and update on Forgejo.

Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.

git switch 'main'
git merge --no-ff 'renovate/security'
git switch 'renovate/security'
git rebase 'main'
git switch 'main'
git merge --ff-only 'renovate/security'
git switch 'renovate/security'
git rebase 'main'
git switch 'main'
git merge --no-ff 'renovate/security'
git switch 'main'
git merge --squash 'renovate/security'
git switch 'main'
git merge --ff-only 'renovate/security'
git switch 'main'
git merge 'renovate/security'
git push origin 'main'
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
dawid/rag-agent!111
No description provided.