# CVE-2026-109152: jbardin scp.py SCP Receive _recv_pushd path traversal

> A path traversal vulnerability in the SCP receive handler allows remote attackers to read or write files outside the intended directory.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **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:** Yes
- **Published:** 13 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-109152, GHSA-3f22-449q-g7c5, OESA-2026-4429, OESA-2026-4430, OESA-2026-4431, UBUNTU-CVE-2026-109152

## What is CVE-2026-109152?

CVE-2026-109152 is a medium-severity path traversal vulnerability in jbardin scp.py, published on 13 Oct 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 security vulnerability has been detected in jbardin scp.py up to 0.16.1. The impacted element is the function _recv_file/_recv_pushd of the component SCP Receive Handler. The manipulation leads to path traversal. Remote exploitation of the attack is possible. Upgrading to version 0.16.2 is sufficient to resolve this issue. The identifier of the patch is 42fc3aaa71411daed60544e3b40179c1038bed5d. Upgrading the affected component is advised. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-109152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-109152 is a medium-severity path traversal vulnerability in jbardin scp.py, published on 13 Oct 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-109152 in the wild and no public exploit code.

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

## Sources

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

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