# CVE-2026-41009: Local Blobstore may allow arbitrary reads/deletes

> Attackers can read or delete arbitrary files via path traversal in the local blobstore when processing agent responses.

- **Severity:** Medium 4.3 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:H/UI:P/VC:N/VI:H/VA:L/SC:N/SI:N/SA:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 May 2026
- **Updated:** 27 May 2026
- **Also known as:** GHSA-gq7j-4834-ccgp

## What is CVE-2026-41009?

CVE-2026-41009 is a medium-severity path traversal vulnerability in Cloud Foundry Foundation BOSH Director, published on 27 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

When the director sends a long-running request (e.g. compile_package), the agent's reply JSON is consumed by AgentClient. inject_compile_log (line 332-339) reads response['value']['result']['compile_log_id'] and format_exception (line 318-325) reads exception['blobstore_id']; both pass the agent-supplied string unmodified to download_and_delete_blob(blob_id) (line 344-349), which calls @resource_manager.get_resource(blob_id) and, in an ensure block, @resource_manager.delete_resource(blob_id). Api::ResourceManager forwards the id straight to blobstore.get(id) / blobstore.delete(id). When the director is configured with the local blobstore provider, Blobstore::LocalClient#object_file_path(oid) is File.join(@blobstore_path, oid) (local_client.rb:54-56) with no normalisation, so oid = "../../jobs/director/config/director.yml" resolves outside the blobstore root.

Affected versions:
BOSH Director: All versions prior to v282.1.12

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

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

It affects 1 product.


Products: Cloud Foundry Bosh.

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

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

## Is CVE-2026-41009 being exploited?

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

## Other vulnerabilities in Cloud Foundry Foundation BOSH Director

- [CVE-2017-4961](https://insights.sbomify.com/CVE-2017-4961/): Command injection in Cloud Foundry Foundation BOSH Release (high 8.8)
- [CVE-2018-11083](https://insights.sbomify.com/CVE-2018-11083/): Bosh accepts refresh tokens in place of an access token (high 8.4)
- [CVE-2026-41704](https://insights.sbomify.com/CVE-2026-41704/): Compromised VM can make arbitrary blobstore deletes (medium 6.8)
- [CVE-2019-11271](https://insights.sbomify.com/CVE-2019-11271/): Bosh Deployment logs leak sensitive information (medium 6.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41009 is a medium-severity path traversal vulnerability in Cloud Foundry Foundation BOSH Director, published on 27 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-41009 in the wild and no public exploit code.

Affected product: Cloud Foundry Foundation BOSH Director. 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-41009/ (Markdown: https://insights.sbomify.com/CVE-2026-41009/index.md)
```

## Sources

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

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