Skip to main content
CVE-2024-34069VulnerabilityPublished Updated

Aws sam cli: Werkzeug debugger vulnerable to remote execution when interacting with attacker controlled domain

Affects aws-sam-cliSource GCVE Database

0
Compare

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

Data as of 18 Nov 2026, 17:51 UTC

CVSS 3.1 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 1.116.0_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 aws-sam-cli to 1.116.0_1.

Affected software

ProductAffectedFixed in
Homebrewaws-sam-clipkg:brew/aws-sam-cliOther threatsAffected
  • >=1.70.0 <1.116.0_1
Fixed in
  • 1.116.0_1

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

AI-suggested

Upgrade aws-sam-cli to version 1.116.0_1 or later, where this vulnerability is fixed. Avoid interacting with untrusted domains that could trigger the debugger. Since a patch is available, applying the official fix is the recommended mitigation.

Description

A vulnerability in the Werkzeug debugger used by aws-sam-cli versions from 1.70.0 up to but not including 1.116.0_1 allows remote code execution. An attacker who can trick a developer into interacting with a domain they control and entering the debugger PIN can gain access to the debugger running on localhost. This requires guessing a URL in the developer's application that triggers the debugger. The issue is fixed in version 1.116.0_1.

References

Community reviews

Loading reviews…