Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

loguru logs sensitive informationGHSA-39ph-wr67-j4xq

MEDIUMFix: delgan/loguru@ea39375

GHSA-39ph-wr67-j4xq is a medium-severity (CVSS 4.3) CWE-532 vulnerability in loguru. 1 public exploit reference exists, so weaponization risk is real. A fix is available for loguru — see the affected versions and patch details below.

Also known asCVE-2022-0338PYSEC-2022-14
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Oct 12, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs54th percentile — riskier than 54% of all scored CVEsHighest risk
0.26%0.59%0.92%1.26%0.8%0.8%0.8%Jul 26Sep 26Oct 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

GHSA-39ph-wr67-j4xq by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg affected
🐍loguru

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Insertion of Sensitive Information into Log File in Conda loguru prior to 0.5.3.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIloguruall versions0.5.3pip install --upgrade 'loguru==0.5.3'

Affected Products

1 product · 1 configurations
Application
loguruloguru_project
< 0.5.3
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Insertion of Sensitive Information into Log File in Conda loguru prior t…

huntr.devNVDJan 2022

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for loguru, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update loguru to 0.5.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-39ph-wr67-j4xq is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

Insertion of Sensitive Information into Log File in Conda loguru prior to 0.5.3.
O3 Security · Impact-Aware SCA

Is GHSA-39ph-wr67-j4xq in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works
GHSA-39ph-wr67-j4xq: loguru — Fixed in 0.5.3