CVE-2026-63417: armurox loggingredactor · Sensitive Data in Logs
Affects armurox loggingredactorSource CVE Database V5
Not known to be exploited · CVSS 8.2 High : upgrade to 0.0.7 soon.
Data as of 3 Nov 2026, 18:43 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.2 |
|---|
- Patch
- Available – fixed in 0.0.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 3 Nov 2026.
What to do
Upgrade armurox loggingredactor to 0.0.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| armuroxloggingredactor | Affected
| Fixed in
|
Description
Logging Redactor is a Python library designed to redact sensitive data in logs based on regex patterns and / or dictionary keys. Prior to 0.0.7, personally identifiable information returned by custom object __str__ or __repr__ methods is not redacted when such non-primitive objects are logged, causing sensitive values to appear in logs that are expected to mask them. This issue is fixed in version 0.0.7.
References
- github.com/armurox/loggingredactor/security/advisories/GHSA-w7qv-268h-9h3f (opens in a new tab)
- github.com/armurox/loggingredactor/issues/12 (opens in a new tab)
- github.com/armurox/loggingredactor/pull/15 (opens in a new tab)
- github.com/armurox/loggingredactor/commit/361a528e56437b9c269e69f3863de4b3e568391b (opens in a new tab)
- github.com/armurox/loggingredactor/releases/tag/0.0.7 (opens in a new tab)