# CVE-2020-26941: Path traversal in n/a

> A local low-privileged user can overwrite arbitrary files via symlink during installation if Self-Defense is disabled, potentially leading to privilege escalation.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-3855-w94p-4hp9

## What is CVE-2020-26941?

CVE-2020-26941 is a medium-severity path traversal vulnerability in n/a, published on 21 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local (authenticated) low-privileged user can exploit a behavior in an ESET installer to achieve arbitrary file overwrite (deletion) of any file via a symlink, due to insecure permissions. The possibility of exploiting this vulnerability is limited and can only take place during the installation phase of ESET products. Furthermore, exploitation can only succeed when Self-Defense is disabled. Affected products are: ESET NOD32 Antivirus, ESET Internet Security, ESET Smart Security, ESET Smart Security Premium versions 13.2 and lower; ESET Endpoint Antivirus, ESET Endpoint Security, ESET NOD32 Antivirus Business Edition, ESET Smart Security Business Edition versions 7.3 and lower; ESET File Security for Microsoft Windows Server, ESET Mail Security for Microsoft Exchange Server, ESET Mail Security for IBM Domino, ESET Security for Kerio, ESET Security for Microsoft SharePoint Server versions 7.2 and lower.

Weakness: CWE-276 (Incorrect Default Permissions)

## Which versions are affected by CVE-2020-26941?

It affects 8 products.


Products: Eset Endpoint Antivirus, Eset Endpoint Security, Eset File Security, Eset Internet Security, Eset Mail Security, Eset Nod32 Antivirus, Eset Security, Eset Smart Security.

## How do I fix CVE-2020-26941?

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

## Is CVE-2020-26941 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-0353](https://insights.sbomify.com/CVE-2024-0353/): Local privilege escalation in Windows products (high 7.8)
- [CVE-2023-3160](https://insights.sbomify.com/CVE-2023-3160/): Local privilege escalation in security products for Windows (high 7.8)
- [CVE-2021-37852](https://insights.sbomify.com/CVE-2021-37852/): LPE in ESET products for Windows (high 7.8)
- [CVE-2023-5594](https://insights.sbomify.com/CVE-2023-5594/): Improper following of a certificate's chain of trust in ESET security products (high 7.5)
- [CVE-2021-37851](https://insights.sbomify.com/CVE-2021-37851/): Local Privilege Escalation in ESET product for Windows (high 7.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-26941 and fix it if it is affected.

What it is: CVE-2020-26941 is a medium-severity path traversal vulnerability in n/a, published on 21 Jan 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-26941 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-2020-26941/ (Markdown: https://insights.sbomify.com/CVE-2020-26941/index.md)
```

## Sources

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

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