# CVE-2025-41380: Injection vulnerability in Iridium Certus 700

> A local attacker can retrieve SSH hash strings from the Iridium Certus 700 satellite modem due to embedded credentials.

- **Severity:** Medium 6.1 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:H/SA: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:** 23 May 2025
- **Updated:** 23 May 2025
- **Also known as:** GHSA-4wjv-q2ww-cm43

## What is CVE-2025-41380?

CVE-2025-41380 is a medium-severity vulnerability in Intellian Technologies Iridium Certus 700, published on 23 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Iridium Certus 700 version 1.0.1 has an embedded credentials vulnerability in the code. This vulnerability allows a local user to retrieve the SSH hash string.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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


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

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

## Is CVE-2025-41380 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41380 is a medium-severity vulnerability in Intellian Technologies Iridium Certus 700, published on 23 May 2025. 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-2025-41380 in the wild and no public exploit code.

Affected product: Intellian Technologies Iridium Certus 700. 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-41380/ (Markdown: https://insights.sbomify.com/CVE-2025-41380/index.md)
```

## Sources

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

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