CVE-2025-26013 json
An issue in Loggrove v.1.0 allows a remote attacker to obtain sensitive information via the read.py component.
published last yr. modified 4mo ago also EUVD-2025-4483
- cvss
- 8.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
An issue in Loggrove v.1.0 allows a remote attacker to obtain sensitive information via the read.py component.
Is CVE-2025-26013 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- last yr.
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- gitee.com https://gitee.com/olajowon/loggrove/issues/IBJSXS referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
| CNA | 3.1 | 8.2 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N |
Classification
- Weakness
-
- CWE-540 Inclusion of Sensitive Information in Source Code
References
-
gitee.com
/olajowon/loggrove/issues/IBJSXS
exploit, issue-tracking, vendor-advisory
Sources
- CVE List CVE-2025-26013
- NVD CVE-2025-26013
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.