# CVE-2026-27462: Combodo iTop: User enumeration via password reset

> Attackers can enumerate valid usernames via inconsistent password reset responses in Combodo iTop, facilitating targeted attacks.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** GHSA-888g-gv33-xwwx

## What is CVE-2026-27462?

CVE-2026-27462 is a high-severity vulnerability in Combodo iTop, published on 21 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Combodo iTop is a web based IT service management tool. Prior to 3.2.3, iTop returns different responses for valid/invalid usernames depending on multiple factors in the reset password mechanism, leading to user enumeration. This issue has been fixed in version 3.2.3.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

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

## Is CVE-2026-27462 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-27462 is a high-severity vulnerability in Combodo iTop, published on 21 Aug 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-27462 exists.

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

## Sources

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

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