# GHSA-g28h-2cmm-rj9x: langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputs

> Attackers can read local files by supplying filesystem paths as image inputs to VLM requests in LangChain NVIDIA AI endpoints.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026

## What is GHSA-g28h-2cmm-rj9x?

GHSA-g28h-2cmm-rj9x is a path traversal vulnerability in langchain-nvidia-ai-endpoints, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

## Summary

`langchain-nvidia-ai-endpoints` versions before 1.4.2 accepted local filesystem paths as image inputs for Vision Language Model (VLM) requests. If an application passed attacker-controlled image input to `ChatNVIDIA` or VLM reranking APIs, an attacker could cause files readable by the application process to be read and included in the outbound request to the configured NVIDIA/NIM model endpoint.

## Impact

Applications are affected if they use VLM image inputs with `ChatNVIDIA` or `NVIDIARerank` and allow untrusted users to control image URLs or document image metadata.

An attacker who can control those inputs may be able to read local files accessible to the application process. Applications that do not use VLM image inputs, or that only pass trusted image references, are not affected.

## Patched Version

Upgrade to `langchain-nvidia-ai-endpoints >= 1.4.2`.

The patched version rejects raw local filesystem paths for VLM image inputs. Supported inputs are remote URLs, `data:image/...;base64,...` URIs, and supported asset/file IDs.

## Workarounds

If upgrading is not immediately possible, applications should reject local filesystem paths in user-controlled VLM image inputs and only allow trusted remote URLs, data URIs, or known safe asset/file IDs.

Applications should also run with least-privilege filesystem access so that the application process cannot read files it does not need.

## Which versions are affected by GHSA-g28h-2cmm-rj9x?

2 open source packages ship an affected version, including langchain-nvidia-ai-endpoints.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `langchain-nvidia-ai-endpoints` | PyPI | All versions | 1.4.2 |
| `langchain-nvidia-ai-endpoints` | PyPI | All versions | 1.4.2 |

## How do I fix GHSA-g28h-2cmm-rj9x?

Upgrade langchain-nvidia-ai-endpoints to 1.4.2 or later.

## Is GHSA-g28h-2cmm-rj9x being exploited?

There is no known exploitation of GHSA-g28h-2cmm-rj9x in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-g28h-2cmm-rj9x and fix it if it is affected.

What it is: GHSA-g28h-2cmm-rj9x is a path traversal vulnerability in langchain-nvidia-ai-endpoints, published on 24 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-g28h-2cmm-rj9x in the wild and no public exploit code.

Affected packages and fixed versions:
- langchain-nvidia-ai-endpoints (PyPI): affected all versions; fixed in 1.4.2
- langchain-nvidia-ai-endpoints (PyPI): affected all versions; fixed in 1.4.2

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/GHSA-g28h-2cmm-rj9x/ (Markdown: https://insights.sbomify.com/GHSA-g28h-2cmm-rj9x/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-g28h-2cmm-rj9x

---
From sbomify Insights: https://insights.sbomify.com/GHSA-g28h-2cmm-rj9x/
Summaries are generated and may contain mistakes; the official description above is the record.