Implementation trusts the "me" field returned by the authorization server without verifying it
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Security bypass
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-290.
Summary
### Impact A malicious user can sign in as a user with any IndieAuth identifier. This is because the implementation does not verify that the final `"me"` URL value returned by the authorization server belongs to the same domain as the initial value entered by the user. ### Patches Version 1.1 fixes this issue. ### Workarounds There is no workaround. Upgrade to 1.1 immediately. ### References - [Security Considerations: Differing User Profile URLs](https://indieauth.spec.indieweb.org/#differing-user-profile-urls-li-1) in the IndieAuth specification. ### For more information If you have any questions or comments about this advisory: * Open an issue in [simonw/datasette-indieauth](https://github.com/simonw/datasette-indieauth/issues)
Why it matters now
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | datasette-indieauth (PyPI) | 1.0 to before 1.1 | 1.1 | Patch available | GHSA-mjcr-rqjg-rhg3 |
- datasette-indieauth (PyPI) Vendor— Affected 1.0 to before 1.1 Fixed in 1.1 Patch available GHSA-mjcr-rqjg-rhg3
Remediation
- Fix · GHSA-mjcr-rqjg-rhg3 datasette-indieauth (PyPI) Fixed in 1.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-mjcr-rqjg-rhg3
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences