# The Apache Airflow Samba provider's \`GCSToSambaOperator\` joined GCS object names to the SMB destination path without a containment check, so an object named with \`../\` segments resolved a write pat...

Advisory record · `GHSA-f6vj-48fm-hmvx`

- **Identifiers:** `GHSA-f6vj-48fm-hmvx` · `CVE-2026-49818` · `PYSEC-2026-208`
- **State:** Confirmed
- **Severity:** CVSS 6.5 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-22](https://cwe.mitre.org/data/definitions/22.html)
- **Tags:** [Path traversal](https://agentprime.io/advisories/tag/path-traversal.md)
- **Published:** 9 Jun 2026
- **Updated:** 4 Aug 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 9 Jun 2026, 09:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `apache-airflow-providers-samba` (PyPI): affected `<4.12.6`; fixed in `4.12.6`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> Versions of apache-airflow-providers-samba before 4.12.6 are affected. In GCSToSambaOperator, GCS object names containing "../" segments could resolve to a write path outside the configured destination_path. An attacker who can write objects into the source GCS bucket could cause files to be written to arbitrary locations on the Samba target when the operator runs. Upgrade apache-airflow-providers-samba to 4.12.6 or later, which checks that the resolved destination stays within destination_path.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 6.5 Medium, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`, from OSV

- **CISA KEV:** Not listed.
- **EPSS:** 0.0062, the 50th percentile, on 16 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:41 UTC: First seen by agentprime
- 31 Oct 2026, 14:41 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-208)

## Sources

- [GitHub Advisory Database: GHSA-f6vj-48fm-hmvx](https://github.com/advisories/GHSA-f6vj-48fm-hmvx)
- [OSV: GHSA-f6vj-48fm-hmvx](https://osv.dev/vulnerability/GHSA-f6vj-48fm-hmvx)
- <http://www.openwall.com/lists/oss-security/2026/06/09/8>
- <https://lists.apache.org/thread/3vs0m3p51psgf54tts18d6336g24x3sf>
- <https://github.com/apache/airflow/pull/67857>
- <https://github.com/advisories/GHSA-f6vj-48fm-hmvx>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-f6vj-48fm-hmvx>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-f6vj-48fm-hmvx/>. Everything for agents: <https://agentprime.io/llms.txt>.
