Unsafe handling of user-specified cookies in treq

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

7.1 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2022-23607: 1.08% estimated exploitation activity in the next 30 days; percentile 65.22 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact Treq's request methods (treq.get, treq.post, HTTPClient.request, HTTPClient.get, etc.) accept cookies as a dictionary, for example: Such cookies are not bound to a single domain, and are therefore sent to every domain ("supercookies"). This can potentially cause sensitive information to leak upon an HTTP redirect to a different domain., e.g. should https://example.com redirect to http://cloudstorageprovider.com the latter will receive the cookie session. Patches Treq 2021.1.0 and later bind cookies given to request methods (treq.request, treq.get, HTTPClient.request, HTTPClient.get, etc.) to the origin of the url parameter. Workarounds Instead of passing a dictionary as the cookies argument, pass a http.cookiejar.CookieJar instance with properly domain- and scheme-scoped cookies in it: References Originally reported at huntr.dev A related issue in the handling of HTTP basic authentication was addressed in Twisted 22.1 (GHSA-92x2-jw7w-xvvx, CVE-2022-21712).

Published by the source

1 Feb 2022, 00:43 UTC

Last modified by the source

13 Nov 2024, 23:23 UTC

Source last checked

26 Oct 2026, 13:26 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fhpf-pp6p-55qc

2. Revision 2 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-fhpf-pp6p-55qc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-23607

Advisory: Unsafe handling of user-specified cookies in treq
IDs: CVE-2022-23607, GHSA-fhpf-pp6p-55qc
Record: https://patchnext.com/advisories/cve-2022-23607 (revision 3, source checked 26 Oct 2026, 13:26 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: treq 22.1.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI treq: affected < 22.1.0; fixed in 22.1.0

## Suggested inspection (read-only)
- `python -m pip show treq`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on treq.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-fhpf-pp6p-55qc (OSV record GHSA-fhpf-pp6p-55qc lists affected ranges: PyPI treq >=0 <22.1.0 (fixed))
- Verified: https://github.com/advisories/GHSA-fhpf-pp6p-55qc (GitHub-reviewed advisory GHSA-fhpf-pp6p-55qc lists affected ranges: PyPI treq >=0 <22.1.0)

Commands are suggestions: review each one before running it.