CVE-2026-66922
MediumCVSS 5.1Exploitation Probability (EPSS)
Low risk21th percentile - higher than 21% of all known CVEs
Summary
Pivotick used plain JavaScript objects as lookup tables indexed by caller-controlled node identifiers. Identifiers matching inherited properties from Object.prototype (e.g., constructor, __proto__) could be misinterpreted, leading to omitted nodes, incorrect hierarchies, bypassed cycle detection, or exceptions causing denial of service.
Risk Assessment
An attacker could compromise the integrity of graph visualizations and analytics, and cause client-side denial of service.
Recommendation
Update Pivotick to a version containing the fix, which replaces objects with Map instances and ignores invalid edges.
Other vulnerabilities in Pivotick
See all- CVE-2026-67174Critical
Pivotick contains a DOM-based XSS vulnerability in UI element resolution and icon-rendering utilities. The tryResolveHTMLElement function treats any resolved string as HTML markup, and createIcon inserts SVG icons without sanitization. An unauthenticated attacker can provide a crafted graph, property value, or SVG icon, leading to JavaScript execution in the victim's browser.
- CVE-2026-67173Medium
Pivotick did not validate the URI scheme of node imagePath values, allowing an attacker to set a malicious URI. When a victim renders the graph, the browser could initiate an unintended request or invoke scheme-specific handling.
- CVE-2026-66921Medium
Pivotick's Markdown node-reference renderer fails to HTML-escape the attacker-controlled nodeName value, allowing injection of malicious HTML attributes or elements. This can lead to arbitrary JavaScript execution in the victim's browser.
- CVE-2026-66920High
Pivotick has an uncontrolled-recursion vulnerability when processing graph and node data. Recursive graph traversals and JSON rendering can exhaust the JavaScript call stack with specially crafted data, causing page or browser crashes.
- CVE-2026-66919Medium
Pivotick contains a cross-site scripting vulnerability in the inspect and edit node modals. Node labels and descriptions from graph data are interpolated directly into HTML, allowing an attacker to inject malicious JavaScript.
- CVE-2026-66918High
Pivotick fails to sanitize attacker-controlled SVG markup from the style.svgIcon property before inserting it into the document. The vulnerable code assigns SVG markup to innerHTML, allowing execution of event handlers like <image> with onerror. An attacker can execute arbitrary JavaScript in the application context.
- CVE-2026-66825Medium
Pivotick contains an XSS vulnerability in the sidebar property-list component. Link-like property values (url, uri, href, link, website, homepage) were rendered as hyperlinks without URL scheme validation. An attacker can supply a malicious value using the javascript: scheme, including whitespace or control characters. Clicking the link can execute JavaScript in the application context. The vulnerability was fixed by normalizing values and blocking unsafe schemes.
Original NVD description (English source)
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.