CVE-2026-121728 SourceHut meta.sr.ht 0.56.11 before 0.89.0 Registration Authorization Bypass via /register/step2
Medium 6.9
Published
Updated
Check this codebase for CVE-2026-121728 and fix it if it is affected.
What it is: CVE-2026-121728 is a medium-severity vulnerability in SourceHut meta.sr.ht, published on 3 Nov 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121728 exists.
Affected product: SourceHut meta.sr.ht. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-121728/ (Markdown: https://insights.sbomify.com/CVE-2026-121728/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-121728?
CVE-2026-121728 is a medium-severity vulnerability in SourceHut meta.sr.ht, published on 3 Nov 2026.
Official description
SourceHut meta.sr.ht 0.56.11 before 0.89.0 contains an authorization bypass vulnerability that allows unauthenticated attackers to register accounts when public registration is disabled. Attackers can obtain a CSRF token from /login and POST credentials to /register/step2, which invokes the unchecked GraphQL RegisterAccount mutation to create accounts.
Weakness: CWE-862
Which versions are affected by CVE-2026-121728?
How do I fix CVE-2026-121728?
No fix has been published for CVE-2026-121728 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-121728 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-121728 exists.
Sources
Also known as GHSA-j8p6-f6h2-jc6f.