How severe is GHSA-527g-3w9m-29hv?

GHSA-527g-3w9m-29hv has a CVSS score of 4.8/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-527g-3w9m-29hv?

GHSA-527g-3w9m-29hv affects the following packages: mitmproxy (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-527g-3w9m-29hv?

Update mitmproxy to 12.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-527g-3w9m-29hv is resolved across your whole dependency graph.

How do I detect GHSA-527g-3w9m-29hv in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mitmproxy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-527g-3w9m-29hv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-527g-3w9m-29hv?

O3 pinpoints whether GHSA-527g-3w9m-29hv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-527g-3w9m-29hv actively exploited in the wild?

No public exploit code has been indexed for GHSA-527g-3w9m-29hv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-527g-3w9m-29hv published, and has it been updated?

GHSA-527g-3w9m-29hv was published on April 14, 2026 and was last updated on June 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-527g-3w9m-29hv

MEDIUM

GHSA-527g-3w9m-29hv is a medium-severity (CVSS 4.8) vulnerability in mitmproxy. O3 Security confirms whether GHSA-527g-3w9m-29hv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

mitmproxy has an LDAP Injection

Also known asCVE-2026-40606PYSEC-2026-92

Published

Apr 14, 2026

Updated

Jun 6, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐍mitmproxy

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Impact

In mitmproxy 12.2.1 and below, the builtin LDAP proxy authentication does not correctly sanitize the username when querying the LDAP server. This allows a malicious client to bypass authentication.

Only mitmproxy instances using the proxyauth option with LDAP are affected. This option is not enabled by default.

Patches

The vulnerability has been fixed in mitmproxy 12.2.2 and above.

Acknowledgements

We thank Yue (Knox) Liu (@yueyueL) for responsibly disclosing this vulnerability to the mitmproxy team.

Timeline

2025-12-08: Received initial report.
2025-12-09: Verified report and confirmed receipt.
2026-01-02: Informed researcher that patch will be part of the next regular patch release.
2026-04-12: Published patch release and advisory.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`mitmproxy`	all versions	12.2.2

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for mitmproxy. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update mitmproxy to 12.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-527g-3w9m-29hv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-527g-3w9m-29hv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-527g-3w9m-29hv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact In mitmproxy 12.2.1 and below, the builtin LDAP proxy authentication does not correctly sanitize the username when querying the LDAP server. This allows a malicious client to bypass authentication. Only mitmproxy instances using the `proxyauth` option with LDAP are affected. This option is not enabled by default. ### Patches The vulnerability has been fixed in mitmproxy 12.2.2 and above. ### Acknowledgements We thank Yue (Knox) Liu (@yueyueL) for responsibly disclosing this vulnerability to the mitmproxy team. ### Timeline - **2025-12-08**: Received initial report. - **2025-

O3 Security · Impact-Aware SCA

Is GHSA-527g-3w9m-29hv in your dependencies?

O3 detects GHSA-527g-3w9m-29hv across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works