CVE-2026-86522

Log injection via an unescaped password reset identity in AshAuthentication

Published Sep 17, 2026 CVSS 4.0 · 6.3 Medium EPSS < 1% KEV · Not listed
Description
Improper Output Neutralization for Logs vulnerability in team-alembic AshAuthentication allows an unauthenticated attacker to forge application log entries by submitting a password reset identity containing newlines or control characters.

AshAuthentication.Strategy.Password.RequestPasswordReset.run/3 interpolates the identity argument, the email or username taken straight from the reset request, into its Logger.warning/1 heredocs without escaping, truncating or type-restricting it. The resource logged beside it is passed through inspect/1, which would have neutralized the value. A newline in the identity therefore ends the log record, and everything after it is written as a line of its own, so an attacker chooses the severity tag and the content of entries that appear to have come from the application.

This issue affects ash_authentication: from 4.2.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Analysis

AI-generated

Technical impact

The issue is an improper output neutralization for logs (CWE-117). AshAuthentication interpolates the password reset identity directly into a log warning, without escaping or truncation. A malicious user can include newline or control characters, causing the log to split into multiple entries and allowing the attacker to forge log messages with arbitrary severity tags and content. This can disguise malicious actions, mislead administrators, or clutter log entries, undermining the reliability of audit trails.

Affected Systems

The vulnerability impacts the AshAuthentication component from team‑alembic. Versions from 4.2.0 up to but not including 4.15.0, and from 5.0.0‑rc.0 up to but not including 5.0.0‑rc.14, are affected.

Risk and Exploitability

The CVSS base score of 6.3 indicates a medium impact. Because the flaw is exploitable through an unauthenticated password reset request, an attacker can achieve log tampering at will. The EPSS score is unavailable, and the vulnerability is not in the CISA KEV catalogue, so there is no data on recent exploit activity. The lack of procedural restrictions means the attack path is straightforward: submit a crafted identity during a reset request and observe forged logs. Vendors have released patches that prevent the failure to neutralize the identity; upgrading to a version >=4.15.0 or >=5.0.0‑rc.14 mitigates the risk.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade AshAuthentication to a fixed version (4.15.0 or later, or 5.0.0‑rc.14 or later).
  • If an upgrade cannot be performed immediately, sanitize the password reset identity input by stripping newline and control characters before it is logged.
  • Ensure that all log statements in the application use proper escaping or neutralization functions, such as passing values through an inspection or explicit filtering.

Generated by OpenCVE AI on September 17, 2026 at 22:54 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Description Improper Output Neutralization for Logs vulnerability in team-alembic AshAuthentication allows an unauthenticated attacker to forge application log entries by submitting a password reset identity containing newlines or control characters. AshAuthentication.Strategy.Password.RequestPasswordReset.run/3 interpolates the identity argument, the email or username taken straight from the reset request, into its Logger.warning/1 heredocs without escaping, truncating or type-restricting it. The resource logged beside it is passed through inspect/1, which would have neutralized the value. A newline in the identity therefore ends the log record, and everything after it is written as a line of its own, so an attacker chooses the severity tag and the content of entries that appear to have come from the application. This issue affects ash_authentication: from 4.2.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.
Title Log injection via an unescaped password reset identity in AshAuthentication
First Time appeared Team-alembic
Team-alembic ash Authentication
Weaknesses CWE-117
CPEs cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*
Vendors & Products Team-alembic
Team-alembic ash Authentication
References
Metrics cvssV4_0

{'score': 6.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N'}

Weaknesses
  • CWE-117

    Improper Output Neutralization for Logs

Sources

Status
PUBLISHED
Assigner
EEF
Published
Updated
Nov 20, 2026, 6:03 AM
Reserved
Sep 7, 2026, 10:30 PM
Status
Deferred
Published
Sep 17, 2026, 2:17 PM
Modified
Nov 20, 2026, 6:17 AM