# CVE-2026-18363: Weak password recovery mechanism in osTicket by Enhancesoft LLC

> Attackers can reuse expired password reset tokens to take over accounts due to flawed expiry validation logic in osTicket.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/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:** 30 Jul 2026
- **Updated:** 30 Jul 2026
- **Also known as:** GHSA-h2gf-gwxr-4pm4

## What is CVE-2026-18363?

CVE-2026-18363 is a critical vulnerability in Enhancesoft LLC osTicket, published on 30 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A logic vulnerability in the password reset token validation routine implemented by osTicket in versions prior to v1.17.8 and v1.18.4. During the password reset process, the application retrieves the timestamp associated with the provided token and checks whether the configured validity period has expired. Consequently, the expiry check is only performed if the timestamp lookup fails, allowing tokens with an existing timestamp to bypass the intended expiry validation. Therefore, an attacker able to obtain a valid password reset token could reuse it to perform an unauthorised password reset and compromise the affected account.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

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


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

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

## Is CVE-2026-18363 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18363 is a critical vulnerability in Enhancesoft LLC osTicket, published on 30 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-18363 in the wild and no public exploit code.

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

## Sources

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

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