Pivotick up to 1.4.0 tree-layout/cycle-detection Math.max resource consumption

Summaryinfo

A vulnerability labeled as problematic has been found in Pivotick up to 1.4.0. This impacts the function Math.max of the component tree-layout/cycle-detection. Such manipulation leads to resource consumption. This vulnerability is documented as CVE-2026-66922. The attack can be executed remotely. There is not any exploit available.

Detailsinfo

A vulnerability was found in Pivotick up to 1.4.0. It has been rated as problematic. Affected by this issue is the function Math.max of the component tree-layout/cycle-detection. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is integrity, and availability. CVE summarizes:

Pivotick used plain JavaScript objects as lookup tables indexed by caller-controlled graph node identifiers in its tree-layout and cycle-detection components. Node identifiers matching properties inherited from Object.prototype, such as constructor, toString, or __proto__, were not handled as ordinary identifiers. These values could be interpreted as existing inherited properties, resolve to values of an unexpected type, or—in the case of __proto__ assignments—modify the prototype of an internal lookup object. An attacker who can supply graph data containing crafted node identifiers could consequently cause nodes or edges to be silently omitted, produce incorrect hierarchy levels, bypass or corrupt cycle-detection results, or trigger an exception that interrupts graph processing and rendering. This affects the integrity of graph visualisations and analytics and may cause a client-side denial-of-service condition. The affected code also failed to safely handle edges whose source node was absent from the supplied node set. Furthermore, calculating the maximum tree depth by spreading all level values into Math.max() could exceed the JavaScript function-argument limit when processing a sufficiently large graph, resulting in an exception and denial of service. The patch replaces identifier-keyed plain objects with Map instances, ignores invalid edges during tree construction, and calculates the maximum depth iteratively.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-66922 since 07/28/2026. The exploitation is known to be easy. The attack may be launched remotely. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1499.

Applying the patch 4e12922627029af77476c6f1ab8a14e98d5ef451 is able to eliminate this problem.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• Pivotick

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4.0

Website

• Product: https://github.com/Pivotick/Pivotick/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion