# CVE-2026-19893: D-Link DIR-842 vsftpd vsftpd.conf default permission

> Incorrect default permissions in vsftpd configuration on D-Link DIR-842 routers allow remote attackers to potentially read or modify data.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-6627-49xg-7jhr

## What is CVE-2026-19893?

CVE-2026-19893 is a low-severity vulnerability in D-Link DIR-842, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was identified in D-Link DIR-842 2.01.B04. This impacts an unknown function of the file /etc/vsftpd.conf of the component vsftpd. Such manipulation leads to incorrect default permissions. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is said to be difficult.

Weakness: CWE-276 (Incorrect Default Permissions), CWE-266 (Incorrect Privilege Assignment)

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


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

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

## Is CVE-2026-19893 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19893 is a low-severity vulnerability in D-Link DIR-842, published on 15 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19893 in the wild and no public exploit code.

Affected product: D-Link DIR-842. 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-19893/ (Markdown: https://insights.sbomify.com/CVE-2026-19893/index.md)
```

## Sources

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

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