# CVE-2025-44643: Hardcoded credentials in n/a

> Hardcoded weak password in routing daemon allows attackers to gain unauthorized control and intercept traffic on Draytek access points.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 4 Aug 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-gc7r-mcv2-9fm9

## What is CVE-2025-44643?

CVE-2025-44643 is a high-severity vulnerability in n/a, published on 4 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Certain Draytek products are affected by Insecure Configuration. This affects AP903 v1.4.18 and AP912C v1.4.9 and AP918R v1.4.9. The setting of the password property in the ripd.conf configuration file sets a hardcoded weak password, posing a security risk. An attacker with network access could exploit this to gain unauthorized control over the routing daemon, potentially altering network routes or intercepting traffic.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2025-44643 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-44643 is a high-severity vulnerability in n/a, published on 4 Aug 2025. 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-2025-44643 exists.

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

## Sources

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

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