# CVE-2025-26013: Information disclosure in n/a

> A remote attacker can obtain sensitive information from the Loggrove logging library via the read.py component.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Feb 2025
- **Updated:** 21 Feb 2025
- **Also known as:** GHSA-27wp-chg4-ffw3

## What is CVE-2025-26013?

CVE-2025-26013 is a high-severity vulnerability in n/a, published on 21 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in Loggrove v.1.0 allows a remote attacker to obtain sensitive information via the read.py component.

Weakness: CWE-540 (Inclusion of Sensitive Information in Source Code)

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

It affects 1 product.


Products: Olajowon Loggrove.

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

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

## Is CVE-2025-26013 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-26014](https://insights.sbomify.com/CVE-2025-26014/): Code injection in n/a (critical 9.8)
- [CVE-2025-26047](https://insights.sbomify.com/CVE-2025-26047/): SQL injection in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26013 is a high-severity vulnerability in n/a, published on 21 Feb 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-26013 in the wild and no public exploit code.

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

## Sources

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

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