GHSA-G28H-2CMM-RJ9X

Vulnerability from github – Published: 2026-09-24 19:25 – Updated: 2026-09-24 19:25
VLAI
Summary
langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputs
Details

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.

Severity
7.5 (High)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Show details on source website
To clipboard 

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 1.4.1"
      },
      "package": {
        "ecosystem": "PyPI",
        "name": "langchain-nvidia-ai-endpoints"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "1.4.2"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [],
  "database_specific": {
    "cwe_ids": [
      "CWE-22"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-09-24T19:25:36Z",
    "nvd_published_at": null,
    "severity": "HIGH"
  },
  "details": "## Summary\n\n`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.\n\n## Impact\n\nApplications are affected if they use VLM image inputs with `ChatNVIDIA` or `NVIDIARerank` and allow untrusted users to control image URLs or document image metadata.\n\nAn 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.\n\n## Patched Version\n\nUpgrade to `langchain-nvidia-ai-endpoints \u003e= 1.4.2`.\n\nThe 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.\n\n## Workarounds\n\nIf 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.\n\nApplications should also run with least-privilege filesystem access so that the application process cannot read files it does not need.",
  "id": "GHSA-g28h-2cmm-rj9x",
  "modified": "2026-09-24T19:25:36Z",
  "published": "2026-09-24T19:25:36Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/langchain-ai/langchain-nvidia/security/advisories/GHSA-g28h-2cmm-rj9x"
    },
    {
      "type": "WEB",
      "url": "https://github.com/langchain-ai/langchain-nvidia/commit/b483c7cad07dd9d5fd0fee2668238c4a08825d86"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/langchain-ai/langchain-nvidia"
    },
    {
      "type": "WEB",
      "url": "https://github.com/langchain-ai/langchain-nvidia/releases/tag/libs%2Fai-endpoints%2Fv1.4.2"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "langchain-nvidia-ai-endpoints has local file disclosure through VLM image inputs"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.



Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.