# CVE-2026-107701: dot-access through 1.0.0 Prototype Pollution via set() path argument

> Attackers can pollute Object.prototype via crafted paths in dot-access, potentially altering authorization flags or crashing the process.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:L/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:** 14 Oct 2026
- **Also known as:** GHSA-mcgm-wx64-jv4w

## What is CVE-2026-107701?

CVE-2026-107701 is a high-severity 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 through 1.0.0 contains a prototype pollution vulnerability that allows attackers to modify Object.prototype by supplying a crafted dotted path to set(). Attackers controlling the path, such as through user-supplied field names, can use __proto__ segments to inject properties into all objects, altering authorization flags and option defaults or crashing the process.

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

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


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

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

## Is CVE-2026-107701 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107701 is a high-severity 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: There is no known exploitation of CVE-2026-107701 in the wild and no public exploit code.

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-107701/ (Markdown: https://insights.sbomify.com/CVE-2026-107701/index.md)
```

## Sources

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

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