# CVE-2026-100677: stoatchat before 0.15.5 Account Enumeration via Error Location

> Unauthenticated attackers can enumerate registered users by analyzing error location fields in login responses, exposing user account existence.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/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:** 26 Sep 2026
- **Updated:** 30 Sep 2026
- **Also known as:** GHSA-h44h-xx2j-hp56, GHSA-v7jg-f6q5-rwc7

## What is CVE-2026-100677?

CVE-2026-100677 is a medium-severity vulnerability in stoatchat, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

stoatchat before 0.15.5 contains an account enumeration vulnerability in the login endpoint that exposes source file locations in error responses. Unauthenticated attackers can distinguish between registered and unregistered email addresses by comparing error location fields returned from POST /api/auth/session/login requests.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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


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

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

## Is CVE-2026-100677 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100677 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-100677 is a medium-severity vulnerability in stoatchat, published on 26 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-100677 exists.

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

## Sources

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

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