CVE-2025-67485
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-10

Last updated on: 2026-03-09

Assigner: GitHub, Inc.

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-10
Last Modified
2026-03-09
Generated
2026-05-07
AI Q&A
2025-12-10
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
machphy mad-proxy to 0.3 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-693 The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability in mad-proxy versions 0.3 and below allows attackers to bypass HTTP/HTTPS traffic interception rules. As a result, malicious actors can evade detection and blocking mechanisms designed to monitor and control web traffic, potentially exposing sensitive data transmitted through the proxy.


How can this vulnerability impact me? :

The vulnerability can lead to exposure of sensitive traffic because attackers can bypass the proxy's interception rules. This means that malicious or unauthorized traffic might go undetected, increasing the risk of data leakage or compromise of confidential information.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows attackers to bypass HTTP/HTTPS traffic interception rules, potentially exposing sensitive traffic. This exposure of sensitive data could negatively impact compliance with standards and regulations such as GDPR and HIPAA, which require protection of sensitive information during transmission. However, the provided resources do not explicitly discuss compliance implications. [1]


What immediate steps should I take to mitigate this vulnerability?

Upgrade mad-proxy to version 0.4 or later, as this version addresses the vulnerability allowing bypass of HTTP/HTTPS traffic interception rules. Until an upgrade is possible, consider disabling mad-proxy or restricting its use to trusted environments to minimize exposure. [1]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart