# CVE-2026-107700: dot-access 0.0.3 through 1.0.0 Code Injection via get() Path Argument

> Remote attackers can execute arbitrary JavaScript and OS commands by supplying crafted paths to the get() function in the dot-access library.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-rhfh-63ph-3pch

## What is CVE-2026-107700?

CVE-2026-107700 is a critical code injection vulnerability in ntharim dot-access, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

dot-access 0.0.3 through 1.0.0 contains a code injection vulnerability that allows remote attackers to execute JavaScript by supplying crafted paths to get(). The path is concatenated into a new Function body in index.js, so attackers can reach constructor.constructor to load child_process and run operating system commands in the Node.js process.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-107700?


## How do I fix CVE-2026-107700?

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

## Is CVE-2026-107700 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107700 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107700 and fix it if it is affected.

What it is: CVE-2026-107700 is a critical code injection vulnerability in ntharim dot-access, published on 8 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107700 exists.

Affected product: ntharim dot-access. 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-2026-107700/ (Markdown: https://insights.sbomify.com/CVE-2026-107700/index.md)
```

## Sources

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

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