# CVE-2026-56312: Capgo - Account Creation Before CAPTCHA Validation in accept_invitation Endpoint

> Attackers can bypass CAPTCHA validation to create unauthorized accounts and consume invite links in Capgo applications.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-pj32-crq8-r292, GHSA-whc5-fvr7-g5v3

## What is CVE-2026-56312?

CVE-2026-56312 is a medium-severity vulnerability in Capgo, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Capgo before 12.128.2 contains an improper validation vulnerability in the accept_invitation endpoint that creates user accounts before captcha validation is enforced. Attackers can bypass captcha protection by sending POST requests with invalid captcha tokens to create unwanted accounts and burn invite links.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-56312?


## How do I fix CVE-2026-56312?

No fix has been published for CVE-2026-56312 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-56312 being exploited?

There is no known exploitation of CVE-2026-56312 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56312 and fix it if it is affected.

What it is: CVE-2026-56312 is a medium-severity vulnerability in Capgo, published on 10 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56312 in the wild and no public exploit code.

Affected product: Capgo. 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-56312/ (Markdown: https://insights.sbomify.com/CVE-2026-56312/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56312
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56312
- OSV: https://osv.dev/vulnerability/CVE-2026-56312

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56312/
Summaries are generated and may contain mistakes; the official description above is the record.