CVE-2026-80218 team-alembic CVE debrief

Who should care

Defenders responsible for ash_authentication deployments should assess exposure and prioritize verification and remediation. This includes reviewing affected versions, implementing compensating controls, and monitoring for suspicious activity. Security teams and vulnerability management teams should also prioritize this vulnerability due to its high severity and potential impact on system security.

Why it matters

CVE-2026-80218 is a high-severity Improper Authentication vulnerability in team-alembic AshAuthentication, allowing an attacker to sign in as a user of a different resource using a valid sign-in token. Defenders should prioritize verifying and upgrading affected versions, assessing exposure, and implementing compensating controls.

• Potential unauthorized access to sensitive resources
• Need to verify and upgrade affected ash_authentication versions
• Possible lateral movement within compromised systems

Technical summary

The AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 function improperly handles JWT sub claims, allowing an attacker to sign in as a user of a different resource. This issue arises from the function's failure to restore the binding between the token's subject and the resource it was issued for. The vulnerability affects ash_authentication versions from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14. Defenders should prioritize verifying and upgrading affected ash_authentication versions, assessing exposure, and implementing compensating controls.

Defensive priority

Defenders should prioritize verifying and upgrading affected ash_authentication versions, assessing exposure, and implementing compensating controls.

Recommended defensive actions

• Verify and upgrade affected ash_authentication versions
• Assess exposure and implement compensating controls
• Monitor for suspicious activity
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but limited information on affected versions and remediation is available. The AshAuthentication.Strategy.Password.SignInWithTokenPreparation.extract_primary_keys_from_subject/2 function improperly handles JWT sub claims. This issue affects ash_authentication: from 3.10.5 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.