withdrawn 2026-11-04 03:36Z

This entry duplicated another and was withdrawn in its favour.

Superseded by ETK-2026-3439.

ETK-2026-3415Zero's internal tracking ID, independent of the CVE number.

withdrawn
no check availablenot proven exploitable
awaiting cvepublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:@better-auth/expo >= 1.4.0-beta.6, < 1.7.16; >= 1.8.0-beta.0, < 1.8.0-beta.5; < 1.7.16
fixed in 1.7.16, 1.8.0-beta.5
CWE-287 Improper Authentication
ETK-2026-3415Zero's internal tracking ID, independent of the CVE number., no cve assigned
pkg:npm/@better-auth/expo
pkg:npm/better-auth
1h 40msince last run
–AI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org, not yet published
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Servers that register the expo() plugin from affected @better-auth/expo releases can sign attacker-controlled authorization state using the application secret. An unauthenticated attacker who knows a user's email address may be able to take over that account and alter its email address; session-cache use can expand impact when a user ID is known. Wildcard trustedOrigins entries can also unintentionally trust malformed or unintended URLs.

mitigation

Upgrade both @better-auth/expo and better-auth to 1.7.16, or to 1.8.0-beta.5 on the beta release line, then rotate the application secret if the endpoint was reachable. Remove the expo() plugin if Expo social sign-in is not needed, and review wildcard entries in trustedOrigins.

fixed in 1.7.16, 1.8.0-beta.5

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
–
cve.org record, t = 0The moment cve.org publishes the CVE in full.
not published yet
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

No signals recorded for this entry yet.

this entry in the feed

GET /api/v1/feed/ETK-2026-3415

{
  "etk_id": "ETK-2026-3415",
  "cve_id": null,
  "display_id": "ETK-2026-3415",
  "ghsa_id": null,
  "euvd_id": null,
  "status": "retired",
  "anchor_state": "awaiting_cve",
  "title": "Unauthenticated token signing in Better Auth Expo plugin",
  "summary": "Servers that register the `expo()` plugin from affected `@better-auth/expo` releases can sign attacker-controlled authorization state using the application secret. An unauthenticated attacker who knows a user's email address may be able to take over that account and alter its email address; session-cache use can expand impact when a user ID is known. Wildcard `trustedOrigins` entries can also unintentionally trust malformed or unintended URLs.",
  "mitigation": "Upgrade both `@better-auth/expo` and `better-auth` to 1.7.16, or to 1.8.0-beta.5 on the beta release line, then rotate the application secret if the endpoint was reachable. Remove the `expo()` plugin if Expo social sign-in is not needed, and review wildcard entries in `trustedOrigins`.",
  "vendor": "npm",
  "product": "npm:@better-auth/expo",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.4.0-beta.6, < 1.7.16"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.7.16"
      ],
      "package_name": "@better-auth/expo",
      "purl": "pkg:npm/@better-auth/expo"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.8.0-beta.0, < 1.8.0-beta.5"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.8.0-beta.5"
      ],
      "package_name": "@better-auth/expo",
      "purl": "pkg:npm/@better-auth/expo"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.7.16"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.7.16"
      ],
      "package_name": "better-auth",
      "purl": "pkg:npm/better-auth"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.8.0-beta.0, < 1.8.0-beta.5"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.8.0-beta.5"
      ],
      "package_name": "better-auth",
      "purl": "pkg:npm/better-auth"
    }
  ],
  "cwes": [
    287
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": null,
  "t0_at": null,
  "signals": {}
}

published 2026-11-03 22:38Z
last change 2026-11-04 03:36Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.