# CVE-2025-26789: Information disclosure in AgentX

> Limited access controls allow li-admin users to access sensitive AgentX Manager information in Logpoint deployments.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** GHSA-q2gx-x2fm-c9fr

## What is CVE-2025-26789?

CVE-2025-26789 is a medium-severity vulnerability in Logpoint AgentX, published on 14 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in Logpoint AgentX before 1.5.0. A vulnerability caused by limited access controls allowed li-admin users to access sensitive information about AgentX Manager in a Logpoint deployment.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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


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

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

## Is CVE-2025-26789 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26789 is a medium-severity vulnerability in Logpoint AgentX, published on 14 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-26789 in the wild and no public exploit code.

Affected product: Logpoint AgentX. 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-26789/ (Markdown: https://insights.sbomify.com/CVE-2025-26789/index.md)
```

## Sources

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

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