Skip to main content
VulnerabilityPublished

CVE-2026-63417: armurox loggingredactor · Sensitive Data in Logs

Affects armurox loggingredactorSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 0.0.7 soon.

Data as of 3 Nov 2026, 18:43 UTC

CVSS 4.0 base score
8.2High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
armuroxloggingredactorAffected
  • <0.0.7
Fixed in
  • 0.0.7

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

Community reviews

Loading reviews…