<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T12:10:57.609642+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2021-41125</id>
    <title>CVE-2021-41125 — HTTP authentication credential leak to target websites in scrapy</title>
    <updated>2026-10-07T12:10:57.645584+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> scrapy</p>
<p>Scrapy is a high-level web crawling and scraping framework for Python. If you use `HttpAuthMiddleware` (i.e. the `http_user` and `http_pass` spider attributes) for HTTP authentication, all requests will expose your credentials to the request target. This includes requests generated by Scrapy components, such as `robots.txt` requests sent by Scrapy when the `ROBOTSTXT_OBEY` setting is set to `True`, or as requests reached through redirects. Upgrade to Scrapy 2.5.1 and use the new `http_auth_domain` spider attribute to control which domains are allowed to receive the configured HTTP authentication credentials. If you are using Scrapy 1.8 or a lower version, and upgrading to Scrapy 2.5.1 is not an option, you may upgrade to Scrapy 1.8.1 instead. If you cannot upgrade, set your HTTP authentication credentials on a per-request basis, using for example the `w3lib.http.basic_auth_header` function to convert your credentials into a value that you can assign to the `Authorization` header of your request, instead of defining your credentials globally using `HttpAuthMiddleware`.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2021-41125"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-7476-1</id>
    <title>USN-7476-1 — python-scrapy vulnerabilities</title>
    <updated>2026-10-07T12:10:57.645657+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:18.04:LTS: python-scrapy, Ubuntu:Pro:20.04:LTS: python-scrapy, Ubuntu:Pro:22.04:LTS: python-scrapy, Ubuntu:Pro:24.04:LTS: python-scrapy</p>
<p>It was discovered that Scrapy improperly exposed HTTP authentication 
credentials to request targets, including during redirects. An attacker 
could use this issue to gain unauthorized access to user accounts. This
issue only affected Ubuntu 18.04 LTS and Ubuntu 20.04 LTS. (CVE-2021-41125)</p>
<p>It was discovered that Scrapy did not remove the cookie header during
cross-domain redirects. An attacker could possibly use this issue to gain
unauthorized access to user accounts. This issue only affected Ubuntu 18.04
LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2022-0577)</p>
<p>It was discovered that Scrapy inefficiently parsed XML content. An
attacker could use this issue to cause a denial of service by sending a
crafted XML response. This issue only affected Ubuntu 18.04 LTS,
Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2024-1892)</p>
<p>It was discovered that Scrapy did not properly check response size during
decompression. An attacker could send a crafted response that would
exhaust memory and cause a denial of service. This issue only affected
Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2024-3572)</p>
<p>It was discovered that Scrapy did not remove the authorization header
during cross-domain redirects. An attacker could possibly use this issue
to gain unauthorized access to user accounts. This issue only affected 
Ubuntu 18.04 LTS, Ubuntu 20.04 LTS, and Ubuntu 22.04 LTS. (CVE-2024-3574)</p>
<p>It was discovered that Scrapy did not remove the authorization header
during redirects…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-7476-1"/>
  </entry>
</feed>
