# CVE-2026-18127: Path traversal in Endpoint Manager

> Remote authenticated attackers can manipulate filenames to gain full write control over S3 session recording storage in Ivanti Endpoint Manager.

- **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Aug 2026
- **Updated:** 11 Aug 2026
- **Also known as:** GHSA-9vrc-hrp5-9j72

## What is CVE-2026-18127?

CVE-2026-18127 is a high-severity path traversal vulnerability in Ivanti Endpoint Manager, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

External control of a filename in the Core of Ivanti Endpoint Manager before version 2024 SU7 allows a remote authenticated attacker full write control over an S3 bucket configured for session recording storage.

Weakness: CWE-73 (External Control of File Name or Path)

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


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

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

## Is CVE-2026-18127 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-18127 is a high-severity path traversal vulnerability in Ivanti Endpoint Manager, published on 11 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-18127 in the wild and no public exploit code.

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

## Sources

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

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