CVE-2026-22041VulnerabilityPublished 8 Jan 2026

CVE-2026-22041: armurox loggingredactor · Incorrect Type Conversion or Cast

Affects armurox loggingredactorSource CVE Database V5

Not known to be exploited · CVSS 2.0 Low : upgrade to 0.0.6 when convenient.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

2.0Low

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.0.6

CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Local
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Local: The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 8 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade armurox loggingredactor to 0.0.6.

Affected software

Product	Affected	Fixed in
armuroxloggingredactor	Affected <0.0.6	Fixed in 0.0.6
PyPIloggingredactor`pkg:pypi/loggingredactor`Other threats	Affected <0.0.6	Fixed in 0.0.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade the armurox loggingredactor library to version 0.0.6 or later to eliminate the vulnerability. Since no workarounds exist, patching is the only effective mitigation. Additionally, organizations should audit their codebases and dependency manifests to identify any usage of affected versions and ensure they are updated. Implementing robust testing around logging functionality can help detect failures caused by type conversion issues. Where feasible, developers should validate data types before passing them to loggingredactor functions to prevent unexpected type errors. Monitoring application logs for errors related to loggingredactor can provide early warning of exploitation attempts or failures. Finally, organizations should maintain an inventory of third-party libraries and subscribe to vulnerability feeds to promptly address similar issues in the future.

Description

Logging Redactor is a Python library designed to redact sensitive data in logs based on regex patterns and / or dictionary keys. Prior to version 0.0.6, non-string types are converted into string types, leading to type errors in %d conversions. The problem has been patched in version 0.0.6. No known workarounds are available.

Impact

For European organizations, the primary impact of CVE-2026-22041 is on the reliability and integrity of logging systems. Organizations that rely heavily on automated log redaction to comply with data protection regulations such as GDPR may experience failures in redacting sensitive information, potentially leading to incomplete or inconsistent logs. This could indirectly affect compliance audits or forensic investigations. Additionally, applications encountering type errors during logging might experience crashes or degraded performance, impacting availability. While the vulnerability does not directly compromise confidentiality or allow remote exploitation, the disruption of logging can hinder incident detection and response capabilities. Sectors with stringent logging requirements, such as finance, healthcare, and critical infrastructure, could face operational challenges if affected versions are in use. The low severity suggests limited direct risk, but the operational impact on logging integrity warrants timely remediation.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 8 Jan 2026, 15:20 UTC

WeaknessesCWE-704

Technical details

References

Community reviews

Related threats