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

GHSA-rvjx-cfjh-5mc9 loggingredactor

GHSA-rvjx-cfjh-5mc9 is a CWE-704 vulnerability in loggingredactor. A fix is available for loggingredactor — see the affected versions and patch details below.

loggingredactor converts non-string types to string types in logs

Also known asCVE-2026-22041PYSEC-2026-1582
Published
Jan 7, 2026
Updated
Jul 7, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-rvjx-cfjh-5mc9.

EPSS Exploitation Probability

via FIRST.org ↗
0.3%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs19th percentile — riskier than 19% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected
🐍loggingredactor

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

Impact

Non-string types are converted into string types, leading to type errors in %d conversions.

Patches

The problem has been patched in version 0.0.6.

Workarounds

None without patching.

Resources

Issue report: https://github.com/armurox/loggingredactor/issues/7 Release: https://github.com/armurox/loggingredactor/releases/tag/0.0.6

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIloggingredactorall versions0.0.6pip install --upgrade 'loggingredactor==0.0.6'

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

    Update loggingredactor to 0.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rvjx-cfjh-5mc9 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-rvjx-cfjh-5mc9 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-rvjx-cfjh-5mc9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Non-string types are converted into string types, leading to type errors in %d conversions. ### Patches The problem has been patched in version 0.0.6. ### Workarounds None without patching. ### Resources Issue report: https://github.com/armurox/loggingredactor/issues/7 Release: https://github.com/armurox/loggingredactor/releases/tag/0.0.6
O3 Security · Impact-Aware SCA

Is GHSA-rvjx-cfjh-5mc9 in your dependencies?

O3 Security finds GHSA-rvjx-cfjh-5mc9 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-rvjx-cfjh-5mc9: loggingredactor | O3 Security