{"id":"CVE-2025-68665","aliases":["GHSA-r399-636x-v7f6"],"summary":"LangChain serialization injection vulnerability enables secret extraction","published_at":"2025-12-23T20:08:48Z","modified_at":"2026-09-10T03:50:58.820101Z","products":[],"rating":{"severity":"high","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","attack_path":"internet_unauthenticated","user_interaction":false,"malicious":false,"red_hat":"Important","vendor_ratings":[{"source":"Red Hat","rating":"Important"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.007930000312626362,"percentile":0.5714100003242493,"date":"2026-11-19T00:00:00Z"},"priority":10.6,"details":"LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3","affected_stack":[],"affected_other":[{"ecosystem":"CVE","package":"langchain-ai/langchainjs","versions":["@langchain/core >= 1.0.0, < 1.1.8","@langchain/core < 0.3.80","langchain >= 1.0.0, < 1.2.3","langchain < 0.3.37"],"provider":"cvelistv5","source":"CVE-2025-68665","relation":"self"},{"ecosystem":"NVD","package":"langchain:langchain.js","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.37"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.2.3"}]}],"fixed":["0.3.37","1.2.3"],"provider":"nvd","source":"CVE-2025-68665","relation":"self"},{"ecosystem":"NVD","package":"langchain:langchain/core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.80"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.1.8"}]}],"fixed":["0.3.80","1.1.8"],"provider":"nvd","source":"CVE-2025-68665","relation":"self"},{"ecosystem":"npm","package":"@langchain/core","purl":"pkg:npm/%40langchain/core","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.3.80"}]}],"fixed":["0.3.80"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"},{"ecosystem":"npm","package":"@langchain/core","purl":"pkg:npm/%40langchain/core","ranges":[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"1.1.8"}]}],"fixed":["1.1.8"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"},{"ecosystem":"npm","package":"langchain","purl":"pkg:npm/langchain","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.3.37"}]}],"fixed":["0.3.37"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"},{"ecosystem":"npm","package":"langchain","purl":"pkg:npm/langchain","ranges":[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"1.2.3"}]}],"fixed":["1.2.3"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Lightspeed","cpe":"cpe:/a:redhat:openshift_lightspeed:1","status":"affected","packages":["openshift-lightspeed/lightspeed-service-api-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat Ansible Automation Platform 2","cpe":"cpe:/a:redhat:ansible_automation_platform:2","status":"affected","packages":["ansible-automation-platform-24/lightspeed-rhel8","ansible-automation-platform-26/lightspeed-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat Ansible Automation Platform 2","cpe":"cpe:/a:redhat:ansible_automation_platform:2","status":"not_affected","packages":["ansible-automation-platform-24/de-minimal-rhel8","ansible-automation-platform-24/de-minimal-rhel9","ansible-automation-platform-24/de-supported-rhel8","ansible-automation-platform-24/de-supported-rhel9","ansible-automation-platform-24/ee-minimal-rhel8","ansible-automation-platform-24/ee-minimal-rhel9","ansible-automation-platform-24/ee-supported-rhel8","ansible-automation-platform-24/ee-supported-rhel9","ansible-automation-platform-24/platform-resource-runner-rhel8","ansible-automation-platform-25/aap-cloud-metrics-collector-rhel8","ansible-automation-platform-25/ansible-dev-tools-rhel8","ansible-automation-platform-25/de-minimal-rhel8","ansible-automation-platform-25/de-minimal-rhel9","ansible-automation-platform-25/de-supported-rhel8","ansible-automation-platform-25/de-supported-rhel9","ansible-automation-platform-25/ee-cloud-services-rhel9","ansible-automation-platform-25/ee-minimal-rhel8","ansible-automation-platform-25/ee-minimal-rhel9","ansible-automation-platform-25/ee-supported-rhel8","ansible-automation-platform-25/ee-supported-rhel9","ansible-automation-platform-25/lightspeed-chatbot-rhel8","ansible-automation-platform-25/lightspeed-rhel8","ansible-automation-platform-25/platform-resource-runner-rhel8","ansible-automation-platform-26/ansible-dev-tools-rhel9","ansible-automation-platform-26/de-minimal-rhel9"],"package_count":34,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat Enterprise Linux AI (RHEL AI)","cpe":"cpe:/a:redhat:enterprise_linux_ai:1","status":"not_affected","packages":["rhelai1/bootc-amd-rhel9","rhelai1/bootc-aws-nvidia-rhel9","rhelai1/bootc-azure-amd-rhel9","rhelai1/bootc-azure-nvidia-rhel9","rhelai1/bootc-gcp-nvidia-rhel9","rhelai1/bootc-intel-rhel9","rhelai1/bootc-nvidia-rhel9","rhelai1/instructlab-amd-rhel9","rhelai1/instructlab-intel-rhel9","rhelai1/instructlab-nvidia-rhel9"],"package_count":10,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"not_affected","packages":["rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"component_not_present","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"fixed","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":["RHSA-2026:3713"],"provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"not_affected","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-68665"}],"records":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2025-2936","relation":"upstream","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-2936","license":"TLP:CLEAR, mirroring permitted","published_at":"2025-12-29T23:00:00Z","modified_at":"2026-03-03T23:00:00Z","summary":"LangChain: Mehrere Schwachstellen ermöglichen Offenlegung von Informationen","details":"Ein Angreifer kann mehrere Schwachstellen in LangChain ausnutzen, um Informationen offenzulegen.\n\nLangChain ist ein Open-Source-Framework, das die Entwicklung von Anwendungen mit großen Sprachmodellen (LLMs) erleichtert","severity":[{"type":"BSI","score":"hoch","source":"WID-SEC-W-2025-2936"}],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://wid.cert-bund.de/.well-known/csaf/white/2025/wid-sec-w-2025-2936.json"},{"type":"WEB","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-2936"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68664"},{"type":"WEB","url":"https://github.com/advisories/GHSA-c67j-w6g6-q2cm"},{"type":"WEB","url":"https://cyata.ai/blog/langgrinch-langchain-core-cve-2025-68664/"},{"type":"WEB","url":"https://github.com/Ak-cybe/CVE-2025-68664-LangGrinch-PoC"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68665"},{"type":"WEB","url":"https://security.snyk.io/vuln/SNYK-JS-LANGCHAINCORE-14563113"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:0406"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:0408"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:0409"},{"type":"WEB","url":"https://access.redhat.com/errata/RHSA-2026:3713"}]},{"provider":"cvelistv5","source_id":"CVE-2025-68665","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2025-68665","license":"CC-BY-4.0","published_at":"2025-12-23T22:56:04.837Z","modified_at":"2025-12-24T14:38:40.268Z","summary":"LangChain serialization injection vulnerability enables secret extraction","details":"LangChain is a framework for building LLM-powered applications. Prior to @langchain/core versions 0.3.80 and 1.1.8, and prior to langchain versions 0.3.37 and 1.2.3, a serialization injection vulnerability exists in LangChain JS's toJSON() method (and subsequently when string-ifying objects using JSON.stringify(). The method did not escape objects with 'lc' keys when serializing free-form data in kwargs. The 'lc' key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data. This issue has been patched in @langchain/core versions 0.3.80 and 1.1.8, and langchain versions 0.3.37 and 1.2.3","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","source":"CVE-2025-68665"}],"affected":[{"ecosystem":"CVE","package":"langchain-ai/langchainjs","versions":["@langchain/core >= 1.0.0, < 1.1.8","@langchain/core < 0.3.80","langchain >= 1.0.0, < 1.2.3","langchain < 0.3.37"],"provider":"cvelistv5","source":"CVE-2025-68665","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-r399-636x-v7f6"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/commit/e5063f9c6e9989ea067dfdff39262b9e7b6aba62"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcore%401.1.8"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/langchain%401.2.3"}]},{"provider":"nvd","source_id":"CVE-2025-68665","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68665","severity":[],"affected":[{"ecosystem":"NVD","package":"langchain:langchain.js","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.37"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.2.3"}]}],"fixed":["0.3.37","1.2.3"],"provider":"nvd","source":"CVE-2025-68665","relation":"self"},{"ecosystem":"NVD","package":"langchain:langchain/core","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.3.80"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.0.0"},{"fixed":"1.1.8"}]}],"fixed":["0.3.80","1.1.8"],"provider":"nvd","source":"CVE-2025-68665","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"GHSA-r399-636x-v7f6","relation":"self","url":"https://osv.dev/vulnerability/GHSA-r399-636x-v7f6","license":"CC-BY-4.0","published_at":"2025-12-23T20:08:48Z","modified_at":"2026-09-10T03:50:58.820101Z","summary":"LangChain serialization injection vulnerability enables secret extraction","details":"## Context\n\nA serialization injection vulnerability exists in LangChain JS's `toJSON()` method (and subsequently when string-ifying objects using `JSON.stringify()`. The method did not escape objects with `'lc'` keys when serializing free-form data in kwargs. The `'lc'` key is used internally by LangChain to mark serialized objects. When user-controlled data contains this key structure, it is treated as a legitimate LangChain object during deserialization rather than plain user data.\n\n### Attack surface\n\nThe core vulnerability was in `Serializable.toJSON()`: this method failed to escape user-controlled objects containing `'lc'` keys within kwargs (e.g., `additional_kwargs`, `metadata`, `response_metadata`). When this unescaped data was later deserialized via `load()`, the injected structures were treated as legitimate LangChain objects rather than plain user data.\n\nThis escaping bug enabled several attack vectors:\n\n1. **Injection via user data**: Malicious LangChain object structures could be injected through user-controlled fields like `metadata`, `additional_kwargs`, or `response_metadata`\n2. **Secret extraction**: Injected secret structures could extract environment variables when `secretsFromEnv` was enabled (which had no explicit default, effectively defaulting to `true` behavior)\n3. **Class instantiation via import maps**: Injected constructor structures could instantiate any class available in the provided import maps with attacker-controlled parameters\n\n**Note on import maps:** Classes must be explicitly included in import maps to be instantiatable. The core import map includes standard types (messages, prompts, documents), and users can extend this via `importMap` and `optionalImportsMap` options. This architecture naturally limits the attack surface—an `allowedObjects` parameter is not necessary because users control which classes are available through the import maps they provide.\n\n**Security hardening:** This patch fixes the escaping bug in `toJSON()` and introduces new restrictive defaults in `load()`: `secretsFromEnv` now explicitly defaults to `false`, and a `maxDepth` parameter protects against DoS via deeply nested structures. JSDoc security warnings have been added to all import map options.\n\n## Who is affected?\n\nApplications are vulnerable if they:\n\n1. **Serialize untrusted data via `JSON.stringify()` on Serializable objects, then deserialize with `load()`** — Trusting your own serialization output makes you vulnerable if user-controlled data (e.g., from LLM responses, metadata fields, or user inputs) contains `'lc'` key structures.\n2. **Deserialize untrusted data with `load()`** — Directly deserializing untrusted data that may contain injected `'lc'` structures.\n3. **Use LangGraph checkpoints** — Checkpoint serialization/deserialization paths may be affected.\n\nThe most common attack vector is through **LLM response fields** like `additional_kwargs` or `response_metadata`, which can be controlled via prompt injection and then serialized/deserialized in streaming operations.\n\n## Impact\n\nAttackers who control serialized data can extract environment variable secrets by injecting `{\"lc\": 1, \"type\": \"secret\", \"id\": [\"ENV_VAR\"]}` to load environment variables during deserialization (when `secretsFromEnv: true`). They can also instantiate classes with controlled parameters by injecting constructor structures to instantiate any class within the provided import maps with attacker-controlled parameters, potentially triggering side effects such as network calls or file operations.\n\nKey severity factors:\n\n- Affects the serialization path—applications trusting their own serialization output are vulnerable\n- Enables secret extraction when combined with `secretsFromEnv: true`\n- LLM responses in `additional_kwargs` can be controlled via prompt injection\n\n## Exploit example\n\n```typescript\nimport { load } from \"@langchain/core/load\";\n\n// Attacker injects secret structure into user-controlled data\nconst attackerPayload = JSON.stringify({\n  user_data: {\n    lc: 1,\n    type: \"secret\",\n    id: [\"OPENAI_API_KEY\"],\n  },\n});\n\nprocess.env.OPENAI_API_KEY = \"sk-secret-key-12345\";\n\n// With secretsFromEnv: true, the secret is extracted\nconst deserialized = await load(attackerPayload, { secretsFromEnv: true });\n\nconsole.log(deserialized.user_data); // \"sk-secret-key-12345\" - SECRET LEAKED!\n```\n\n## Security hardening changes\n\nThis patch introduces the following changes to `load()`:\n\n1. **`secretsFromEnv` default changed to `false`**: Disables automatic secret loading from environment variables. Secrets not found in `secretsMap` now throw an error instead of being loaded from `process.env`. This fail-safe behavior ensures missing secrets are caught immediately rather than silently continuing with `null`.\n2. **New `maxDepth` parameter** (defaults to `50`): Protects against denial-of-service attacks via deeply nested JSON structures that could cause stack overflow.\n3. **Escape mechanism in `toJSON()`**: User-controlled objects containing `'lc'` keys are now wrapped in `{\"__lc_escaped__\": {...}}` during serialization and unwrapped as plain data during deserialization.\n4. **JSDoc security warnings**: All import map options (`importMap`, `optionalImportsMap`, `optionalImportEntrypoints`) now include security warnings about never populating them from user input.\n\n## Migration guide\n\n### No changes needed for most users\n\nIf you're deserializing standard LangChain types (messages, documents, prompts) using the core import map, your code will work without changes:\n\n```typescript\nimport { load } from \"@langchain/core/load\";\n\n// Works with default settings\nconst obj = await load(serializedData);\n```\n\n### For secrets from environment\n\n`secretsFromEnv` now defaults to `false`, and missing secrets throw an error. If you need to load secrets:\n\n```typescript\nimport { load } from \"@langchain/core/load\";\n\n// Provide secrets explicitly (recommended)\nconst obj = await load(serializedData, {\n  secretsMap: { OPENAI_API_KEY: process.env.OPENAI_API_KEY },\n});\n\n// Or explicitly opt-in to load from env (only use with trusted data)\nconst obj = await load(serializedData, { secretsFromEnv: true });\n```\n\n> **Warning:** Only enable `secretsFromEnv` if you trust the serialized data. Untrusted data could extract any environment variable.\n\n> **Note:** If a secret reference is encountered but not found in `secretsMap` (and `secretsFromEnv` is `false` or the secret is not in the environment), an error is thrown. This fail-safe behavior ensures you're aware of missing secrets rather than silently receiving `null` values.\n\n### For deeply nested structures\n\nIf you have legitimate deeply nested data that exceeds the default depth limit of 50:\n\n```typescript\nimport { load } from \"@langchain/core/load\";\n\nconst obj = await load(serializedData, { maxDepth: 100 });\n```\n\n### For custom import maps\n\nIf you provide custom import maps, ensure they only contain trusted modules:\n\n```typescript\nimport { load } from \"@langchain/core/load\";\nimport * as myModule from \"./my-trusted-module\";\n\n// GOOD - explicitly include only trusted modules\nconst obj = await load(serializedData, {\n  importMap: { my_module: myModule },\n});\n\n// BAD - never populate from user input\nconst obj = await load(serializedData, {\n  importMap: userProvidedImports, // DANGEROUS!\n});\n```","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","source":"GHSA-r399-636x-v7f6"}],"affected":[{"ecosystem":"npm","package":"@langchain/core","purl":"pkg:npm/%40langchain/core","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.3.80"}]}],"fixed":["0.3.80"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"},{"ecosystem":"npm","package":"@langchain/core","purl":"pkg:npm/%40langchain/core","ranges":[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"1.1.8"}]}],"fixed":["1.1.8"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"},{"ecosystem":"npm","package":"langchain","purl":"pkg:npm/langchain","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.3.37"}]}],"fixed":["0.3.37"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"},{"ecosystem":"npm","package":"langchain","purl":"pkg:npm/langchain","ranges":[{"type":"SEMVER","events":[{"introduced":"1.0.0"},{"fixed":"1.2.3"}]}],"fixed":["1.2.3"],"provider":"osv","source":"GHSA-r399-636x-v7f6","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-r399-636x-v7f6"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68665"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/commit/e5063f9c6e9989ea067dfdff39262b9e7b6aba62"},{"type":"PACKAGE","url":"https://github.com/langchain-ai/langchainjs"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcore%401.1.8"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/langchain%401.2.3"}]},{"provider":"redhat-vex","source_id":"CVE-2025-68665","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2025-68665","license":"CC-BY-4.0","published_at":"2025-12-23T22:56:04.837Z","modified_at":"2026-08-10T11:00:52.758843Z","summary":"langchain-core: LangChain: Arbitrary Code Execution via Serialization Injection","details":"A flaw was found in LangChain. A remote attacker could exploit a serialization injection vulnerability in the `toJSON()` method. This occurs because the method fails to properly escape objects containing 'lc' keys during serialization of free-form data. When user-controlled data includes this key structure, it is incorrectly processed as a legitimate LangChain object during deserialization, which could lead to arbitrary code execution.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","source":"CVE-2025-68665"},{"type":"Red Hat","score":"Important","source":"CVE-2025-68665"}],"affected":[],"product_status":[{"vendor":"Red Hat","product":"OpenShift Lightspeed","cpe":"cpe:/a:redhat:openshift_lightspeed:1","status":"affected","packages":["openshift-lightspeed/lightspeed-service-api-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat Ansible Automation Platform 2","cpe":"cpe:/a:redhat:ansible_automation_platform:2","status":"affected","packages":["ansible-automation-platform-24/lightspeed-rhel8","ansible-automation-platform-26/lightspeed-rhel9"],"package_count":2,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat Ansible Automation Platform 2","cpe":"cpe:/a:redhat:ansible_automation_platform:2","status":"not_affected","packages":["ansible-automation-platform-24/de-minimal-rhel8","ansible-automation-platform-24/de-minimal-rhel9","ansible-automation-platform-24/de-supported-rhel8","ansible-automation-platform-24/de-supported-rhel9","ansible-automation-platform-24/ee-minimal-rhel8","ansible-automation-platform-24/ee-minimal-rhel9","ansible-automation-platform-24/ee-supported-rhel8","ansible-automation-platform-24/ee-supported-rhel9","ansible-automation-platform-24/platform-resource-runner-rhel8","ansible-automation-platform-25/aap-cloud-metrics-collector-rhel8","ansible-automation-platform-25/ansible-dev-tools-rhel8","ansible-automation-platform-25/de-minimal-rhel8","ansible-automation-platform-25/de-minimal-rhel9","ansible-automation-platform-25/de-supported-rhel8","ansible-automation-platform-25/de-supported-rhel9","ansible-automation-platform-25/ee-cloud-services-rhel9","ansible-automation-platform-25/ee-minimal-rhel8","ansible-automation-platform-25/ee-minimal-rhel9","ansible-automation-platform-25/ee-supported-rhel8","ansible-automation-platform-25/ee-supported-rhel9","ansible-automation-platform-25/lightspeed-chatbot-rhel8","ansible-automation-platform-25/lightspeed-rhel8","ansible-automation-platform-25/platform-resource-runner-rhel8","ansible-automation-platform-26/ansible-dev-tools-rhel9","ansible-automation-platform-26/de-minimal-rhel9"],"package_count":34,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat Enterprise Linux AI (RHEL AI)","cpe":"cpe:/a:redhat:enterprise_linux_ai:1","status":"not_affected","packages":["rhelai1/bootc-amd-rhel9","rhelai1/bootc-aws-nvidia-rhel9","rhelai1/bootc-azure-amd-rhel9","rhelai1/bootc-azure-nvidia-rhel9","rhelai1/bootc-gcp-nvidia-rhel9","rhelai1/bootc-intel-rhel9","rhelai1/bootc-nvidia-rhel9","rhelai1/instructlab-amd-rhel9","rhelai1/instructlab-intel-rhel9","rhelai1/instructlab-nvidia-rhel9"],"package_count":10,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI (RHOAI)","cpe":"cpe:/a:redhat:openshift_ai","status":"not_affected","packages":["rhoai/odh-trustyai-ragas-lls-provider-dsp-rhel9"],"package_count":1,"fixed":[],"advisories":[],"note":"component_not_present","provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"fixed","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":["RHSA-2026:3713"],"provider":"redhat-vex","source":"CVE-2025-68665"},{"vendor":"Red Hat","product":"Red Hat OpenShift AI 3.3","cpe":"cpe:/a:redhat:openshift_ai:3.3::el9","status":"not_affected","packages":["rhoai"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2025-68665"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-68665.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2025-68665"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424797"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2025-68665"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68665"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/commit/e5063f9c6e9989ea067dfdff39262b9e7b6aba62"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcore%401.1.8"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/langchain%401.2.3"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-r399-636x-v7f6"}]}],"references":[{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/security/advisories/GHSA-r399-636x-v7f6"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/commit/e5063f9c6e9989ea067dfdff39262b9e7b6aba62"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/%40langchain%2Fcore%401.1.8"},{"type":"WEB","url":"https://github.com/langchain-ai/langchainjs/releases/tag/langchain%401.2.3"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68665"},{"type":"PACKAGE","url":"https://github.com/langchain-ai/langchainjs"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2025/cve-2025-68665.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2025-68665"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2424797"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2025-68665"}],"sources":[{"provider":"csaf-bsi","source_id":"WID-SEC-W-2025-2936","url":"https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2025-2936","license":"TLP:CLEAR, mirroring permitted","modified_at":"2026-03-03T23:00:00Z","relation":"upstream"},{"provider":"cvelistv5","source_id":"CVE-2025-68665","url":"https://www.cve.org/CVERecord?id=CVE-2025-68665","license":"CC-BY-4.0","modified_at":"2025-12-24T14:38:40.268Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2025-68665","url":"https://nvd.nist.gov/vuln/detail/CVE-2025-68665","relation":"self"},{"provider":"osv","source_id":"GHSA-r399-636x-v7f6","url":"https://osv.dev/vulnerability/GHSA-r399-636x-v7f6","license":"CC-BY-4.0","modified_at":"2026-09-10T03:50:58.820101Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2025-68665","url":"https://access.redhat.com/security/cve/CVE-2025-68665","license":"CC-BY-4.0","modified_at":"2026-08-10T11:00:52.758843Z","relation":"self"}]}
