# CVE-2026-81033: Automatisch through 0.15.0 User Enumeration via Forgot-Password Response Discrepancy

> Unauthenticated attackers can enumerate registered user accounts by analyzing response discrepancies in the forgot-password endpoint.

- **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 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-p996-89cm-88c6

## What is CVE-2026-81033?

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

### Official description

Automatisch reveals whether an address is registered through the response to its forgot-password request. The controller at packages/backend/src/controllers/internal/api/v1/users/forgot-password.js looks the address up and chains a not-found throw onto the query, so an address with no account raises an error that the global handler renders as a not-found status, while a registered address proceeds to send the reset message and returns no-content. The route is mounted without authentication. Submitting candidate addresses and comparing the two status codes therefore establishes which addresses hold accounts, with no credential and no rate limiting in the path.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

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

## Is CVE-2026-81033 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-81033 is a medium-severity vulnerability in automatisch, published on 26 Aug 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-81033 in the wild and no public exploit code.

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

## Sources

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

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