GHSA-g28h-2cmm-rj9x
langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputs
GHSA-g28h-2cmm-rj9x is a high vulnerability (CVSS 7.5) in langchain-nvidia-ai-endpoints, published September 24, 2026. No source lists public exploit code. Fixed in langchain-nvidia-ai-endpoints 1.4.2.
- Severity
- 7.5 HighCVSS 3.1, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
1.4.2langchain-nvidia-ai-endpoints +1 more
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Affected packages
| Package | Affected | Fixed |
|---|---|---|
langchain-nvidia-ai-endpointsPyPI | through 1.4.1 | 1.4.2 |
langchain-nvidia-ai-endpointsPyPI | before 1.4.2, plus listed versions 0.0.10.0.100.0.110.0.120.0.13 Show 45 moreShow less0.0.140.0.150.0.160.0.170.0.180.0.190.0.20.0.200.0.30.0.40.0.4rc10.0.50.0.5rc00.0.60.0.70.0.80.0.90.1.00.1.10.1.20.1.30.1.40.1.50.1.60.1.70.2.00.2.10.2.20.3.00.3.10.3.100.3.110.3.120.3.130.3.140.3.150.3.160.3.170.3.180.3.190.3.20.3.30.3.40.3.50.3.6 | 1.4.2 |
What each source reports
GitHub Advisories Score used
langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputs
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.
- Record
GHSA-g28h-2cmm-rj9x- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
OSV
langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputs
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.
- Record
GHSA-g28h-2cmm-rj9x- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Weakness
- CWE-22
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
References
github.com/langchain-ai/langchain-nvidia/security/advisories/GHSA-g28h-2cmm-rj9x
Left out here: 14 versions. The JSON record has them.