Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unratedamended

Implementation trusts the "me" field returned by the authorization server without verifying it

GHSA-mjcr-rqjg-rhg3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (datasette-indieauth 1.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

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 in the IndieAuth specification. For more information If you have any questions or comments about this advisory: Open an issue in simonw/datasette-indieauth

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-mjcr-rqjg-rhg3

  2. Revision 1 · created ·

    Published from osv record GHSA-mjcr-rqjg-rhg3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-mjcr-rqjg-rhg3

Advisory: Implementation trusts the "me" field returned by the authorization server without verifying it
IDs: GHSA-mjcr-rqjg-rhg3
Record: https://patchnext.com/advisories/ghsa-mjcr-rqjg-rhg3 (revision 2, source checked 26 Oct 2026, 13:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: datasette-indieauth 1.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI datasette-indieauth: affected >= 1.0, <= 1.0; fixed in 1.1

## Suggested inspection (read-only)
- `python -m pip show datasette-indieauth`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on datasette-indieauth.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-mjcr-rqjg-rhg3 (OSV record GHSA-mjcr-rqjg-rhg3 lists affected ranges: PyPI datasette-indieauth >=1.0 <1.1 (fixed))
- Verified: https://github.com/advisories/GHSA-mjcr-rqjg-rhg3 (GitHub-reviewed advisory GHSA-mjcr-rqjg-rhg3 lists affected ranges: PyPI datasette-indieauth >=1.0 <=1.0)

Commands are suggestions: review each one before running it.

Loading voting…