dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-15598

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A weakness has been identified in antv layout 2.0.0. This impacts the function setNestedValue in the library lib/util/object.js. Executing a manipulation of the argument path can lead to improperly controlled modification of object prototype attributes. The attack can be launched remotely. The project was informed of the problem early through an issue report but has not responded yet.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A prototype pollution vulnerability in antv layout 2.0.0 allows attackers to modify object prototype attributes by manipulating the path argument in the setNestedValue function in lib/util/object.js, potentially leading to code execution or denial of service.

MitigationImplement strict input validation on the path argument to block access to prototype properties (__proto__, constructor.prototype) and ensure path traversal cannot reach object prototypes.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if antv layout package is installed
    Run 'npm list antv-layout' or check package.json for antv-layout dependency
    Affected if The package is not installed or the dependency is missing entirely, then not affected. If installed, proceed to next check.
  2. Check installed version of antv-layout
    Run 'npm list antv-layout' or inspect the version in node_modules/antv-layout/package.json
    Affected if Version is exactly 2.0.0, then affected. Versions other than 2.0.0 or versions above 2.0.0 are likely not affected.
  3. Locate the vulnerable setNestedValue function
    Inspect the file lib/util/object.js within the antv-layout package installation directory (typically node_modules/antv-layout/lib/util/object.js)
    Affected if The file exists and contains a setNestedValue function, proceed to next check. If the file does not exist, likely not affected or different version.
  4. Verify code paths that call setNestedValue with user input
    Search project codebase for calls to setNestedValue or the parent layout functions that accept a path parameter, especially where that path originates from external input (request parameters, user data, API input)
    Affected if Code passes untrusted or unsanitized path arguments to setNestedValue or related layout APIs, then likely vulnerable to prototype pollution. If all path inputs are strictly validated or hardcoded, likely not exploitable.

The environment is affected only if antv-layout version 2.0.0 is installed AND code uses setNestedValue with unvalidated user-controlled path arguments that can reach __proto__ or constructor.prototype.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation on the path argument to block access to prototype properties (__proto__, constructor.prototype) and ensure path traversal cannot reach object prototypes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15598 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15598 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data