CVE-2026-18363

CRITICALPre-NVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (41st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-51068 (ENISA EUVD) · GHSA-h2gf-gwxr-4pm4 (GitHub Security Advisories)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.1Exploit: None knownExposed services: Not assessed

The issue has been resolved in versions v1.17.8 and v1.18.4 (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)) — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
41
EG Risk 41/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The issue has been resolved in versions v1.17.8 and v1.18.4 (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)). Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
41st
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

The issue has been resolved in versions v1.17.8 and v1.18.4 (from the CVE record's solution, Spanish National Cybersecurity Institute, S.A. (INCIBE)). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 30, 2026

Last Modified

October 23, 2026

Advisory Details (1)

Auto-updated Sep 16, 2026
Fix named in the CVE record's solution (Spanish National Cybersecurity Institute, S.A. (INCIBE)).
Web page

Weak password recovery mechanism in osTicket by Enhancesoft LLC | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/weak-password-recovery-mechanism-osticket-enhancesoft-llc

Vendor Advisories for CVE-2026-18363(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 23× in last 7d / 91× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 476 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 376 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 22:44 UTCEG score recompute
  2. 2026-11-02 22:44 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  3. 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  4. 2026-11-02 00:45 UTCEG score recompute
  5. 2026-11-02 00:45 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  6. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  7. 2026-11-01 02:52 UTCEG score recompute
  8. 2026-11-01 02:52 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  9. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  10. 2026-10-31 04:58 UTCEG score recompute
  11. 2026-10-31 04:58 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  12. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  13. 2026-10-30 07:05 UTCEG score recompute
  14. 2026-10-30 07:05 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  15. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  16. 2026-10-29 09:11 UTCEG score recompute
  17. 2026-10-29 09:10 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  18. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  19. 2026-10-28 11:17 UTCEG score recompute
  20. 2026-10-28 11:17 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  21. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  22. 2026-10-27 12:49 UTCEG score recompute
  23. 2026-10-27 12:49 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  24. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  25. 2026-10-26 16:21 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
Show 75 more
  1. 2026-10-25 18:20 UTCEG score recompute
  2. 2026-10-25 18:19 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  3. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  4. 2026-10-25 14:45 UTCEG score recompute
  5. 2026-10-24 20:21 UTCEG score recompute
  6. 2026-10-24 20:21 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  8. 2026-10-23 22:28 UTCEG score recompute
  9. 2026-10-23 22:27 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  10. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  11. 2026-10-23 01:06 UTCEG score recompute
  12. 2026-10-23 01:06 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  13. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  14. 2026-10-22 02:20 UTCEG score recompute
  15. 2026-10-22 02:20 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  16. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  17. 2026-10-21 04:13 UTCEG score recompute
  18. 2026-10-21 04:13 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  19. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  20. 2026-10-20 06:14 UTCEG score recompute
  21. 2026-10-20 06:14 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  22. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  23. 2026-10-19 08:19 UTCEG score recompute
  24. 2026-10-19 08:19 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  25. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  26. 2026-10-18 10:08 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  27. 2026-10-18 03:59 UTCEG score recompute
  28. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  29. 2026-10-17 06:30 UTCEG score recompute
  30. 2026-10-17 06:30 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  31. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-10-16 07:57 UTCEG score recompute
  33. 2026-10-16 07:57 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  34. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  35. 2026-10-15 06:59 UTCEG score recompute
  36. 2026-10-15 06:58 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  37. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  38. 2026-10-14 02:48 UTCEG score recompute
  39. 2026-10-14 02:48 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  40. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  41. 2026-10-12 22:54 UTCEG score recompute
  42. 2026-10-12 22:54 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  43. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  44. 2026-10-12 16:27 UTCEG score recompute
  45. 2026-10-12 09:27 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  46. 2026-10-11 20:07 UTCEG score recompute
  47. 2026-10-11 17:20 UTCEG score recompute
  48. 2026-10-11 14:52 UTCEG score recompute
  49. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  50. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  52. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  53. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  54. 2026-10-07 04:06 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  55. 2026-10-06 23:53 UTCEG score recompute
  56. 2026-10-06 23:53 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  57. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  58. 2026-10-05 20:01 UTCEG score recompute
  59. 2026-10-05 20:01 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  60. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  61. 2026-10-04 23:58 UTCEG score recompute
  62. 2026-10-04 23:58 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  63. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  64. 2026-10-04 12:32 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  65. 2026-10-04 06:41 UTCEG score recompute
  66. 2026-10-04 06:41 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  67. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  68. 2026-10-03 03:08 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  69. 2026-10-02 17:00 UTCEG score recompute
  70. 2026-10-02 16:59 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  71. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  72. 2026-10-01 14:46 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  73. 2026-10-01 10:58 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  74. 2026-10-01 06:57 UTCGHSA enrichmentGHSA-h2gf-gwxr-4pm4 · GitHub severity CRITICAL
  75. 2026-10-01 03:08 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-18363?
CVE-2026-18363 is a critical-severity vulnerability; its CVE record was published on July 30, 2026. 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…
When was CVE-2026-18363 made public?
CVE-2026-18363 was made public on July 30, 2026: that is the date its CVE record's CNA, Spanish National Cybersecurity Institute, S.A. (INCIBE), gives for when the vulnerability was made public. The CVE record itself was published on July 30, 2026. EchelonGraph's copy of the record carries a last-modified date of October 23, 2026; the record at its source may have been updated since.
Is CVE-2026-18363 actively exploited?
CVE-2026-18363 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-18363?
CVE-2026-18363 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-18363?
The CVE record's solution for CVE-2026-18363, written by its CNA Spanish National Cybersecurity Institute, S.A. (INCIBE), names the fix: "The issue has been resolved in versions v1.17.8 and v1.18.4." The vendor advisories EchelonGraph has for CVE-2026-18363 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-18363

Explore →

Is Your Infrastructure Affected by CVE-2026-18363?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs