<?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-03T22:32:32.203374+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/bdu:2025-04191</id>
    <title>bdu:2025-04191</title>
    <updated>2026-10-03T22:32:33.455558+00:00</updated>
    <content>bdu:2025-04191</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2025-04191"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2021-28363</id>
    <title>Withdrawn: BELL-CVE-2021-28363 — CVE-2021-28363 does not affect BellSoft software</title>
    <updated>2026-10-03T22:32:33.455602+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <strong>Withdrawn by the publisher.</strong>
        </p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2021-28363"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/brew-ansible-cve-2021-28363</id>
    <title>BREW-ansible-CVE-2021-28363 — Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection</title>
    <updated>2026-10-03T22:32:33.455622+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Homebrew: ansible</p>
<p>### Impact</p>
<p>Users who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via `proxy_config`.
Only the default SSLContext is impacted.</p>
<p>### Patches</p>
<p>[urllib3 &gt;=1.26.4 has the issue resolved](https://github.com/urllib3/urllib3/releases/tag/1.26.4). urllib3&lt;1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies.</p>
<p>### Workarounds</p>
<p>Upgrading is recommended as this is a minor release and not likely to break current usage.</p>
<p>Configuring an `SSLContext` with `check_hostname=True` and passing via `proxy_config` instead of relying on the default `SSLContext`</p>
<p>### For more information
If you have any questions or comments about this advisory:
* Email us at [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/brew-ansible-cve-2021-28363"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2021-avi-490</id>
    <title>certfr-2021-avi-490 — De multiples vulnérabilités ont été découvertes dans IBM Spectrum
Protect. Certaines d'entre elles permettent à un atta…</title>
    <updated>2026-10-03T22:32:33.455663+00:00</updated>
    <content>certfr-2021-avi-490</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2021-avi-490"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-ak39245</id>
    <title>CLEANSTART-2026-AK39245 — Security fix for CVE-2021-28363 applied in: py3-urllib3 1.26.4-r0</title>
    <updated>2026-10-03T22:32:33.455679+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> CleanStart: py3-urllib3</p>
<p>Security vulnerability affects the py3-urllib3 package. This issue is resolved in later releases. See references for vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-ak39245"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-25977</id>
    <title>EUVD-2026-25977</title>
    <updated>2026-10-03T22:32:33.455698+00:00</updated>
    <content>EUVD-2026-25977</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-25977"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2021-28363</id>
    <title>fkie_cve-2021-28363</title>
    <updated>2026-10-03T22:32:33.455709+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. The initial connection to the HTTPS proxy (if an SSLContext isn't given via proxy_config) doesn't verify the hostname of the certificate. This means certificates for different servers that still validate properly with the default urllib3 SSLContext will be silently accepted.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2021-28363"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5phf-pp7p-vc2r</id>
    <title>GHSA-5phf-pp7p-vc2r — Using default SSLContext for HTTPS requests in an HTTPS proxy doesn't verify certificate hostname for proxy connection</title>
    <updated>2026-10-03T22:32:33.455731+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: urllib3</p>
<p>### Impact</p>
<p>Users who are using an HTTPS proxy to issue HTTPS requests and haven't configured their own SSLContext via `proxy_config`.
Only the default SSLContext is impacted.</p>
<p>### Patches</p>
<p>[urllib3 &gt;=1.26.4 has the issue resolved](https://github.com/urllib3/urllib3/releases/tag/1.26.4). urllib3&lt;1.26 is not impacted due to not supporting HTTPS requests via HTTPS proxies.</p>
<p>### Workarounds</p>
<p>Upgrading is recommended as this is a minor release and not likely to break current usage.</p>
<p>Configuring an `SSLContext` with `check_hostname=True` and passing via `proxy_config` instead of relying on the default `SSLContext`</p>
<p>### For more information
If you have any questions or comments about this advisory:
* Email us at [sethmichaellarson@gmail.com](mailto:sethmichaellarson@gmail.com)</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5phf-pp7p-vc2r"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2021-28363</id>
    <title>gsd-2021-28363</title>
    <updated>2026-10-03T22:32:33.455758+00:00</updated>
    <content>gsd-2021-28363</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2021-28363"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/icsa-23-348-10</id>
    <title>ICSA-23-348-10 — Siemens SIMATIC S7-1500</title>
    <updated>2026-10-03T22:32:33.455770+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>expat 2.1.0 and earlier does not properly handle entities expansion unless an application developer uses the XML_SetEntityDeclHandler function, which allows remote attackers to cause a denial of service (resource consumption), send HTTP requests to intranet servers, or read arbitrary files via a crafted XML document, aka an XML External Entity (XXE) issue.  NOTE: it could be argued that because expat already provides the ability to disable external entity expansion, the responsibility for resolving this issue lies with application developers; according to this argument, this entry should be REJECTed, and each affected application would need its own CVE. shadow: TOCTOU (time-of-check time-of-use) race condition when copying and removing directory trees run-mailcap in the Debian mime-support package before 3.52-1+deb7u1 allows context-dependent attackers to execute arbitrary commands via shell metacharacters in a filename. In Python (aka CPython) up to 3.10.8, the mailcap module does not add escape characters into commands discovered in the system mailcap file. This may allow attackers to inject shell commands into applications that call mailcap.findmatch with untrusted input (if they lack validation of user-provided filenames or arguments). The fix is also back-ported to 3.7, 3.8, 3.9 Use-after-free vulnerability in bzip2recover in bzip2 1.0.6 allows remote attackers to cause a denial of service (crash) via a crafted bzip2 file, related to block ends set to before the start o…</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/icsa-23-348-10"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2021-28363</id>
    <title>msrc_CVE-2021-28363 — The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to H…</title>
    <updated>2026-10-03T22:32:33.457050+00:00</updated>
    <content>msrc_CVE-2021-28363</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2021-28363"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/pysec-2021-59</id>
    <title>PYSEC-2021-59</title>
    <updated>2026-10-03T22:32:33.457071+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: urllib3</p>
<p>The urllib3 library 1.26.x before 1.26.4 for Python omits SSL certificate validation in some cases involving HTTPS to HTTPS proxies. The initial connection to the HTTPS proxy (if an SSLContext isn't given via proxy_config) doesn't verify the hostname of the certificate. This means certificates for different servers that still validate properly with the default urllib3 SSLContext will be silently accepted.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/pysec-2021-59"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhba-2021:1147</id>
    <title>RHBA-2021:1147 — Red Hat Bug Fix Advisory: OpenShift Container Platform 3.11.420 bug fix and enhancement update</title>
    <updated>2026-10-03T22:32:33.457093+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>python-urllib3: HTTPS proxy host name not validated when using default SSLContext</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhba-2021:1147"/>
  </entry>
</feed>
