GHSA-7vwr-g6pm-9hc8
Cookie leakage between different users in fastapi-proxy-lib
Impact
In the implementation of version 0.0.1, requests from different user clients are processed using a shared httpx.AsyncClient.
However, one oversight is that the httpx.AsyncClient will persistently store cookies based on the set-cookie response header sent by the target server and share these cookies across different user requests.
This results in a cookie leakage issue among all user clients sharing the same httpx.AsyncClient.
Patches
It's fixed in 0.1.0
Workarounds
If you insist 0.0.1:
- Do not use
ForwardHttpProxyat all. - Do not use
ReverseHttpProxyorReverseWebSocketProxyfor any servers that may potentially send aset-cookieresponse.
However, it's best to upgrade to the latest version.
References
fixed in #10
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- None
- Availability
- None
What each source reports
GitHub Advisories Score used
Cookie leakage between different users in fastapi-proxy-lib
Impact
In the implementation of version 0.0.1, requests from different user clients are processed using a shared httpx.AsyncClient.
However, one oversight is that the httpx.AsyncClient will persistently store cookies based on the set-cookie response header sent by the target server and share these cookies across different user requests.
This results in a cookie leakage issue among all user clients sharing the same httpx.AsyncClient.
Patches
It's fixed in 0.1.0
Workarounds
If you insist 0.0.1:
- Do not use
ForwardHttpProxyat all. - Do not use
ReverseHttpProxyorReverseWebSocketProxyfor any servers that may potentially send aset-cookieresponse.
However, it's best to upgrade to the latest version.
References
fixed in #10
- Record
GHSA-7vwr-g6pm-9hc8- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
OSV
Cookie leakage between different users in fastapi-proxy-lib
Impact
In the implementation of version 0.0.1, requests from different user clients are processed using a shared httpx.AsyncClient.
However, one oversight is that the httpx.AsyncClient will persistently store cookies based on the set-cookie response header sent by the target server and share these cookies across different user requests.
This results in a cookie leakage issue among all user clients sharing the same httpx.AsyncClient.
Patches
It's fixed in 0.1.0
Workarounds
If you insist 0.0.1:
- Do not use
ForwardHttpProxyat all. - Do not use
ReverseHttpProxyorReverseWebSocketProxyfor any servers that may potentially send aset-cookieresponse.
However, it's best to upgrade to the latest version.
References
fixed in #10
- Record
GHSA-7vwr-g6pm-9hc8- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
fastapi-proxy-libPyPI | before 0.1.0 | 0.1.0 |
fastapi-proxy-libPyPI | before 0.1.0, plus listed versions 0.0.1b0 | 0.1.0 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-7vwr-g6pm-9hc8 is a high vulnerability (CVSS 7.5) in fastapi-proxy-lib, published December 1, 2023. No source lists public exploit code. Fixed in fastapi-proxy-lib 0.1.0.