### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

We observed that version 1.83.8 and above is using `aiohttp==3.13.3` while older version (1.83.7) uses `aiohttp==3.13.5`.

There are 10 CVEs that are fixed in `aiohttp==3.13.5`. Is this change to use the older version intentional? Are there plans to use latest version of aiohttp to avoid CVEs. If it is not can you please upgrade the version to 3.13.4 or above. Thank you.

### Steps to Reproduce

1. Install latest litellm. 2. Scan for CVEs on the dependency chain. There will be 10 CVEs on aiohttp. 3. Install version 1.83.7. 4. Scan for CVEs on the dependency chain. There will be 0 CVEs on aiohttp.

### Relevant log output

```shell Logs from litellm==1.83.7 install

Collecting litellm==1.83.7 Downloading litellm-1.83.7-py3-none-any.whl.metadata (31 kB) Collecting aiohttp==3.13.5 (from litellm==1.83.7) Downloading aiohttp-3.13.5-cp313-cp313-macosx_11_0_arm64.whl.metadata (8.1 kB)

Logs from litellm==1.83.8 install

Collecting aiohttp==3.13.3 (from litellm==1.83.8) Downloading aiohttp-3.13.3-cp313-cp313-macosx_11_0_arm64.whl.metadata (8…