Skip to main content
VulnerabilityPublished

CVE-2026-119215: team-alembic ash_authentication · Insecure Direct Object Reference

Affects team-alembic ash_authenticationSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High : upgrade to 5.0.0-rc.16 soon.

Data as of 3 Nov 2026, 15:58 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (EEF)CVSS 4.07.6
Patch
Available – fixed in 5.0.0-rc.16, 4058be0f519c2e9b0d2266e90f9c7d8547d54574
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 3 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 3 Nov 2026.

What to do

Upgrade ash_authentication to 5.0.0-rc.16; ash_authentication to 4058be0f519c2e9b0d2266e90f9c7d8547d54574.

Affected software

ProductAffectedFixed in
team-alembicash_authenticationAffected
  • >=5.0.0-rc.0 <5.0.0-rc.16
Fixed in
  • 5.0.0-rc.16
ash_authenticationteam-alembic/ash_authenticationAffected
  • ≥ 6e7a880698614887527a87df206b4eb0c0fbd8c1, < 4058be0f519c2e9b0d2266e90f9c7d8547d54574
Fixed in
  • 4058be0f519c2e9b0d2266e90f9c7d8547d54574
Hexash_authenticationpkg:hex/ash_authenticationOther threatsAffected
  • >=5.0.0-rc.0 <5.0.0-rc.16
Fixed in
  • 5.0.0-rc.16

CPE configurations (1)

  • cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*

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

Description

Authorization Bypass Through User-Controlled Key vulnerability in team-alembic ash_authentication allows a user with an account to install a TOTP secret they control on another user's account, and then sign in as that user or hold their second factor. AshAuthentication.Strategy.Totp.ConfirmSetupChange verified a setup token but did not check that it was issued to the record being confirmed, so an attacker's own pending secret could be confirmed onto another user's record. The TOTP setup changes, ConfirmSetupChange, GeneratePendingSetupChange and GenerateSecretChange, also marked their changesets as AshAuthentication interactions, which the standard AshAuthenticationInteraction policy bypass lets through. A policy limiting setup and confirm_setup to the actor's own record therefore never ran when an application exposed those actions by record key, and a direct setup call on another user's record returned that user's pending secret and setup token. This issue affects ash_authentication: from 5.0.0-rc.0 before 5.0.0-rc.16.

References

Community reviews

Loading reviews…