docopt.cpp 0.6.2 LeafPattern::match integer overflow

Summaryinfo

A vulnerability marked as problematic has been reported in docopt.cpp 0.6.2. This affects the function LeafPattern::match. This manipulation causes integer overflow. The identification of this vulnerability is CVE-2025-67125. There is no exploit available.

Detailsinfo

A vulnerability was found in docopt.cpp 0.6.2. It has been declared as problematic. Affected by this vulnerability is the function LeafPattern::match. The manipulation with an unknown input leads to a integer overflow vulnerability. The CWE definition for the vulnerability is CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

A signed integer overflow in docopt.cpp v0.6.2 (LeafPattern::match in docopt_private.h) when merging occurrence counters (e.g., default LONG_MAX + first user "-v/--verbose") can cause counter wrap (negative/unbounded semantics) and lead to logic/policy bypass in applications that rely on occurrence-based limits, rate-gating, or safety toggles. In hardened builds (e.g., UBSan or -ftrapv), the overflow may also result in process abort (DoS).

It is possible to read the advisory at gist.github.com. This vulnerability is known as CVE-2025-67125 since 12/08/2025. The exploitation appears to be difficult. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/12/2026).

The vulnerability scanner Nessus provides a plugin with the ID 296423 (Linux Distros Unpatched Vulnerability : CVE-2025-67125), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (296423). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

• docopt.cpp

Version

• 0.6.2

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion