Mitmweb API Authentication Bypass Using Proxy Server
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mitmproxy | mitmproxy | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Mitmproxy | Mitmproxy | — |
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2025-3147 | Mitmweb API Authentication Bypass Using Proxy Server |
Github GHSA |
GHSA-wg33-5h85-7q5p | Mitmweb API Authentication Bypass Using Proxy Server |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.866% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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's proxy server (bound to `*:8080` by default) to access mitmweb'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. | |
| Title | Mitmweb API Authentication Bypass Using Proxy Server | |
| Weaknesses | CWE-288 CWE-441 |
|
| References |
| |
| Metrics |
cvssV4_0
|