How severe is GHSA-g28h-2cmm-rj9x?

GHSA-g28h-2cmm-rj9x has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-g28h-2cmm-rj9x?

GHSA-g28h-2cmm-rj9x affects the following packages: langchain-nvidia-ai-endpoints (PyPI). Ecosystems affected: PyPI.

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

Update langchain-nvidia-ai-endpoints to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g28h-2cmm-rj9x is resolved across your whole dependency graph.

How do I detect GHSA-g28h-2cmm-rj9x in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langchain-nvidia-ai-endpoints, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g28h-2cmm-rj9x if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is GHSA-g28h-2cmm-rj9x actively exploited in the wild?

No public exploit code has been indexed for GHSA-g28h-2cmm-rj9x yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-g28h-2cmm-rj9x published, and has it been updated?

GHSA-g28h-2cmm-rj9x was published on September 24, 2026 and was last updated on September 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

HIGH severity

langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputsGHSA-g28h-2cmm-rj9x

HIGHFix: langchain-ai/langchain-nvidia@b483c7c

GHSA-g28h-2cmm-rj9x is a high-severity (CVSS 7.5) vulnerability in langchain-nvidia-ai-endpoints. A fix is available for langchain-nvidia-ai-endpoints — see the affected versions and patch details below.

Published

Sep 24, 2026

Updated

Sep 24, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍langchain-nvidia-ai-endpoints

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`langchain-nvidia-ai-endpoints`	all versions	1.4.2`pip install --upgrade 'langchain-nvidia-ai-endpoints==1.4.2'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for langchain-nvidia-ai-endpoints, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update langchain-nvidia-ai-endpoints to 1.4.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g28h-2cmm-rj9x is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

## 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 attack

O3 Security · Impact-Aware SCA

Is GHSA-g28h-2cmm-rj9x in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works