Which versions of datasette-indieauth are affected by GHSA-MJCR-RQJG-RHG3?

datasette-indieauth (pip) versions = 1.0 is affected.

Is there a fix for GHSA-MJCR-RQJG-RHG3?

Yes. GHSA-MJCR-RQJG-RHG3 is fixed in 1.1. Upgrade to this version or later.

Is GHSA-MJCR-RQJG-RHG3 exploitable, and should I be worried?

Whether GHSA-MJCR-RQJG-RHG3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-MJCR-RQJG-RHG3 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-MJCR-RQJG-RHG3?

Upgrade datasette-indieauth to 1.1 or later.

GHSA-MJCR-RQJG-RHG3 in datasette-indieauth

GHSA-MJCR-RQJG-RHG3

GHSA-MJCR-RQJG-RHG3 is a critical-severity security vulnerability in datasette-indieauth (pip), affecting versions = 1.0. It is fixed in 1.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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

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.

Affected versions

datasette-indieauth (= 1.0)

Security releases

datasette-indieauth → 1.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Version 1.1 fixes this issue.

Frequently Asked Questions

What is GHSA-MJCR-RQJG-RHG3? GHSA-MJCR-RQJG-RHG3 is a critical-severity security vulnerability in datasette-indieauth (pip), affecting versions = 1.0. It is fixed in 1.1.
Which versions of datasette-indieauth are affected by GHSA-MJCR-RQJG-RHG3? datasette-indieauth (pip) versions = 1.0 is affected.
Is there a fix for GHSA-MJCR-RQJG-RHG3? Yes. GHSA-MJCR-RQJG-RHG3 is fixed in 1.1. Upgrade to this version or later.
Is GHSA-MJCR-RQJG-RHG3 exploitable, and should I be worried? Whether GHSA-MJCR-RQJG-RHG3 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-MJCR-RQJG-RHG3 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-MJCR-RQJG-RHG3? Upgrade datasette-indieauth to 1.1 or later.