# CVE-2026-26895: Information disclosure in n/a

> Remote attackers can enumerate valid usernames via the password reset page, exposing user account existence.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** 2 Apr 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-6p2p-wf8c-wq75

## What is CVE-2026-26895?

CVE-2026-26895 is a medium-severity vulnerability in n/a, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

User enumeration vulnerability in /pwreset.php in osTicket v1.18.2 allows remote attackers to enumerate valid usernames registered in the platform.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Enhancesoft Osticket.

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

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

## Is CVE-2026-26895 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-42235](https://insights.sbomify.com/CVE-2021-42235/): SQL injection in n/a (critical 9.8)
- [CVE-2020-24881](https://insights.sbomify.com/CVE-2020-24881/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2022-31888](https://insights.sbomify.com/CVE-2022-31888/): Other in n/a (high 8.8)
- [CVE-2019-14749](https://insights.sbomify.com/CVE-2019-14749/): Other in n/a (high 8.8)
- [CVE-2026-22200](https://insights.sbomify.com/CVE-2026-22200/): osTicket (1.18.x < 1.18.3, 1.17.x < 1.17.7) PDF Export Arbitrary File Read (high 8.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-26895 is a medium-severity vulnerability in n/a, published on 2 Apr 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-26895 exists.

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

## Sources

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

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