CVE-2026-9507

MEDIUMPre-NVD 5.15.1—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.1 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 67% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:incibe, epss
5.1
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A session fixation vulnerability has been identified in osTicket v1.18.2. This security flaw allows an attacker to hijack a victim’s account by keeping the initial session identifier (OSTSESSID) active after a successful login.

The issue lies in the fact that the application does not invalidate the pre-authentication cookie or generate a new identifier for the authenticated context. As a result, if an attacker manages to set a known session identifier in the victim’s browser, they will be able to maintain unauthorised access to the account once the victim has authenticated.

CVSS v3
5.1
EG Score
5.1(medium)
EPSS
32.9%
KEV
Not listed

Published

June 16, 2026

Last Modified

June 16, 2026

Advisory Details (1)

Auto-updated Jun 16, 2026
No patch confirmed yet.
generic

Session fixation vulnerability in Enhancesoft's osTicket | INCIBE-CERT | INCIBE

https://www.incibe.es/en/incibe-cert/notices/aviso/session-fixation-vulnerability-enhancesofts-osticket

Vendor Advisories for CVE-2026-9507(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 9× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-22 14:08 UTCEPSS rescore
  2. 2026-07-21 15:25 UTCEPSS rescore
  3. 2026-07-21 15:25 UTCEPSS rescore
  4. 2026-07-20 17:08 UTCEPSS rescore
  5. 2026-07-19 14:31 UTCEPSS rescore
  6. 2026-07-19 02:29 UTCEPSS rescore
  7. 2026-07-18 10:04 UTCEPSS rescore
  8. 2026-07-16 22:41 UTCGHSA enrichment
  9. 2026-07-16 17:03 UTCEPSS rescore
  10. 2026-07-15 16:57 UTCEPSS rescore
  11. 2026-07-15 16:05 UTCGHSA enrichment
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-14 16:56 UTCGHSA enrichment
  14. 2026-07-13 22:31 UTCEPSS rescore
  15. 2026-07-13 17:48 UTCGHSA enrichment
  16. 2026-07-13 06:13 UTCEPSS rescore
  17. 2026-07-12 18:10 UTCGHSA enrichment
  18. 2026-07-12 05:46 UTCEPSS rescore
  19. 2026-07-11 19:00 UTCGHSA enrichment
  20. 2026-07-11 08:27 UTCEPSS rescore
  21. 2026-07-10 19:51 UTCGHSA enrichment
  22. 2026-07-09 20:43 UTCGHSA enrichment
  23. 2026-07-09 19:10 UTCEPSS rescore
  24. 2026-07-08 21:32 UTCGHSA enrichment
  25. 2026-07-08 15:16 UTCEPSS rescore
Show 43 more
  1. 2026-07-07 22:24 UTCGHSA enrichment
  2. 2026-07-07 13:46 UTCEPSS rescore
  3. 2026-07-06 23:16 UTCGHSA enrichment
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-05 08:44 UTCGHSA enrichment
  7. 2026-07-05 02:31 UTCEPSS rescore
  8. 2026-07-04 09:21 UTCGHSA enrichment
  9. 2026-07-04 06:31 UTCEPSS rescore
  10. 2026-07-03 05:56 UTCGHSA enrichment
  11. 2026-07-02 06:44 UTCGHSA enrichment
  12. 2026-07-01 15:07 UTCEPSS rescore
  13. 2026-07-01 07:36 UTCGHSA enrichment
  14. 2026-06-30 23:22 UTCEPSS rescore
  15. 2026-06-30 08:27 UTCGHSA enrichment
  16. 2026-06-29 14:06 UTCEPSS rescore
  17. 2026-06-29 09:19 UTCGHSA enrichment
  18. 2026-06-28 14:07 UTCEPSS rescore
  19. 2026-06-28 10:10 UTCGHSA enrichment
  20. 2026-06-28 04:56 UTCEPSS rescore
  21. 2026-06-27 10:59 UTCGHSA enrichment
  22. 2026-06-27 03:08 UTCEPSS rescore
  23. 2026-06-26 11:51 UTCGHSA enrichment
  24. 2026-06-25 13:50 UTCEPSS rescore
  25. 2026-06-25 07:03 UTCGHSA enrichment
  26. 2026-06-24 14:05 UTCEPSS rescore
  27. 2026-06-24 07:45 UTCGHSA enrichment
  28. 2026-06-23 21:33 UTCEPSS rescore
  29. 2026-06-23 08:06 UTCGHSA enrichment
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-22 08:57 UTCGHSA enrichment
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 09:40 UTCGHSA enrichment
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-20 10:31 UTCGHSA enrichment
  36. 2026-06-19 19:26 UTCEPSS rescore
  37. 2026-06-19 11:19 UTCGHSA enrichment
  38. 2026-06-18 17:52 UTCEPSS rescore
  39. 2026-06-18 12:08 UTCGHSA enrichment
  40. 2026-06-17 17:53 UTCEPSS rescore
  41. 2026-06-17 12:55 UTCGHSA enrichment
  42. 2026-06-16 13:47 UTCEG score recompute
  43. 2026-06-16 13:46 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-9507?
CVE-2026-9507 is a medium vulnerability published on June 16, 2026. A session fixation vulnerability has been identified in osTicket v1.18.2. This security flaw allows an attacker to hijack a victim’s account by keeping the initial session identifier (OSTSESSID) active after a successful login. The issue lies in the fact that the application does not invalidate the…
When was CVE-2026-9507 disclosed?
CVE-2026-9507 was first published in the National Vulnerability Database on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-9507 actively exploited?
CVE-2026-9507 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 32.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-9507?
CVE-2026-9507 has a CVSS v4.0 base score of 5.1 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-9507?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-9507, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-9507?

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

Start Free Scan →Browse All CVEs