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

This week

HIGH 8.2REMOTEDOWNGRADE

CVE-2025-26013 is a high-severity flaw (CVSS 8.2) affecting loggrove. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

High severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	8.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.4% (top 64%)
CISA exploited list	No
Weakness	CWE-540
Published	2025-02-21
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: olajowon

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-02-21 16:15 UTCPublished CVE record published
2026-06-17 09:01 UTCUpdated Record last modified

olajowon loggrove DOWNGRADE

Affected: 1.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 1.0

1. Check installed version

apt-cache policy loggrove || rpm -q loggrove || loggrove --version

2. No fixed release: DOWNGRADE to a release before 1.0 (Debian / Ubuntu)

apt-cache madison loggrove sudo apt install loggrove=<VERSION_BEFORE_1.0> sudo apt-mark hold loggrove

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list loggrove sudo dnf downgrade loggrove-<VERSION_BEFORE_1.0> sudo dnf versionlock add loggrove

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-26013?

loggrove: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-26013 being exploited?

CVE-2025-26013 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-26013 affect?

CVE-2025-26013 affects loggrove. Severity is high (CVSS 8.2). An issue in Loggrove v.1.0 allows a remote attacker to obtain sensitive information via the read.py component.

How urgent is CVE-2025-26013?

Priority 48/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-26047 MEDIUM 5.1 DOWNGRADE Loggrove v1.0 is vulnerable to SQL Injection in the read.py file.
CVE-2025-26014 CRITICAL 9.8 DOWNGRADE A Remote Code Execution (RCE) vulnerability in Loggrove v.1.0 allows a remote attacker to execute arbitrary co

References

← Back to latest CVEs