# CVE-2026-46491: SimpleSAMLphp casserver FileSystemTicketStore path traversal allows out-of-ticket-directory read/unserialize and conditional deletion

> Remote attackers can read and delete arbitrary files via path traversal in the CAS ticket store, requiring FileSystemTicketStore configuration.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jun 2026
- **Updated:** 10 Jun 2026
- **Also known as:** GHSA-jrrg-99xh-5j2q

## What is CVE-2026-46491?

CVE-2026-46491 is a high-severity path traversal vulnerability in simplesamlphp-module-casserver, published on 9 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SimpleSAMLphp-casserver is a CAS 1.0 and 2.0 compliant CAS server in the form of a SimpleSAMLphp module. Prior to version 7.0.3, simplesamlphp-module-casserver builds file paths for the file-based CAS ticket store by directly concatenating the configured ticket directory with an attacker-controlled ticket identifier. Public CAS validation/proxy endpoints pass attacker-controlled ticket / pgt query parameters into this store. In deployments using FileSystemTicketStore, a remote attacker can use path traversal sequences such as ../target.serialized to make the CAS server read and unserialize files outside the ticket directory. In the CAS 1.0 validation flow, the same attacker-selected path is also passed to deleteTicket() immediately after getTicket() returns, which can delete the target file when it is readable by the PHP process, deletable under the PHP process filesystem permissions, and unserializes to a value compatible with the ?array return type. This issue has been patched in version 7.0.3.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

2 open source packages ship an affected version, including simplesamlphp/simplesamlphp-module-casserver.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `simplesamlphp/simplesamlphp-module-casserver` | Packagist | All versions | 7.0.3 |
| `simplesamlphp/simplesamlphp-module-casserver` | Packagist | All versions | 7.0.3 |

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

Upgrade simplesamlphp/simplesamlphp-module-casserver to 7.0.3 or later.

## Is CVE-2026-46491 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-46491 is a high-severity path traversal vulnerability in simplesamlphp-module-casserver, published on 9 Jun 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-46491 in the wild and no public exploit code.

Affected packages and fixed versions:
- simplesamlphp/simplesamlphp-module-casserver (Packagist): affected all versions; fixed in 7.0.3
- simplesamlphp/simplesamlphp-module-casserver (Packagist): affected all versions; fixed in 7.0.3

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

## Sources

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

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