# CVE-2025-41418: Memory corruption in HRX-1621/TE

> A buffer overflow in TB-eye network recorders allows attackers to cause a denial of service by sending specially crafted requests to the CGI process.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jun 2025
- **Updated:** 30 Jun 2025
- **Also known as:** GHSA-gh4r-42hj-jqg2

## What is CVE-2025-41418?

CVE-2025-41418 is a medium-severity memory corruption vulnerability in TB-eye Ltd. HRX-1621/TE, published on 27 Jun 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Overflow vulnerability exists in multiple versions of TB-eye network recorders and AHD recorders. The CGI process may be terminated abnormally by processing  a specially crafted request.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

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


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

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

## Is CVE-2025-41418 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-41418 is a medium-severity memory corruption vulnerability in TB-eye Ltd. HRX-1621/TE, published on 27 Jun 2025. 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-41418 in the wild and no public exploit code.

Affected product: TB-eye Ltd. HRX-1621/TE. 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-41418/ (Markdown: https://insights.sbomify.com/CVE-2025-41418/index.md)
```

## Sources

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

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