# CVE-2026-9507: Session fixation vulnerability in Enhancesoft's osTicket

> Attackers can hijack user accounts in osTicket by maintaining a pre-authentication session ID after the victim logs in.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 Jun 2026
- **Updated:** 16 Jun 2026
- **Also known as:** GHSA-6cj6-2fg2-2r4g

## What is CVE-2026-9507?

CVE-2026-9507 is a medium-severity authentication bypass vulnerability in Enhancesoft osTicket, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-38 (Path Traversal: '\absolute\pathname\here')

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


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

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

## Is CVE-2026-9507 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-9507 is a medium-severity authentication bypass vulnerability in Enhancesoft osTicket, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-9507 in the wild and no public exploit code.

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

## Sources

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

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