# CVE-2025-57347: Code injection in n/a

> Prototype pollution in dagre-d3-es allows attackers to inject malicious properties, potentially leading to arbitrary code execution or denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-cc8p-78qf-8p7q

## What is CVE-2025-57347?

CVE-2025-57347 is a critical code injection vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in the 'dagre-d3-es' Node.js package version 7.0.9, specifically within the 'bk' module's addConflict function, which fails to properly sanitize user-supplied input during property assignment operations. This flaw allows attackers to exploit prototype pollution vulnerabilities by injecting malicious input values (e.g., "__proto__"), enabling unauthorized modification of the JavaScript Object prototype chain. Successful exploitation could lead to denial of service conditions, unexpected application behavior, or potential execution of arbitrary code in contexts where polluted properties are later accessed or executed. The issue affects versions prior to 7.0.11 and remains unpatched at the time of disclosure.

Weakness: CWE-1321 (Improperly Controlled Modification of Object Prototype Attributes)

## Which versions are affected by CVE-2025-57347?

It affects 1 product.


Products: Tbo47 Dagre-D3-Es.

## How do I fix CVE-2025-57347?

No fix has been published for CVE-2025-57347 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-57347 being exploited?

There is no known exploitation of CVE-2025-57347 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-57347 and fix it if it is affected.

What it is: CVE-2025-57347 is a critical code injection vulnerability in n/a, published on 24 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-57347 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-57347/ (Markdown: https://insights.sbomify.com/CVE-2025-57347/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-57347
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-57347
- OSV: https://osv.dev/vulnerability/CVE-2025-57347

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-57347/
Summaries are generated and may contain mistakes; the official description above is the record.