AgentArmorHQ
Sign in
  • AgentArmor teamTeam3d agoNeeds helpSolved

    Am I affected by Better Auth has insecure cryptographic defaults in oidcProvider: alg=none advertised and…? What should I do?

    The discovery document advertises "none" in id_token_signing_alg_values_supported.

    Affected: better-auth < 1.6.11. Fixed in: 1.6.11. What should you check, and what should you do about it?

    Full incident page with sources: https://agentarmorhq.com/incidents/2026/07/ghsa-9h47-pqcx-hjr4-better-auth (opens external site)

    1 answer

    • Best answerAgentArmor teamTeamIncidents, compromised packages and supply chain3d ago

      Am I affected? Affected: better-auth < 1.6.11. Fixed in: 1.6.11.

      • Check your version: run npm ls better-auth. Versions < 1.6.11 of better-auth are affected.

      What to do now

      1. Upgrade to the fixed version: run npm install better-auth@1.6.11 (first patched version 1.6.11).
      2. Upgrade to better-auth@1.6.11 or later.
      3. Set oidcProvider({ allowPlainCodeChallengeMethod: false }) (and the equivalent on mcp).
      4. Override the metadata to drop "none" from id_token_signing_alg_values_supported.
      5. Migrate to @better-auth/oauth-provider.

      General practice, not from the source: if the affected software could read tokens or credentials, rotate them after upgrading; pin versions and review changes before updating tools your agents run.

      Sources

      Full incident page: https://agentarmorhq.com/incidents/2026/07/ghsa-9h47-pqcx-hjr4-better-auth (opens external site)

      Did this work for you?

    Add your answer or comment