# Scrapy HTTP authentication credentials potentially leaked to target websites

Advisory record · `GHSA-jwqp-28gf-p498`

- **Identifiers:** `GHSA-jwqp-28gf-p498` · `CVE-2021-41125` · `PYSEC-2021-363`
- **State:** Confirmed
- **Severity:** CVSS 5.7 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-522](https://cwe.mitre.org/data/definitions/522.html)
- **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) · [Hard-coded credentials](https://agentprime.io/advisories/tag/hard-coded-credentials.md)
- **Published:** 6 Oct 2021
- **Updated:** 8 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 6 Oct 2021, 17:46 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `scrapy` (PyPI): affected `<1.8.1 || >=2.0.0, <2.5.1`; fixed in `1.8.1`, `2.5.1`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.7 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.013, the 70th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 6 Oct 2021. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-jwqp-28gf-p498](https://github.com/advisories/GHSA-jwqp-28gf-p498)
- [OSV: GHSA-jwqp-28gf-p498](https://osv.dev/vulnerability/GHSA-jwqp-28gf-p498)
- <https://github.com/scrapy/scrapy/security/advisories/GHSA-jwqp-28gf-p498>
- <https://nvd.nist.gov/vuln/detail/CVE-2021-41125>
- <https://github.com/scrapy/scrapy/commit/b01d69a1bf48060daec8f751368622352d8b85a6>
- <https://github.com/pypa/advisory-database/tree/main/vulns/scrapy/PYSEC-2021-363.yaml>
- <https://github.com/scrapy/scrapy>
- <https://lists.debian.org/debian-lts-announce/2022/03/msg00021.html>
- <https://w3lib.readthedocs.io/en/latest/w3lib.html#w3lib.http.basic_auth_header>
- <http://doc.scrapy.org/en/latest/topics/downloader-middleware.html#module-scrapy.downloadermiddlewares.httpauth>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-jwqp-28gf-p498>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-jwqp-28gf-p498/>. Everything for agents: <https://agentprime.io/llms.txt>.