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

> Attackers can inject commands via the SSID field to compromise the system and other devices on the Iridium Certus 700.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/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:** 27 May 2025
- **Also known as:** GHSA-9hpw-wrhw-6g76

## What is CVE-2025-41378?

CVE-2025-41378 is a medium-severity command injection 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

The SSID field is not parsed correctly and can be used to inject commands into the hostpad.conf file. This can be exploited by an attacker to extend his knowledge of the system and compromise other devices. The information is filtered by the logs function of the web panel.

Weakness: CWE-20 (Improper Input Validation)

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


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

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

## Is CVE-2025-41378 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41378 is a medium-severity command injection 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-41378 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-41378/ (Markdown: https://insights.sbomify.com/CVE-2025-41378/index.md)
```

## Sources

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

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