---
id: "CVE-2026-63417"
kind: "vulnerability"
aliases: ["CVE-2026-63417"]
title: "Logging Redactor: custom __str__ and __repr__ output leaks personal data into logs"
severity: "high"
cvss: 8.2
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["logging", "package", "pii", "python"]
not_affected_if: ["library-not-used", "no-custom-repr-with-pii"]
published_at: "2026-11-03T19:18:09+00:00"
first_seen_at: "2026-11-03T19:44:53+00:00"
updated_at: "2026-11-03T19:45:25+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-63417", "first_seen_at": "2026-11-03T19:44:53+00:00"}]
---

# Logging Redactor: custom __str__ and __repr__ output leaks personal data into logs

Logging Redactor is a Python library meant to mask sensitive data in logs. Before version 0.0.7, personal data returned by custom __str__ or __repr__ methods on objects was not redacted when those objects were logged, so the values appear in plain text in log files.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version with `pip show logging-redactor` (package name as listed in the sources; confirm the exact name in your environment).
- Search your dependency lock file for the package and look for a version below `0.0.7`.
- Look for code that logs objects with custom __str__ or __repr__ methods that include personal data.

## Fix

- Upgrade the Logging Redactor Python package to `0.0.7` or later.

## Timeline

- 2026-11-03T19:44:53+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-63417

## Documents

- [advisory] Vendor advisory: github.com https://github.com/armurox/loggingredactor/security/advisories/GHSA-w7qv-268h-9h3f
- [fix] Patch: github.com https://github.com/armurox/loggingredactor/commit/361a528e56437b9c269e69f3863de4b3e568391b
- [fix] Release notes: github.com https://github.com/armurox/loggingredactor/releases/tag/0.0.7

## From the sources

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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_