CVE-2026-76949

{"dataType": "CVE_RECORD", "dataVersion": "5.2", "cveMetadata": {"cveId": "CVE-2026-76949", "assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "state": "PUBLISHED", "assignerShortName": "EEF", "dateReserved": "2026-09-17T05:30:01.744Z", "datePublished": "2026-09-17T21:57:50.146Z", "dateUpdated": "2026-09-18T14:31:41.806Z"}, "containers": {"cna": {"affected": [{"collectionURL": "https://repo.hex.pm", "cpes": ["cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*"], "defaultStatus": "unaffected", "modules": ["'Elixir.AshAuthentication.Plug.Helpers'"], "packageName": "ash_authentication", "packageURL": "pkg:hex/ash_authentication", "product": "ash_authentication", "programFiles": ["lib/ash_authentication/plug/helpers.ex"], "programRoutines": [{"name": "'Elixir.AshAuthentication.Plug.Helpers':sign_in_using_remember_me/3"}, {"name": "'Elixir.AshAuthentication.Plug.Helpers':store_in_session/2"}], "repo": "https://github.com/team-alembic/ash_authentication", "vendor": "team-alembic", "versions": [{"lessThan": "4.15.0", "status": "affected", "version": "4.10.0", "versionType": "semver"}, {"lessThan": "5.0.0-rc.14", "status": "affected", "version": "5.0.0-rc.0", "versionType": "semver"}]}, {"collectionURL": "https://github.com", "cpes": ["cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*"], "defaultStatus": "unaffected", "modules": ["'Elixir.AshAuthentication.Plug.Helpers'"], "packageName": "team-alembic/ash_authentication", "packageURL": "pkg:github/team-alembic/ash_authentication", "product": "ash_authentication", "programFiles": ["lib/ash_authentication/plug/helpers.ex"], "programRoutines": [{"name": "'Elixir.AshAuthentication.Plug.Helpers':sign_in_using_remember_me/3"}, {"name": "'Elixir.AshAuthentication.Plug.Helpers':store_in_session/2"}], "repo": "https://github.com/team-alembic/ash_authentication", "vendor": "team-alembic", "versions": [{"changes": [{"at": "b9568a53b438247238b1c5a4f49c8d84650f4bba", "status": "unaffected"}, {"at": "9a34136b844abe179da1075067cf2835c64dcc12", "status": "unaffected"}], "lessThan": "*", "status": "affected", "version": "3d3de314692558d06ec13945f857f00514e95a8c", "versionType": "git"}]}], "configurations": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "<p>The application must enable the <code>remember_me</code> strategy and run its per-request plug in the browser pipeline, with <code>require_token_presence_for_authentication?</code> at its default of <code>false</code>. Enabling that setting makes the guard read the key the session actually holds, which closes the issue.</p>\n<p>The attacker also needs a position from which to set a cookie in the victim's browser, such as cookie tossing from a sibling subdomain, an HTTP host without HSTS, or a shared or kiosk browser.</p>"}, {"base64": false, "type": "text/markdown", "value": "The application must enable the `remember_me` strategy and run its per-request plug in the browser pipeline, with `require_token_presence_for_authentication?` at its default of `false`. Enabling that setting makes the guard read the key the session actually holds, which closes the issue.\n\nThe attacker also needs a position from which to set a cookie in the victim's browser, such as cookie tossing from a sibling subdomain, an HTTP host without HSTS, or a shared or kiosk browser."}], "value": "The application must enable the remember_me strategy and run its per-request plug in the browser pipeline, with require_token_presence_for_authentication? at its default of false. Enabling that setting makes the guard read the key the session actually holds, which closes the issue.\n\nThe attacker also needs a position from which to set a cookie in the victim's browser, such as cookie tossing from a sibling subdomain, an HTTP host without HSTS, or a shared or kiosk browser."}], "cpeApplicability": [{"nodes": [{"cpeMatch": [{"criteria": "cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*", "versionEndExcluding": "4.15.0", "versionStartIncluding": "4.10.0", "vulnerable": true}, {"criteria": "cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*", "versionEndExcluding": "5.0.0-rc.14", "versionStartIncluding": "5.0.0-rc.0", "vulnerable": true}], "negate": false, "operator": "OR"}], "operator": "AND"}], "credits": [{"lang": "en", "type": "reporter", "value": "Peter Ullrich"}, {"lang": "en", "type": "remediation developer", "value": "James Harton"}, {"lang": "en", "type": "coordinator", "value": "Jonatan M\u00e4nnchen / EEF"}], "dateAssigned": "2026-09-17T14:23:56.000Z", "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "<p>Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.</p>\n<p><code>AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3</code> skips re-authenticating an already-signed-in visitor by checking the session for <code>\"&lt;subject_name&gt;_token\"</code>, but <code>store_in_session/2</code> writes that key only when <code>require_token_presence_for_authentication?</code> is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in <code>authenticate_resource_from_session/4</code> selects the key correctly, so the guard and the reader disagree about which key holds the session.</p>\n<p>This issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.</p>"}, {"base64": false, "type": "text/markdown", "value": "Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.\n\n`AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3` skips re-authenticating an already-signed-in visitor by checking the session for `\"<subject_name>_token\"`, but `store_in_session/2` writes that key only when `require_token_presence_for_authentication?` is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in `authenticate_resource_from_session/4` selects the key correctly, so the guard and the reader disagree about which key holds the session.\n\nThis issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14."}], "value": "Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.\n\nAshAuthentication.Plug.Helpers.sign_in_using_remember_me/3 skips re-authenticating an already-signed-in visitor by checking the session for \"<subject_name>_token\", but store_in_session/2 writes that key only when require_token_presence_for_authentication? is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in authenticate_resource_from_session/4 selects the key correctly, so the guard and the reader disagree about which key holds the session.\n\nThis issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14."}], "impacts": [{"capecId": "CAPEC-21", "descriptions": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "<p>An attacker who can set a remember-me cookie in a victim's browser silently replaces the victim's authenticated session with one for the attacker's own account, so data the victim subsequently enters is written to records the attacker controls. The victim is given no indication their identity changed.</p>"}, {"base64": false, "type": "text/markdown", "value": "An attacker who can set a remember-me cookie in a victim's browser silently replaces the victim's authenticated session with one for the attacker's own account, so data the victim subsequently enters is written to records the attacker controls. The victim is given no indication their identity changed."}], "value": "An attacker who can set a remember-me cookie in a victim's browser silently replaces the victim's authenticated session with one for the attacker's own account, so data the victim subsequently enters is written to records the attacker controls. The victim is given no indication their identity changed."}]}], "metrics": [{"cvssV4_0": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "attackVector": "NETWORK", "baseScore": 9.1, "baseSeverity": "CRITICAL", "privilegesRequired": "NONE", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "version": "4.0", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "format": "CVSS", "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "problemTypes": [{"descriptions": [{"cweId": "CWE-290", "description": "CWE-290 Authentication Bypass by Spoofing", "lang": "en", "type": "CWE"}]}], "providerMetadata": {"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "shortName": "EEF", "dateUpdated": "2026-09-17T21:57:50.146Z"}, "references": [{"name": "GitHub Advisory", "tags": ["related", "vendor-advisory"], "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-hh34-374j-pfr5"}, {"name": "EEF CNA record for CVE-2026-76949", "tags": ["related"], "url": "https://cna.erlef.org/cves/CVE-2026-76949.html"}, {"name": "OSV record EEF-CVE-2026-76949", "tags": ["related"], "url": "https://osv.dev/vulnerability/EEF-CVE-2026-76949"}, {"name": "Introducing commit 3d3de31 in team-alembic/ash_authentication", "tags": ["related"], "url": "https://github.com/team-alembic/ash_authentication/commit/3d3de314692558d06ec13945f857f00514e95a8c"}, {"name": "Fix commit b9568a5 in team-alembic/ash_authentication", "tags": ["patch"], "url": "https://github.com/team-alembic/ash_authentication/commit/b9568a53b438247238b1c5a4f49c8d84650f4bba"}, {"name": "Fix commit 9a34136 in team-alembic/ash_authentication", "tags": ["patch"], "url": "https://github.com/team-alembic/ash_authentication/commit/9a34136b844abe179da1075067cf2835c64dcc12"}], "source": {"discovery": "EXTERNAL"}, "title": "Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement", "workarounds": [{"lang": "en", "supportingMedia": [{"base64": false, "type": "text/html", "value": "<p>Set <code>require_token_presence_for_authentication? true</code> on the authenticated resource's token configuration. <code>store_in_session/2</code> then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource.</p>\n<p>Otherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely.</p>"}, {"base64": false, "type": "text/markdown", "value": "Set `require_token_presence_for_authentication? true` on the authenticated resource's token configuration. `store_in_session/2` then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource.\n\nOtherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely."}], "value": "Set require_token_presence_for_authentication? true on the authenticated resource's token configuration. store_in_session/2 then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource.\n\nOtherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely."}]}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-76949", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-09-18T14:24:28.652087Z"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-09-18T14:31:41.806Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2026-76949", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "yes"}, {"Technical Impact": "total"}], "version": "2.0.3", "timestamp": "2026-09-18T14:24:28.652087Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2026-09-18T14:29:29.773Z"}}], "cna": {"title": "Remember-me sign-in guard reads a session key that is never written in ash_authentication, allowing session replacement", "source": {"discovery": "EXTERNAL"}, "credits": [{"lang": "en", "type": "reporter", "value": "Peter Ullrich"}, {"lang": "en", "type": "remediation developer", "value": "James Harton"}, {"lang": "en", "type": "coordinator", "value": "Jonatan M\u00e4nnchen / EEF"}], "impacts": [{"capecId": "CAPEC-21", "descriptions": [{"lang": "en", "value": "An attacker who can set a remember-me cookie in a victim's browser silently replaces the victim's authenticated session with one for the attacker's own account, so data the victim subsequently enters is written to records the attacker controls. The victim is given no indication their identity changed.", "supportingMedia": [{"type": "text/html", "value": "<p>An attacker who can set a remember-me cookie in a victim's browser silently replaces the victim's authenticated session with one for the attacker's own account, so data the victim subsequently enters is written to records the attacker controls. The victim is given no indication their identity changed.</p>", "base64": false}, {"type": "text/markdown", "value": "An attacker who can set a remember-me cookie in a victim's browser silently replaces the victim's authenticated session with one for the attacker's own account, so data the victim subsequently enters is written to records the attacker controls. The victim is given no indication their identity changed.", "base64": false}]}]}], "metrics": [{"format": "CVSS", "cvssV4_0": {"Safety": "NOT_DEFINED", "version": "4.0", "Recovery": "NOT_DEFINED", "baseScore": 9.1, "Automatable": "NOT_DEFINED", "attackVector": "NETWORK", "baseSeverity": "CRITICAL", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N", "providerUrgency": "NOT_DEFINED", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "NONE", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "HIGH", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "scenarios": [{"lang": "en", "value": "GENERAL"}]}], "affected": [{"cpes": ["cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*"], "repo": "https://github.com/team-alembic/ash_authentication", "vendor": "team-alembic", "modules": ["'Elixir.AshAuthentication.Plug.Helpers'"], "product": "ash_authentication", "versions": [{"status": "affected", "version": "4.10.0", "lessThan": "4.15.0", "versionType": "semver"}, {"status": "affected", "version": "5.0.0-rc.0", "lessThan": "5.0.0-rc.14", "versionType": "semver"}], "packageURL": "pkg:hex/ash_authentication", "packageName": "ash_authentication", "programFiles": ["lib/ash_authentication/plug/helpers.ex"], "collectionURL": "https://repo.hex.pm", "defaultStatus": "unaffected", "programRoutines": [{"name": "'Elixir.AshAuthentication.Plug.Helpers':sign_in_using_remember_me/3"}, {"name": "'Elixir.AshAuthentication.Plug.Helpers':store_in_session/2"}]}, {"cpes": ["cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*"], "repo": "https://github.com/team-alembic/ash_authentication", "vendor": "team-alembic", "modules": ["'Elixir.AshAuthentication.Plug.Helpers'"], "product": "ash_authentication", "versions": [{"status": "affected", "changes": [{"at": "b9568a53b438247238b1c5a4f49c8d84650f4bba", "status": "unaffected"}, {"at": "9a34136b844abe179da1075067cf2835c64dcc12", "status": "unaffected"}], "version": "3d3de314692558d06ec13945f857f00514e95a8c", "lessThan": "*", "versionType": "git"}], "packageURL": "pkg:github/team-alembic/ash_authentication", "packageName": "team-alembic/ash_authentication", "programFiles": ["lib/ash_authentication/plug/helpers.ex"], "collectionURL": "https://github.com", "defaultStatus": "unaffected", "programRoutines": [{"name": "'Elixir.AshAuthentication.Plug.Helpers':sign_in_using_remember_me/3"}, {"name": "'Elixir.AshAuthentication.Plug.Helpers':store_in_session/2"}]}], "references": [{"url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-hh34-374j-pfr5", "name": "GitHub Advisory", "tags": ["related", "vendor-advisory"]}, {"url": "https://cna.erlef.org/cves/CVE-2026-76949.html", "name": "EEF CNA record for CVE-2026-76949", "tags": ["related"]}, {"url": "https://osv.dev/vulnerability/EEF-CVE-2026-76949", "name": "OSV record EEF-CVE-2026-76949", "tags": ["related"]}, {"url": "https://github.com/team-alembic/ash_authentication/commit/3d3de314692558d06ec13945f857f00514e95a8c", "name": "Introducing commit 3d3de31 in team-alembic/ash_authentication", "tags": ["related"]}, {"url": "https://github.com/team-alembic/ash_authentication/commit/b9568a53b438247238b1c5a4f49c8d84650f4bba", "name": "Fix commit b9568a5 in team-alembic/ash_authentication", "tags": ["patch"]}, {"url": "https://github.com/team-alembic/ash_authentication/commit/9a34136b844abe179da1075067cf2835c64dcc12", "name": "Fix commit 9a34136 in team-alembic/ash_authentication", "tags": ["patch"]}], "workarounds": [{"lang": "en", "value": "Set require_token_presence_for_authentication? true on the authenticated resource's token configuration. store_in_session/2 then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource.\n\nOtherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely.", "supportingMedia": [{"type": "text/html", "value": "<p>Set <code>require_token_presence_for_authentication? true</code> on the authenticated resource's token configuration. <code>store_in_session/2</code> then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource.</p>\n<p>Otherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely.</p>", "base64": false}, {"type": "text/markdown", "value": "Set `require_token_presence_for_authentication? true` on the authenticated resource's token configuration. `store_in_session/2` then writes the key the guard reads, so the already-signed-in branch fires and the remember-me sign-in no longer runs against a live session. Note this changes session storage semantics for the whole application and requires a token resource.\n\nOtherwise remove the remember-me plug from the browser pipeline, which disables remember-me auto-login entirely.", "base64": false}]}], "dateAssigned": "2026-09-17T14:23:56.000Z", "descriptions": [{"lang": "en", "value": "Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.\n\nAshAuthentication.Plug.Helpers.sign_in_using_remember_me/3 skips re-authenticating an already-signed-in visitor by checking the session for \"<subject_name>_token\", but store_in_session/2 writes that key only when require_token_presence_for_authentication? is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in authenticate_resource_from_session/4 selects the key correctly, so the guard and the reader disagree about which key holds the session.\n\nThis issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.", "supportingMedia": [{"type": "text/html", "value": "<p>Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.</p>\n<p><code>AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3</code> skips re-authenticating an already-signed-in visitor by checking the session for <code>\"&lt;subject_name&gt;_token\"</code>, but <code>store_in_session/2</code> writes that key only when <code>require_token_presence_for_authentication?</code> is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in <code>authenticate_resource_from_session/4</code> selects the key correctly, so the guard and the reader disagree about which key holds the session.</p>\n<p>This issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.</p>", "base64": false}, {"type": "text/markdown", "value": "Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.\n\n`AshAuthentication.Plug.Helpers.sign_in_using_remember_me/3` skips re-authenticating an already-signed-in visitor by checking the session for `\"<subject_name>_token\"`, but `store_in_session/2` writes that key only when `require_token_presence_for_authentication?` is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in `authenticate_resource_from_session/4` selects the key correctly, so the guard and the reader disagree about which key holds the session.\n\nThis issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14.", "base64": false}]}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-290", "description": "CWE-290 Authentication Bypass by Spoofing"}]}], "configurations": [{"lang": "en", "value": "The application must enable the remember_me strategy and run its per-request plug in the browser pipeline, with require_token_presence_for_authentication? at its default of false. Enabling that setting makes the guard read the key the session actually holds, which closes the issue.\n\nThe attacker also needs a position from which to set a cookie in the victim's browser, such as cookie tossing from a sibling subdomain, an HTTP host without HSTS, or a shared or kiosk browser.", "supportingMedia": [{"type": "text/html", "value": "<p>The application must enable the <code>remember_me</code> strategy and run its per-request plug in the browser pipeline, with <code>require_token_presence_for_authentication?</code> at its default of <code>false</code>. Enabling that setting makes the guard read the key the session actually holds, which closes the issue.</p>\n<p>The attacker also needs a position from which to set a cookie in the victim's browser, such as cookie tossing from a sibling subdomain, an HTTP host without HSTS, or a shared or kiosk browser.</p>", "base64": false}, {"type": "text/markdown", "value": "The application must enable the `remember_me` strategy and run its per-request plug in the browser pipeline, with `require_token_presence_for_authentication?` at its default of `false`. Enabling that setting makes the guard read the key the session actually holds, which closes the issue.\n\nThe attacker also needs a position from which to set a cookie in the victim's browser, such as cookie tossing from a sibling subdomain, an HTTP host without HSTS, or a shared or kiosk browser.", "base64": false}]}], "cpeApplicability": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "4.15.0", "versionStartIncluding": "4.10.0"}, {"criteria": "cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*", "vulnerable": true, "versionEndExcluding": "5.0.0-rc.14", "versionStartIncluding": "5.0.0-rc.0"}], "operator": "OR"}], "operator": "AND"}], "providerMetadata": {"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "shortName": "EEF", "dateUpdated": "2026-09-17T21:57:50.146Z"}}}, "cveMetadata": {"cveId": "CVE-2026-76949", "state": "PUBLISHED", "dateUpdated": "2026-09-18T14:31:41.806Z", "dateReserved": "2026-09-17T05:30:01.744Z", "assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "datePublished": "2026-09-17T21:57:50.146Z", "assignerShortName": "EEF"}, "dataVersion": "5.2"}

{"affected": [{"affectedData": [{"collectionURL": "https://repo.hex.pm", "cpes": ["cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*"], "defaultStatus": "unaffected", "modules": ["'Elixir.AshAuthentication.Plug.Helpers'"], "packageName": "ash_authentication", "packageURL": "pkg:hex/ash_authentication", "product": "ash_authentication", "programFiles": ["lib/ash_authentication/plug/helpers.ex"], "programRoutines": [{"name": "'Elixir.AshAuthentication.Plug.Helpers':sign_in_using_remember_me/3"}, {"name": "'Elixir.AshAuthentication.Plug.Helpers':store_in_session/2"}], "repo": "https://github.com/team-alembic/ash_authentication", "vendor": "team-alembic", "versions": [{"lessThan": "4.15.0", "status": "affected", "version": "4.10.0", "versionType": "semver"}, {"lessThan": "5.0.0-rc.14", "status": "affected", "version": "5.0.0-rc.0", "versionType": "semver"}]}, {"collectionURL": "https://github.com", "cpes": ["cpe:2.3:a:team-alembic:ash_authentication:*:*:*:*:*:*:*:*"], "defaultStatus": "unaffected", "modules": ["'Elixir.AshAuthentication.Plug.Helpers'"], "packageName": "team-alembic/ash_authentication", "packageURL": "pkg:github/team-alembic/ash_authentication", "product": "ash_authentication", "programFiles": ["lib/ash_authentication/plug/helpers.ex"], "programRoutines": [{"name": "'Elixir.AshAuthentication.Plug.Helpers':sign_in_using_remember_me/3"}, {"name": "'Elixir.AshAuthentication.Plug.Helpers':store_in_session/2"}], "repo": "https://github.com/team-alembic/ash_authentication", "vendor": "team-alembic", "versions": [{"changes": [{"at": "b9568a53b438247238b1c5a4f49c8d84650f4bba", "status": "unaffected"}, {"at": "9a34136b844abe179da1075067cf2835c64dcc12", "status": "unaffected"}], "lessThan": "*", "status": "affected", "version": "3d3de314692558d06ec13945f857f00514e95a8c", "versionType": "git"}]}], "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "Authentication Bypass by Spoofing vulnerability in team-alembic ash_authentication allows an attacker who can plant a remember-me cookie in a victim's browser to replace that victim's authenticated session with one for the attacker's own account.\n\nAshAuthentication.Plug.Helpers.sign_in_using_remember_me/3 skips re-authenticating an already-signed-in visitor by checking the session for \"<subject_name>_token\", but store_in_session/2 writes that key only when require_token_presence_for_authentication? is enabled and otherwise writes the bare subject name. At the default setting the guard therefore reads a key that is never written, its already-signed-in branch is unreachable, and the remember-me sign-in runs on every request through the per-request browser pipeline plug. A planted remember-me cookie is consequently honoured even for a visitor holding a live authenticated session, so whatever the victim enters afterwards lands in data the attacker controls. The read path in authenticate_resource_from_session/4 selects the key correctly, so the guard and the reader disagree about which key holds the session.\n\nThis issue affects ash_authentication: from 4.10.0 before 4.15.0 and from 5.0.0-rc.0 before 5.0.0-rc.14."}], "id": "CVE-2026-76949", "lastModified": "2026-09-18T18:16:18.527", "metrics": {"cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "attackVector": "NETWORK", "availabilityRequirement": "NOT_DEFINED", "baseScore": 9.1, "baseSeverity": "CRITICAL", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "NONE", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "version": "4.0", "vulnAvailabilityImpact": "NONE", "vulnConfidentialityImpact": "HIGH", "vulnIntegrityImpact": "HIGH", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-76949", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "total"}], "role": "CISA Coordinator", "timestamp": "2026-09-18T14:24:28.652087Z", "version": "2.0.3"}}]}, "published": "2026-09-17T22:17:03.883", "references": [{"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "url": "https://cna.erlef.org/cves/CVE-2026-76949.html"}, {"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "url": "https://github.com/team-alembic/ash_authentication/commit/3d3de314692558d06ec13945f857f00514e95a8c"}, {"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "url": "https://github.com/team-alembic/ash_authentication/commit/9a34136b844abe179da1075067cf2835c64dcc12"}, {"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "url": "https://github.com/team-alembic/ash_authentication/commit/b9568a53b438247238b1c5a4f49c8d84650f4bba"}, {"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "url": "https://github.com/team-alembic/ash_authentication/security/advisories/GHSA-hh34-374j-pfr5"}, {"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "url": "https://osv.dev/vulnerability/EEF-CVE-2026-76949"}], "sourceIdentifier": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "vulnStatus": "Deferred", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-290"}], "source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db", "type": "Secondary"}]}

{}

{"affected": [{"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[4.10.0,4.15.0)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "semver", "value": "[5.0.0-rc.0,5.0.0-rc.14)"}}, {"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[0,*]"}}], "enrichment": {"confidence": 95.0, "confidence_source": "inferred", "scores": [{"score": 95.0, "source": "inferred"}, {"score": 100.0, "source": "matching"}]}, "original": {"product": "ash_authentication", "source": "cna", "vendor": "team-alembic"}, "product": "ash_authentication", "vendor": "team-alembic"}, {"configurations": [{"platform": null, "status": "affected", "versions": {"scheme": "generic", "value": "[0,*]"}}], "enrichment": {"confidence": 100.0, "confidence_source": "matching", "scores": [{"score": 100.0, "source": "matching"}]}, "original": {"product": "ash_authentication", "source": "cna", "vendor": "team-alembic"}, "product": "ash_authentication", "vendor": "team-alembic"}], "created": "2026-09-18T11:45:07.307251+00:00", "updated": "2026-09-18T23:45:15.931662+00:00", "vendors": ["team-alembic", "team-alembic$PRODUCT$ash_authentication"]}