# CVE-2025-67485: HTTP/HTTPS Traffic Interception Bypass in mad-proxy

> Attackers can bypass HTTP/HTTPS traffic interception rules in mad-proxy, potentially exposing sensitive traffic to unauthorized parties.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 10 Dec 2025
- **Also known as:** GHSA-wx63-35hw-2482, PYSEC-2026-1596

## What is CVE-2025-67485?

CVE-2025-67485 is a medium-severity vulnerability in machphy mad-proxy, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mad-proxy is a Python-based HTTP/HTTPS proxy server for detection and blocking of malicious web activity using custom security policies. Versions 0.3 and below allow attackers to bypass HTTP/HTTPS traffic interception rules, potentially exposing sensitive traffic. This issue does not have a fix at the time of publication.

Weakness: CWE-693 (Protection Mechanism Failure)

## Which versions are affected by CVE-2025-67485?

3 open source packages ship an affected version, including mad-proxy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mad-proxy` | PyPI | All versions to 0.3 | None |
| `mad-proxy` | PyPI | All versions to 0.3 | None |
| `mad-proxy` | PyPI | All versions to 0.3 | None |

Products: Machphy Mad-Proxy.

## How do I fix CVE-2025-67485?

No fix has been published for CVE-2025-67485 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-67485 being exploited?

There is no known exploitation of CVE-2025-67485 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67485 and fix it if it is affected.

What it is: CVE-2025-67485 is a medium-severity vulnerability in machphy mad-proxy, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67485 in the wild and no public exploit code.

Affected packages and fixed versions:
- mad-proxy (PyPI): affected all versions up to 0.3; no fix listed
- mad-proxy (PyPI): affected all versions up to 0.3; no fix listed
- mad-proxy (PyPI): affected all versions up to 0.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67485/ (Markdown: https://insights.sbomify.com/CVE-2025-67485/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67485
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67485
- OSV: https://osv.dev/vulnerability/CVE-2025-67485

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67485/
Summaries are generated and may contain mistakes; the official description above is the record.