Skip to main content
CVE-2024-34069VulnerabilityPublished Updated

Mapproxy: Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain

Affects mapproxySource GCVE Database

0
Compare

Public exploit available (Metasploit) · CVSS 7.5 High : upgrade to 3.1.1 as a priority.

Data as of 18 Nov 2026, 18:03 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 3.1.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    1 Metasploit module

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade mapproxy to 3.1.1.

Affected software

ProductAffectedFixed in
Homebrewmapproxypkg:brew/mapproxyOther threatsAffected
  • >=2.1.1 <3.1.1
Fixed in
  • 3.1.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Mapproxy to version 3.1.1 or later, where the vulnerability is fixed. Until patched, avoid interacting with untrusted domains that could trigger the debugger and do not enter debugger PINs prompted by suspicious sources. There is no indication that other mitigations fully prevent exploitation.

Description

A vulnerability in the Werkzeug debugger used by Mapproxy versions >=2.1.1 and <3.1.1 allows remote code execution if an attacker can trick a developer into interacting with a malicious domain and entering the debugger PIN. Successful exploitation grants access to the debugger even when it is restricted to localhost. The vulnerability requires guessing a URL that triggers the debugger in the developer's application.

References

Community reviews

Loading reviews…