# CVE-2025-7706: Improper Access Control in TUBITAK BILGEM's Liderahenk

> Attackers can execute remote code via critical functions lacking authentication in Liderahenk server software.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Feb 2026
- **Updated:** 5 Jun 2026
- **Also known as:** GHSA-8jrm-jhc8-cchx

## What is CVE-2025-7706?

CVE-2025-7706 is a medium-severity missing authorization vulnerability in TUBITAK BILGEM Software Technologies Research Institute Liderahenk, published on 17 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Missing Authentication for Critical Function vulnerability in TUBITAK BILGEM Software Technologies Research Institute Liderahenk allows Remote Code Inclusion.

This issue affects Liderahenk: from 3.0.0 to 3.3.1 before 3.5.0.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-7706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7706 is a medium-severity missing authorization vulnerability in TUBITAK BILGEM Software Technologies Research Institute Liderahenk, published on 17 Feb 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-7706 in the wild and no public exploit code.

Affected product: TUBITAK BILGEM Software Technologies Research Institute Liderahenk. 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-7706/ (Markdown: https://insights.sbomify.com/CVE-2025-7706/index.md)
```

## Sources

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

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