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

> Remote attackers can derive administrative credentials from the MAC address due to deterministic generation, enabling full device access.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 19 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-r7vj-ffgg-6jj4

## What is CVE-2025-67114?

CVE-2025-67114 is a critical vulnerability in n/a, published on 19 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use of a deterministic credential generation algorithm in /ftl/bin/calc_f2 in Small Cell Sercomm SCE4255W (FreedomFi Englewood) firmware before DG3934v3@2308041842 allows remote attackers to derive valid administrative/root credentials from the device's MAC address, enabling authentication bypass and full device access.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2025-67114 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67114 is a critical vulnerability in n/a, published on 19 Mar 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-2025-67114 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-2025-67114/ (Markdown: https://insights.sbomify.com/CVE-2025-67114/index.md)
```

## Sources

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

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