External risk intelligence

osTicket Password Reset Token Validation Logic Flaw

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-18363

osTicket is a widely deployed, web-based help desk ticketing system that is typically configured as a public-facing web application to allow users and customers to submit and manage support requests over the internet.

Halo Surface Signal: 4 out of 5 — likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a logic vulnerability in osTicket's password reset function. The flaw allows an attacker who obtains a valid password reset token to bypass expiry checks and potentially reset the password for an affected account, leading to unauthorized access. The primary concern is confirming the relevance and exposure of this issue within your environment.

  • Password resets can be exploited.
  • Impacts user account access security.
  • Confirm if osTicket is used.

Attack Path

How an attacker could exploit the issue

An attacker could gain unauthorized access to a user's account by exploiting a flaw in the password reset process. If an attacker can obtain a valid password reset token, they may be able to bypass the intended expiration check. This could allow them to reset the password and take control of the account.

  • No authentication needed for initial access.
  • Token bypass allows password reset.
  • Account compromise and data theft.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow an attacker to reset a user's password if they can obtain a valid password reset token. This occurs because the system may not properly check if the token has expired when certain conditions are met during the password reset process.

  • Account takeover
  • Password reset token interception
  • Unauthorized account access

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability in osTicket affects the password reset process and could allow an attacker to compromise user accounts. Platform or application owners should first identify all instances of osTicket, determine their exposure to the internet, and confirm business criticality. Subsequently, a remediation plan should be developed based on the assessed risk.

  • Platform/Application owners must take ownership.
  • Verify osTicket instances and exposure.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is osTicket?

osTicket is a widely used, open-source help desk software designed to manage customer support requests. It provides a web-based interface where users and staff can track, prioritize, and respond to support tickets. Because it acts as a central hub for communication, it is often configured as a public-facing web application so that end users can easily submit or check the status of their inquiries directly through a browser.

What does CVE-2026-18363 mean?

This CVE identifies a logic flaw classified as CWE-640, which concerns weak password recovery mechanisms. Specifically, the software's password reset routine contains a programming error where it fails to verify if a reset token has expired under certain conditions. Instead of checking the expiration time first, the system only performs this check if it cannot find an existing timestamp, effectively allowing old or already used tokens to remain active.

How can an attacker trigger this vulnerability?

An attacker needs to obtain a valid password reset token for a target account to initiate the exploit. The bug is triggered when the system skips the intended expiration validation because a timestamp is successfully retrieved during the reset process. Importantly, the vulnerability does not trigger if the token is invalid or if the system fails to find a timestamp, as those scenarios default to the proper expiration check.

Is my osTicket installation at risk?

According to Halo Surface Signal, osTicket is frequently deployed as a public-facing application to support internet-based ticket management. Because this vulnerability does not require prior authentication to exploit, any instance accessible over the internet is potentially at higher risk of unauthorized account takeover. You should prioritize internal assessments to determine if your specific installation is reachable by external traffic.

What should I do to secure my system?

Your first step is to verify the version of osTicket currently running in your environment. Confirm your deployment's reachability and criticality to business operations. Ensure you are aware of the official vendor guidance regarding the affected versions v1.17.8 and v1.18.4, and prepare a plan to apply the necessary updates provided by the vendor to remediate the logic flaw in the password reset process.