# CVE-2025-22152: Improper Path Validation Enables Path Traversal in Multiple Components in Atheos

> Attackers can read, modify, or execute arbitrary files on the server due to improper path validation in Atheos cloud IDE.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jan 2025
- **Updated:** 10 Jan 2025

## What is CVE-2025-22152?

CVE-2025-22152 is a critical path traversal vulnerability in Atheos, published on 10 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Atheos is a self-hosted browser-based cloud IDE. Prior to v600, the $path and $target parameters are not properly validated across multiple components, allowing an attacker to read, modify, or execute arbitrary files on the server. These vulnerabilities can be exploited through various attack vectors present in multiple PHP files. This vulnerability is fixed in v600.

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-22152?


## How do I fix CVE-2025-22152?

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

## Is CVE-2025-22152 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22152 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-22152 and fix it if it is affected.

What it is: CVE-2025-22152 is a critical path traversal vulnerability in Atheos, published on 10 Jan 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-22152 exists.

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

## Sources

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

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