team-alembic ash_authentication up to 4.14.x/5.0.0-rc.13 Password Reset identity neutralization

Summaryinfo

A vulnerability, which was classified as critical, was found in team-alembic ash_authentication up to 4.14.x/5.0.0-rc.13. Affected is the function AshAuthentication.Strategy.Password.RequestPasswordReset.run of the component Password Reset. Such manipulation of the argument identity leads to neutralization. This vulnerability is traded as CVE-2026-86522. The attack may be launched remotely. There is no exploit available.

Detailsinfo

A vulnerability was found in team-alembic ash_authentication up to 4.14.x/5.0.0-rc.13. It has been rated as critical. Affected by this issue is the function AshAuthentication.Strategy.Password.RequestPasswordReset.run of the component Password Reset. The manipulation of the argument identity with an unknown input leads to a neutralization vulnerability. Using CWE to declare the problem leads to CWE-707. The product does not ensure or incorrectly ensures that structured messages or data are well-formed and that certain security properties are met before being read from an upstream component or sent to a downstream component. Impacted is integrity, and availability. CVE summarizes:

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.

The advisory is available at github.com. This vulnerability is handled as CVE-2026-86522 since 09/08/2026. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 09/17/2026).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Vendor

• team-alembic

Name

• ash_authentication

Version

• 4.0
• 4.1
• 4.2
• 4.3
• 4.4
• 4.5
• 4.6
• 4.7
• 4.8
• 4.9
• 4.10
• 4.11
• 4.12
• 4.13
• 4.14
• 5.0.0-rc.0
• 5.0.0-rc.1
• 5.0.0-rc.2
• 5.0.0-rc.3
• 5.0.0-rc.4
• 5.0.0-rc.5
• 5.0.0-rc.6
• 5.0.0-rc.7
• 5.0.0-rc.8
• 5.0.0-rc.9
• 5.0.0-rc.10
• 5.0.0-rc.11
• 5.0.0-rc.12
• 5.0.0-rc.13

Website

• Product: https://github.com/team-alembic/ash_authentication/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion