# CVE-2026-85199: Path traversal in Eclipse aeriOS

> Unauthenticated attackers can exploit path traversal in the REST API to write or delete files outside intended directories, impacting data integrity and availability.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2026
- **Updated:** 3 Sep 2026
- **Also known as:** GHSA-vg3m-qwjp-6wvx

## What is CVE-2026-85199?

CVE-2026-85199 is a high-severity path traversal vulnerability in Eclipse aeriOS, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Eclipse aeriOS Self-orchestrator versions prior to 1.2.1 contain a path traversal vulnerability in the REST API. User-controlled identifiers used to create, update, or delete Self-orchestrator resources were incorporated into filesystem paths without adequate validation or sanitization. An unauthenticated remote attacker able to access the Self-orchestrator API could therefore supply specially crafted identifiers containing path traversal sequences to write or delete JSON files outside the intended application directories, subject to the filesystem permissions of the Self-orchestrator process.

The impact is increased by the absence of authentication on the affected API and by the container running with elevated privileges in the affected deployment configuration.

The issue has been addressed in version 1.2.1 by introducing validation and sanitization of user-controlled identifiers before they are used to construct filesystem paths, preventing path separator characters from being used to escape the intended directories.

Weakness: CWE-23 (Relative Path Traversal), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-206 (Observable Internal Behavioral Discrepancy)

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


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

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

## Is CVE-2026-85199 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-85199 is a high-severity path traversal vulnerability in Eclipse aeriOS, published on 3 Sep 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-85199 in the wild and no public exploit code.

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

## Sources

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

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