https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 04:56:28 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-215123 EUVD-2026-215123 https://cve.radiocsirt.org/vuln/euvd-2026-215123 https://cve.radiocsirt.org/vuln/fkie_cve-2025-23217 <p>mitmproxy is a interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers and mitmweb is a web-based interface for mitmproxy. In mitmweb 11.1.1 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the cannot access the API directly, they can access the API through the proxy. An attacker may be able to escalate this SSRF-style access to remote code execution. The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. This vulnerability has been fixed in mitmproxy 11.1.2 and above. Users are advised to upgrade. There are no known workarounds for this vulnerability.</p> <p>mitmproxy is a interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers and mitmweb is a web-based interface for mitmproxy. In mitmweb 11.1.1 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the cannot access the API directly, they can access the API through the proxy. An attacker may be able to escalate this SSRF-style access to remote code execution. The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. This vulnerability has been fixed in mitmproxy 11.1.2 and above. Users are advised to upgrade. There are no known workarounds for this vulnerability.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-23217 https://cve.radiocsirt.org/vuln/ghsa-wg33-5h85-7q5p <p><strong>Affected:</strong> PyPI: mitmproxy</p> <p>### Impact In mitmweb 11.1.0 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the client cannot access the API directly (good), they can access the API through the proxy (bad). An attacker may be able to escalate this [SSRF](https://en.wikipedia.org/wiki/Server-side_request_forgery)-style access to remote code execution.</p> <p>The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. The `block_global` option, which is enabled by default, blocks connections originating from publicly-routable IP addresses in the proxy. The attacker needs to be in the same local network.</p> <p>### Patches</p> <p>The vulnerability has been fixed in mitmproxy 11.1.2 and above.</p> <p>### Acknowledgements</p> <p>We thank Stefan Grönke (@gronke) for reporting this vulnerability as part of a security audit by [Radically Open Security](https://www.radicallyopensecurity.com/). This audit was supported by the [NGI0 Entrust fund](https://nlnet.nl/entrust/) established by [NLnet](https://nlnet.nl/).</p> <p>### Timeline</p> <p>- **2025-01-14**: Received initial report. - **2025-01-14**: Verified report and confirmed receipt. - **2025-01-19**: Shared patch with researcher. - **2025-02-04**: Received final confirmation that patch is working. - **2025-02-05**: Published patched release and advisory.</p> <p><strong>Affected:</strong> PyPI: mitmproxy</p> <p>### Impact In mitmweb 11.1.0 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the client cannot access the API directly (good), they can access the API through the proxy (bad). An attacker may be able to escalate this [SSRF](https://en.wikipedia.org/wiki/Server-side_request_forgery)-style access to remote code execution.</p> <p>The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. The `block_global` option, which is enabled by default, blocks connections originating from publicly-routable IP addresses in the proxy. The attacker needs to be in the same local network.</p> <p>### Patches</p> <p>The vulnerability has been fixed in mitmproxy 11.1.2 and above.</p> <p>### Acknowledgements</p> <p>We thank Stefan Grönke (@gronke) for reporting this vulnerability as part of a security audit by [Radically Open Security](https://www.radicallyopensecurity.com/). This audit was supported by the [NGI0 Entrust fund](https://nlnet.nl/entrust/) established by [NLnet](https://nlnet.nl/).</p> <p>### Timeline</p> <p>- **2025-01-14**: Received initial report. - **2025-01-14**: Verified report and confirmed receipt. - **2025-01-19**: Shared patch with researcher. - **2025-02-04**: Received final confirmation that patch is working. - **2025-02-05**: Published patched release and advisory.</p> https://cve.radiocsirt.org/vuln/ghsa-wg33-5h85-7q5p https://cve.radiocsirt.org/vuln/opensuse-su-2025:14762-1 <p>python312-mitmproxy-11.1.2-1.1 on GA media</p> <p>python312-mitmproxy-11.1.2-1.1 on GA media</p> https://cve.radiocsirt.org/vuln/opensuse-su-2025:14762-1 https://cve.radiocsirt.org/vuln/pysec-2026-1630 <p><strong>Affected:</strong> PyPI: mitmproxy</p> <p>### Impact In mitmweb 11.1.0 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the client cannot access the API directly (good), they can access the API through the proxy (bad). An attacker may be able to escalate this [SSRF](https://en.wikipedia.org/wiki/Server-side_request_forgery)-style access to remote code execution.</p> <p>The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. The `block_global` option, which is enabled by default, blocks connections originating from publicly-routable IP addresses in the proxy. The attacker needs to be in the same local network.</p> <p>### Patches</p> <p>The vulnerability has been fixed in mitmproxy 11.1.2 and above.</p> <p>### Acknowledgements</p> <p>We thank Stefan Grönke (@gronke) for reporting this vulnerability as part of a security audit by [Radically Open Security](https://www.radicallyopensecurity.com/). This audit was supported by the [NGI0 Entrust fund](https://nlnet.nl/entrust/) established by [NLnet](https://nlnet.nl/).</p> <p>### Timeline</p> <p>- **2025-01-14**: Received initial report. - **2025-01-14**: Verified report and confirmed receipt. - **2025-01-19**: Shared patch with researcher. - **2025-02-04**: Received final confirmation that patch is working. - **2025-02-05**: Published patched release and advisory.</p> <p><strong>Affected:</strong> PyPI: mitmproxy</p> <p>### Impact In mitmweb 11.1.0 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the client cannot access the API directly (good), they can access the API through the proxy (bad). An attacker may be able to escalate this [SSRF](https://en.wikipedia.org/wiki/Server-side_request_forgery)-style access to remote code execution.</p> <p>The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. The `block_global` option, which is enabled by default, blocks connections originating from publicly-routable IP addresses in the proxy. The attacker needs to be in the same local network.</p> <p>### Patches</p> <p>The vulnerability has been fixed in mitmproxy 11.1.2 and above.</p> <p>### Acknowledgements</p> <p>We thank Stefan Grönke (@gronke) for reporting this vulnerability as part of a security audit by [Radically Open Security](https://www.radicallyopensecurity.com/). This audit was supported by the [NGI0 Entrust fund](https://nlnet.nl/entrust/) established by [NLnet](https://nlnet.nl/).</p> <p>### Timeline</p> <p>- **2025-01-14**: Received initial report. - **2025-01-14**: Verified report and confirmed receipt. - **2025-01-19**: Shared patch with researcher. - **2025-02-04**: Received final confirmation that patch is working. - **2025-02-05**: Published patched release and advisory.</p> https://cve.radiocsirt.org/vuln/pysec-2026-1630 https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-23217 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: mitmproxy, Ubuntu:18.04:LTS: mitmproxy, Ubuntu:20.04:LTS: mitmproxy, Ubuntu:22.04:LTS: mitmproxy, Ubuntu:24.04:LTS: mitmproxy, Ubuntu:25.10: mitmproxy, Ubuntu:26.04:LTS: mitmproxy</p> <p>mitmproxy is a interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers and mitmweb is a web-based interface for mitmproxy. In mitmweb 11.1.1 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the cannot access the API directly, they can access the API through the proxy. An attacker may be able to escalate this SSRF-style access to remote code execution. The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. This vulnerability has been fixed in mitmproxy 11.1.2 and above. Users are advised to upgrade. There are no known workarounds for this vulnerability.</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: mitmproxy, Ubuntu:18.04:LTS: mitmproxy, Ubuntu:20.04:LTS: mitmproxy, Ubuntu:22.04:LTS: mitmproxy, Ubuntu:24.04:LTS: mitmproxy, Ubuntu:25.10: mitmproxy, Ubuntu:26.04:LTS: mitmproxy</p> <p>mitmproxy is a interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers and mitmweb is a web-based interface for mitmproxy. In mitmweb 11.1.1 and below, a malicious client can use mitmweb&#39;s proxy server (bound to `*:8080` by default) to access mitmweb&#39;s internal API (bound to `127.0.0.1:8081` by default). In other words, while the cannot access the API directly, they can access the API through the proxy. An attacker may be able to escalate this SSRF-style access to remote code execution. The mitmproxy and mitmdump tools are unaffected. Only mitmweb is affected. This vulnerability has been fixed in mitmproxy 11.1.2 and above. Users are advised to upgrade. There are no known workarounds for this vulnerability.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2025-23217