Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-40190 (GCVE-0-2026-40190)
Vulnerability from cvelistv5 – Published: 2026-04-10 19:47 – Updated: 2026-04-13 16:13- CWE-1321 - Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
| URL | Tags |
|---|---|
| https://github.com/langchain-ai/langsmith-sdk/sec… | x_refsource_CONFIRM |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| langchain-ai | langsmith-sdk |
Affected:
< 0.5.18
|
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-40190",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-04-13T16:13:33.168377Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-04-13T16:13:45.532Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "langsmith-sdk",
"vendor": "langchain-ai",
"versions": [
{
"status": "affected",
"version": "\u003c 0.5.18"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. Prior to 0.5.18, the LangSmith JavaScript/TypeScript SDK (langsmith) contains an incomplete prototype pollution fix in its internally vendored lodash set() utility. The baseAssignValue() function only guards against the __proto__ key, but fails to prevent traversal via constructor.prototype. This allows an attacker who controls keys in data processed by the createAnonymizer() API to pollute Object.prototype, affecting all objects in the Node.js process. This vulnerability is fixed in 0.5.18."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.6,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-1321",
"description": "CWE-1321: Improperly Controlled Modification of Object Prototype Attributes (\u0027Prototype Pollution\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-04-10T19:47:57.642Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252"
}
],
"source": {
"advisory": "GHSA-fw9q-39r9-c252",
"discovery": "UNKNOWN"
},
"title": "LangSmith Client SDKs has Prototype Pollution in langsmith-sdk via Incomplete `__proto__` Guard in Internal lodash `set()`"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-40190",
"datePublished": "2026-04-10T19:47:57.642Z",
"dateReserved": "2026-04-09T20:59:17.620Z",
"dateUpdated": "2026-04-13T16:13:45.532Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-40190",
"date": "2026-09-11",
"epss": "0.00313",
"percentile": "0.23994"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-40190\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-04-10T20:16:24.043\",\"lastModified\":\"2026-07-07T18:33:24.723\",\"vulnStatus\":\"Analyzed\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. Prior to 0.5.18, the LangSmith JavaScript/TypeScript SDK (langsmith) contains an incomplete prototype pollution fix in its internally vendored lodash set() utility. The baseAssignValue() function only guards against the __proto__ key, but fails to prevent traversal via constructor.prototype. This allows an attacker who controls keys in data processed by the createAnonymizer() API to pollute Object.prototype, affecting all objects in the Node.js process. This vulnerability is fixed in 0.5.18.\"}],\"affected\":[{\"source\":\"security-advisories@github.com\",\"affectedData\":[{\"vendor\":\"langchain-ai\",\"product\":\"langsmith-sdk\",\"versions\":[{\"version\":\"\u003c 0.5.18\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L\",\"baseScore\":5.6,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.2,\"impactScore\":3.4},{\"source\":\"nvd@nist.gov\",\"type\":\"Primary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H\",\"baseScore\":9.8,\"baseSeverity\":\"CRITICAL\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"HIGH\",\"integrityImpact\":\"HIGH\",\"availabilityImpact\":\"HIGH\"},\"exploitabilityScore\":3.9,\"impactScore\":5.9}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-04-13T16:13:33.168377Z\",\"id\":\"CVE-2026-40190\",\"options\":[{\"exploitation\":\"poc\"},{\"automatable\":\"no\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-1321\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:langchain:langsmith:*:*:*:*:*:node.js:*:*\",\"versionEndExcluding\":\"0.5.18\",\"matchCriteriaId\":\"7304E366-AE7C-45DB-BD8A-77742DB3B235\"}]}]}],\"references\":[{\"url\":\"https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252\",\"source\":\"security-advisories@github.com\",\"tags\":[\"Exploit\",\"Vendor Advisory\",\"Mitigation\"]}]}}",
"redhat_vex": {
"current_release_date": "2026-04-13T19:23:53+00:00",
"cve": "CVE-2026-40190",
"id": "CVE-2026-40190",
"initial_release_date": "2026-01-01T00:00:00+00:00",
"product_status:known_not_affected": "1",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "LangSmith Client SDKs has Prototype Pollution in langsmith-sdk via Incomplete `__proto__` Guard in Internal lodash `set()`",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40190.json",
"version": "3"
},
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-40190\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-04-13T16:13:33.168377Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-04-13T16:13:41.123Z\"}}], \"cna\": {\"title\": \"LangSmith Client SDKs has Prototype Pollution in langsmith-sdk via Incomplete `__proto__` Guard in Internal lodash `set()`\", \"source\": {\"advisory\": \"GHSA-fw9q-39r9-c252\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.6, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L\", \"integrityImpact\": \"LOW\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"LOW\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"LOW\"}}], \"affected\": [{\"vendor\": \"langchain-ai\", \"product\": \"langsmith-sdk\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003c 0.5.18\"}]}], \"references\": [{\"url\": \"https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252\", \"name\": \"https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252\", \"tags\": [\"x_refsource_CONFIRM\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. Prior to 0.5.18, the LangSmith JavaScript/TypeScript SDK (langsmith) contains an incomplete prototype pollution fix in its internally vendored lodash set() utility. The baseAssignValue() function only guards against the __proto__ key, but fails to prevent traversal via constructor.prototype. This allows an attacker who controls keys in data processed by the createAnonymizer() API to pollute Object.prototype, affecting all objects in the Node.js process. This vulnerability is fixed in 0.5.18.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-1321\", \"description\": \"CWE-1321: Improperly Controlled Modification of Object Prototype Attributes (\u0027Prototype Pollution\u0027)\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-04-10T19:47:57.642Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-40190\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-04-13T16:13:45.532Z\", \"dateReserved\": \"2026-04-09T20:59:17.620Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-04-10T19:47:57.642Z\", \"assignerShortName\": \"GitHub_M\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
FKIE_CVE-2026-40190
Vulnerability from fkie_nvd - Published: 2026-04-10 20:16 - Updated: 2026-07-07 18:339.8 (Critical) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252 | Exploit, Vendor Advisory, Mitigation |
{
"affected": [
{
"affectedData": [
{
"product": "langsmith-sdk",
"vendor": "langchain-ai",
"versions": [
{
"status": "affected",
"version": "\u003c 0.5.18"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:langchain:langsmith:*:*:*:*:*:node.js:*:*",
"matchCriteriaId": "7304E366-AE7C-45DB-BD8A-77742DB3B235",
"versionEndExcluding": "0.5.18",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. Prior to 0.5.18, the LangSmith JavaScript/TypeScript SDK (langsmith) contains an incomplete prototype pollution fix in its internally vendored lodash set() utility. The baseAssignValue() function only guards against the __proto__ key, but fails to prevent traversal via constructor.prototype. This allows an attacker who controls keys in data processed by the createAnonymizer() API to pollute Object.prototype, affecting all objects in the Node.js process. This vulnerability is fixed in 0.5.18."
}
],
"id": "CVE-2026-40190",
"lastModified": "2026-07-07T18:33:24.723",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "HIGH",
"attackVector": "NETWORK",
"availabilityImpact": "LOW",
"baseScore": 5.6,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"version": "3.1"
},
"exploitabilityScore": 2.2,
"impactScore": 3.4,
"source": "security-advisories@github.com",
"type": "Secondary"
},
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 9.8,
"baseSeverity": "CRITICAL",
"confidentialityImpact": "HIGH",
"integrityImpact": "HIGH",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 5.9,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-40190",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-04-13T16:13:33.168377Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-04-10T20:16:24.043",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Vendor Advisory",
"Mitigation"
],
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-1321"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
GHSA-FW9Q-39R9-C252
Vulnerability from github – Published: 2026-04-10 20:18 – Updated: 2026-04-10 21:37GHSA-fw9q-39r9-c252: Prototype Pollution via Incomplete Lodash set() Guard in langsmith-sdk
Severity: Medium (CVSS ~5.6) Status: Fixed in 0.5.18
Summary
The LangSmith JavaScript/TypeScript SDK (langsmith) contains an incomplete prototype pollution fix in its internally vendored lodash set() utility. The baseAssignValue() function only guards against the __proto__ key, but fails to prevent traversal via constructor.prototype. This allows an attacker who controls keys in data processed by the createAnonymizer() API to pollute Object.prototype, affecting all objects in the Node.js process.
Affected Products
| Product | Affected Versions | Component |
|---|---|---|
langsmith (npm) |
<= 0.5.17 | js/src/utils/lodash/baseAssignValue.ts, js/src/anonymizer/index.ts |
| langchain-ai/langsmith-sdk | GitHub main branch (as of 2026-03-24) | JS/TypeScript SDK |
Not affected: The Python SDK (langsmith on PyPI) does not use lodash or an equivalent pattern.
Root Cause
The SDK vendors an internal copy of lodash's set() function at js/src/utils/lodash/. The baseAssignValue() function at baseAssignValue.ts:11 implements a guard for prototype pollution:
function baseAssignValue(object: Record<string, any>, key: string, value: any) {
if (key === "__proto__") {
Object.defineProperty(object, key, {
configurable: true, enumerable: true, value: value, writable: true,
});
} else {
object[key] = value; // ← No guard for "constructor" or "prototype" keys
}
}
This blocks __proto__ pollution but does not block the constructor.prototype traversal path. When set() is called with a path like "constructor.prototype.polluted":
castPath()splits it into["constructor", "prototype", "polluted"]baseSet()iterates:obj.constructor→Object→Object.prototypeassignValue(Object.prototype, "polluted", value)callsbaseAssignValue()- Key is
"polluted"(not"__proto__"), so the guard is bypassed Object.prototype.polluted = value— all objects are polluted
Attack Vector via Anonymizer
The createAnonymizer() API (importable as langsmith/anonymizer) processes data by:
- Extracting string nodes —
extractStringNodes()walks an object recursively and builds dotted paths from keys - Applying regex replacements — If a string value matches a configured pattern, the node is marked for update (
anonymizer/index.ts:95) - Writing back with
set()—set(mutateValue, node.path, node.value)writes the replaced value back (anonymizer/index.ts:123)
An attacker who controls keys in data being anonymized can construct a nested object where the path resolves to constructor.prototype.X:
{
wrapper: {
"constructor.prototype.isAdmin": "contains-secret-pattern"
}
}
extractStringNodes() produces path "wrapper.constructor.prototype.isAdmin". When the replacement triggers and set() writes back, it traverses up to Object.prototype.
Although createAnonymizer() uses deepClone() at anonymizer/index.ts:62 (JSON.parse(JSON.stringify(data))), the prototype chain traversal escapes the clone boundary because clone.wrapper.constructor resolves to the global Object constructor, not a cloned copy.
Proof of Concept
import { createAnonymizer } from "langsmith/anonymizer";
const anonymizer = createAnonymizer([
{ pattern: "secret", replace: "[REDACTED]" }
]);
console.log("BEFORE:", ({}).isAdmin); // undefined
const maliciousInput = {
wrapper: {
"constructor.prototype.isAdmin": "this-is-secret-data"
}
};
anonymizer(maliciousInput);
console.log("AFTER:", ({}).isAdmin); // "this-is-[REDACTED]-data"
console.log("Array:", [].isAdmin); // "this-is-[REDACTED]-data"
function checkAccess(user) {
if (user.isAdmin) return "ACCESS GRANTED";
return "ACCESS DENIED";
}
console.log(checkAccess({ name: "bob" })); // "ACCESS GRANTED" ← BYPASSED
Impact
Prototype pollution in a Node.js process can enable:
- Authentication bypass —
if (user.isAdmin)checks succeed on all objects - Remote Code Execution — Exploitable in template engines (Pug, EJS, Handlebars, Nunjucks) via polluted prototype properties that reach
eval()/Function()sinks - Denial of Service — Overwriting
toString,valueOf, orhasOwnPropertyon all objects - Data exfiltration — Polluting serialization methods to inject attacker-controlled values
Remediation
In baseAssignValue.ts, extend the guard to cover constructor and prototype keys:
function baseAssignValue(object, key, value) {
if (key === "__proto__" || key === "constructor" || key === "prototype") {
Object.defineProperty(object, key, {
configurable: true, enumerable: true, value, writable: true,
});
} else {
object[key] = value;
}
}
As defense in depth, extractStringNodes() in anonymizer/index.ts should also sanitize or reject path segments matching constructor or prototype before passing them to set().
Timeline
| Date | Event |
|---|---|
| 2026-03-24 | Initial report submitted |
| 2026-04-09 | Vendor confirmed; fixed in 0.5.18 |
Credits
Reported by: OneThing4101
{
"affected": [
{
"database_specific": {
"last_known_affected_version_range": "\u003c= 0.5.17"
},
"package": {
"ecosystem": "npm",
"name": "langsmith"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.5.18"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-40190"
],
"database_specific": {
"cwe_ids": [
"CWE-1321"
],
"github_reviewed": true,
"github_reviewed_at": "2026-04-10T20:18:02Z",
"nvd_published_at": "2026-04-10T20:16:24Z",
"severity": "MODERATE"
},
"details": "# GHSA-fw9q-39r9-c252: Prototype Pollution via Incomplete Lodash `set()` Guard in `langsmith-sdk`\n\n**Severity:** Medium (CVSS ~5.6)\n**Status:** Fixed in 0.5.18\n\n---\n\n## Summary\n\nThe LangSmith JavaScript/TypeScript SDK (`langsmith`) contains an incomplete prototype pollution fix in its internally vendored lodash `set()` utility. The `baseAssignValue()` function only guards against the `__proto__` key, but fails to prevent traversal via `constructor.prototype`. This allows an attacker who controls keys in data processed by the `createAnonymizer()` API to pollute `Object.prototype`, affecting all objects in the Node.js process.\n\n---\n\n## Affected Products\n\n| Product | Affected Versions | Component |\n|---------|-------------------|-----------|\n| `langsmith` (npm) | \u003c= 0.5.17 | `js/src/utils/lodash/baseAssignValue.ts`, `js/src/anonymizer/index.ts` |\n| langchain-ai/langsmith-sdk | GitHub main branch (as of 2026-03-24) | JS/TypeScript SDK |\n\n**Not affected:** The Python SDK (`langsmith` on PyPI) does not use lodash or an equivalent pattern.\n\n---\n\n## Root Cause\n\nThe SDK vendors an internal copy of lodash\u0027s `set()` function at `js/src/utils/lodash/`. The `baseAssignValue()` function at `baseAssignValue.ts:11` implements a guard for prototype pollution:\n\n```typescript\nfunction baseAssignValue(object: Record\u003cstring, any\u003e, key: string, value: any) {\n if (key === \"__proto__\") {\n Object.defineProperty(object, key, {\n configurable: true, enumerable: true, value: value, writable: true,\n });\n } else {\n object[key] = value; // \u2190 No guard for \"constructor\" or \"prototype\" keys\n }\n}\n```\n\nThis blocks `__proto__` pollution but does **not** block the `constructor.prototype` traversal path. When `set()` is called with a path like `\"constructor.prototype.polluted\"`:\n\n1. `castPath()` splits it into `[\"constructor\", \"prototype\", \"polluted\"]`\n2. `baseSet()` iterates: `obj.constructor` \u2192 `Object` \u2192 `Object.prototype`\n3. `assignValue(Object.prototype, \"polluted\", value)` calls `baseAssignValue()`\n4. Key is `\"polluted\"` (not `\"__proto__\"`), so the guard is bypassed\n5. `Object.prototype.polluted = value` \u2014 all objects are polluted\n\n---\n\n## Attack Vector via Anonymizer\n\nThe `createAnonymizer()` API (importable as `langsmith/anonymizer`) processes data by:\n\n1. **Extracting string nodes** \u2014 `extractStringNodes()` walks an object recursively and builds dotted paths from keys\n2. **Applying regex replacements** \u2014 If a string value matches a configured pattern, the node is marked for update (`anonymizer/index.ts:95`)\n3. **Writing back with `set()`** \u2014 `set(mutateValue, node.path, node.value)` writes the replaced value back (`anonymizer/index.ts:123`)\n\nAn attacker who controls keys in data being anonymized can construct a nested object where the path resolves to `constructor.prototype.X`:\n\n```javascript\n{\n wrapper: {\n \"constructor.prototype.isAdmin\": \"contains-secret-pattern\"\n }\n}\n```\n\n`extractStringNodes()` produces path `\"wrapper.constructor.prototype.isAdmin\"`. When the replacement triggers and `set()` writes back, it traverses up to `Object.prototype`.\n\nAlthough `createAnonymizer()` uses `deepClone()` at `anonymizer/index.ts:62` (`JSON.parse(JSON.stringify(data))`), the prototype chain traversal escapes the clone boundary because `clone.wrapper.constructor` resolves to the global `Object` constructor, not a cloned copy.\n\n---\n\n## Proof of Concept\n\n```javascript\nimport { createAnonymizer } from \"langsmith/anonymizer\";\n\nconst anonymizer = createAnonymizer([\n { pattern: \"secret\", replace: \"[REDACTED]\" }\n]);\n\nconsole.log(\"BEFORE:\", ({}).isAdmin); // undefined\n\nconst maliciousInput = {\n wrapper: {\n \"constructor.prototype.isAdmin\": \"this-is-secret-data\"\n }\n};\n\nanonymizer(maliciousInput);\n\nconsole.log(\"AFTER:\", ({}).isAdmin); // \"this-is-[REDACTED]-data\"\nconsole.log(\"Array:\", [].isAdmin); // \"this-is-[REDACTED]-data\"\n\nfunction checkAccess(user) {\n if (user.isAdmin) return \"ACCESS GRANTED\";\n return \"ACCESS DENIED\";\n}\nconsole.log(checkAccess({ name: \"bob\" })); // \"ACCESS GRANTED\" \u2190 BYPASSED\n```\n\n---\n\n## Impact\n\nPrototype pollution in a Node.js process can enable:\n\n1. **Authentication bypass** \u2014 `if (user.isAdmin)` checks succeed on all objects\n2. **Remote Code Execution** \u2014 Exploitable in template engines (Pug, EJS, Handlebars, Nunjucks) via polluted prototype properties that reach `eval()`/`Function()` sinks\n3. **Denial of Service** \u2014 Overwriting `toString`, `valueOf`, or `hasOwnProperty` on all objects\n4. **Data exfiltration** \u2014 Polluting serialization methods to inject attacker-controlled values\n\n---\n\n## Remediation\n\nIn `baseAssignValue.ts`, extend the guard to cover `constructor` and `prototype` keys:\n\n```typescript\nfunction baseAssignValue(object, key, value) {\n if (key === \"__proto__\" || key === \"constructor\" || key === \"prototype\") {\n Object.defineProperty(object, key, {\n configurable: true, enumerable: true, value, writable: true,\n });\n } else {\n object[key] = value;\n }\n}\n```\n\nAs defense in depth, `extractStringNodes()` in `anonymizer/index.ts` should also sanitize or reject path segments matching `constructor` or `prototype` before passing them to `set()`.\n\n---\n\n## Timeline\n\n| Date | Event |\n|------|-------|\n| 2026-03-24 | Initial report submitted |\n| 2026-04-09 | Vendor confirmed; fixed in 0.5.18 |\n\n---\n\n## Credits\n\nReported by: OneThing4101",
"id": "GHSA-fw9q-39r9-c252",
"modified": "2026-04-10T21:37:36Z",
"published": "2026-04-10T20:18:02Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-fw9q-39r9-c252"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-40190"
},
{
"type": "WEB",
"url": "https://github.com/langchain-ai/langsmith-sdk/pull/2690"
},
{
"type": "WEB",
"url": "https://github.com/langchain-ai/langsmith-sdk/commit/31d3c3aec02892f4312baae112f817d6b2f0ebe3"
},
{
"type": "PACKAGE",
"url": "https://github.com/langchain-ai/langsmith-sdk"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
"type": "CVSS_V3"
}
],
"summary": "LangSmith Client SDKs has Prototype Pollution in langsmith-sdk via Incomplete `__proto__` Guard in Internal lodash `set()`"
}
WID-SEC-W-2026-3046
Vulnerability from csaf_certbund - Published: 2026-08-26 22:00 - Updated: 2026-08-30 22:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
IBM Concert <3.0.0
IBM / Concert
|
<3.0.0 |
{
"document": {
"aggregate_severity": {
"text": "hoch"
},
"category": "csaf_base",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE",
"url": "https://www.first.org/tlp/"
}
},
"lang": "de-DE",
"notes": [
{
"category": "legal_disclaimer",
"text": "Das BSI ist als Anbieter f\u00fcr die eigenen, zur Nutzung bereitgestellten Inhalte nach den allgemeinen Gesetzen verantwortlich. Nutzerinnen und Nutzer sind jedoch daf\u00fcr verantwortlich, die Verwendung und/oder die Umsetzung der mit den Inhalten bereitgestellten Informationen sorgf\u00e4ltig im Einzelfall zu pr\u00fcfen."
},
{
"category": "description",
"text": "IBM Concert ist eine Plattform f\u00fcr die Automatisierung von Gesch\u00e4ftsprozessen und Entscheidungsfindung.",
"title": "Produktbeschreibung"
},
{
"category": "summary",
"text": "Ein Angreifer kann mehrere Schwachstellen in IBM Concert ausnutzen, um beliebigen Programmcode auszuf\u00fchren, um einen Denial of Service Angriff durchzuf\u00fchren, um Informationen offenzulegen, um Dateien zu manipulieren, um einen Cross-Site Scripting Angriff durchzuf\u00fchren, um einen SQL-Injection Angriff durchzuf\u00fchren und um Sicherheitsvorkehrungen zu umgehen.",
"title": "Angriff"
},
{
"category": "general",
"text": "- Linux\n- UNIX",
"title": "Betroffene Betriebssysteme"
}
],
"publisher": {
"category": "other",
"contact_details": "csaf-provider@cert-bund.de",
"name": "Bundesamt f\u00fcr Sicherheit in der Informationstechnik",
"namespace": "https://www.bsi.bund.de"
},
"references": [
{
"category": "self",
"summary": "WID-SEC-W-2026-3046 - CSAF Version",
"url": "https://wid.cert-bund.de/.well-known/csaf/white/2026/wid-sec-w-2026-3046.json"
},
{
"category": "self",
"summary": "WID-SEC-2026-3046 - Portal Version",
"url": "https://wid.cert-bund.de/portal/wid/securityadvisory?name=WID-SEC-2026-3046"
},
{
"category": "external",
"summary": "IBM Security Bulletin 7285337 vom 2026-08-26",
"url": "https://www.ibm.com/support/pages/node/7285337"
}
],
"source_lang": "en-US",
"title": "IBM Concert: Mehrere Schwachstellen",
"tracking": {
"current_release_date": "2026-08-30T22:00:00.000+00:00",
"generator": {
"date": "2026-08-31T06:12:08.730+00:00",
"engine": {
"name": "BSI-WID",
"version": "1.6.0"
}
},
"id": "WID-SEC-W-2026-3046",
"initial_release_date": "2026-08-26T22:00:00.000+00:00",
"revision_history": [
{
"date": "2026-08-26T22:00:00.000+00:00",
"number": "1",
"summary": "Initiale Fassung"
},
{
"date": "2026-08-30T22:00:00.000+00:00",
"number": "2",
"summary": "Referenz(en) aufgenommen: EUVD-2026-67959, EUVD-2025-210810"
}
],
"status": "final",
"version": "2"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "\u003c3.0.0",
"product": {
"name": "IBM Concert \u003c3.0.0",
"product_id": "T058718"
}
},
{
"category": "product_version",
"name": "3.0.0",
"product": {
"name": "IBM Concert 3.0.0",
"product_id": "T058718-fixed",
"product_identification_helper": {
"cpe": "cpe:/a:ibm:concert:3.0.0"
}
}
}
],
"category": "product_name",
"name": "Concert"
}
],
"category": "vendor",
"name": "IBM"
}
]
},
"vulnerabilities": [
{
"cve": "CVE-2019-19921",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2019-19921"
},
{
"cve": "CVE-2021-23337",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2021-23337"
},
{
"cve": "CVE-2024-3651",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2024-3651"
},
{
"cve": "CVE-2024-39338",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2024-39338"
},
{
"cve": "CVE-2024-45590",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2024-45590"
},
{
"cve": "CVE-2025-13465",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-13465"
},
{
"cve": "CVE-2025-15284",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-15284"
},
{
"cve": "CVE-2025-15599",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-15599"
},
{
"cve": "CVE-2025-22874",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-22874"
},
{
"cve": "CVE-2025-47273",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-47273"
},
{
"cve": "CVE-2025-47907",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-47907"
},
{
"cve": "CVE-2025-52881",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-52881"
},
{
"cve": "CVE-2025-53643",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-53643"
},
{
"cve": "CVE-2025-55184",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-55184"
},
{
"cve": "CVE-2025-58056",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-58056"
},
{
"cve": "CVE-2025-58188",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-58188"
},
{
"cve": "CVE-2025-58189",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-58189"
},
{
"cve": "CVE-2025-61723",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-61723"
},
{
"cve": "CVE-2025-61730",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-61730"
},
{
"cve": "CVE-2025-64649",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-64649"
},
{
"cve": "CVE-2025-64756",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-64756"
},
{
"cve": "CVE-2025-67221",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-67221"
},
{
"cve": "CVE-2025-68121",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-68121"
},
{
"cve": "CVE-2025-68146",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2025-68146"
},
{
"cve": "CVE-2026-0540",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-0540"
},
{
"cve": "CVE-2026-2327",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-2327"
},
{
"cve": "CVE-2026-23490",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-23490"
},
{
"cve": "CVE-2026-23897",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-23897"
},
{
"cve": "CVE-2026-2391",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-2391"
},
{
"cve": "CVE-2026-23949",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-23949"
},
{
"cve": "CVE-2026-24486",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-24486"
},
{
"cve": "CVE-2026-25528",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-25528"
},
{
"cve": "CVE-2026-25547",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-25547"
},
{
"cve": "CVE-2026-25639",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-25639"
},
{
"cve": "CVE-2026-25990",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-25990"
},
{
"cve": "CVE-2026-26007",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-26007"
},
{
"cve": "CVE-2026-26019",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-26019"
},
{
"cve": "CVE-2026-26996",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-26996"
},
{
"cve": "CVE-2026-27142",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-27142"
},
{
"cve": "CVE-2026-27212",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-27212"
},
{
"cve": "CVE-2026-27699",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-27699"
},
{
"cve": "CVE-2026-27903",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-27903"
},
{
"cve": "CVE-2026-27904",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-27904"
},
{
"cve": "CVE-2026-28684",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-28684"
},
{
"cve": "CVE-2026-29063",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-29063"
},
{
"cve": "CVE-2026-29181",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-29181"
},
{
"cve": "CVE-2026-2950",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-2950"
},
{
"cve": "CVE-2026-31808",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-31808"
},
{
"cve": "CVE-2026-31900",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-31900"
},
{
"cve": "CVE-2026-32274",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-32274"
},
{
"cve": "CVE-2026-32288",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-32288"
},
{
"cve": "CVE-2026-32597",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-32597"
},
{
"cve": "CVE-2026-32630",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-32630"
},
{
"cve": "CVE-2026-32887",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-32887"
},
{
"cve": "CVE-2026-32952",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-32952"
},
{
"cve": "CVE-2026-33186",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-33186"
},
{
"cve": "CVE-2026-33532",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-33532"
},
{
"cve": "CVE-2026-33750",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-33750"
},
{
"cve": "CVE-2026-33814",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-33814"
},
{
"cve": "CVE-2026-33816",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-33816"
},
{
"cve": "CVE-2026-33916",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-33916"
},
{
"cve": "CVE-2026-34043",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-34043"
},
{
"cve": "CVE-2026-34073",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-34073"
},
{
"cve": "CVE-2026-34077",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-34077"
},
{
"cve": "CVE-2026-3520",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-3520"
},
{
"cve": "CVE-2026-35469",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-35469"
},
{
"cve": "CVE-2026-35515",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-35515"
},
{
"cve": "CVE-2026-3627",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-3627"
},
{
"cve": "CVE-2026-39823",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-39823"
},
{
"cve": "CVE-2026-39825",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-39825"
},
{
"cve": "CVE-2026-39826",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-39826"
},
{
"cve": "CVE-2026-39892",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-39892"
},
{
"cve": "CVE-2026-39984",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-39984"
},
{
"cve": "CVE-2026-40175",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-40175"
},
{
"cve": "CVE-2026-40179",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-40179"
},
{
"cve": "CVE-2026-40181",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-40181"
},
{
"cve": "CVE-2026-40190",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-40190"
},
{
"cve": "CVE-2026-40347",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-40347"
},
{
"cve": "CVE-2026-41066",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41066"
},
{
"cve": "CVE-2026-41182",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41182"
},
{
"cve": "CVE-2026-41238",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41238"
},
{
"cve": "CVE-2026-41239",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41239"
},
{
"cve": "CVE-2026-41240",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41240"
},
{
"cve": "CVE-2026-41305",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41305"
},
{
"cve": "CVE-2026-41324",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41324"
},
{
"cve": "CVE-2026-41425",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41425"
},
{
"cve": "CVE-2026-41481",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41481"
},
{
"cve": "CVE-2026-41488",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41488"
},
{
"cve": "CVE-2026-41602",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41602"
},
{
"cve": "CVE-2026-41636",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-41636"
},
{
"cve": "CVE-2026-42151",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42151"
},
{
"cve": "CVE-2026-42154",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42154"
},
{
"cve": "CVE-2026-42198",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42198"
},
{
"cve": "CVE-2026-42211",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42211"
},
{
"cve": "CVE-2026-42338",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42338"
},
{
"cve": "CVE-2026-42342",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42342"
},
{
"cve": "CVE-2026-42561",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42561"
},
{
"cve": "CVE-2026-42577",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-42577"
},
{
"cve": "CVE-2026-43870",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-43870"
},
{
"cve": "CVE-2026-44405",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44405"
},
{
"cve": "CVE-2026-44431",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44431"
},
{
"cve": "CVE-2026-44432",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44432"
},
{
"cve": "CVE-2026-44486",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44486"
},
{
"cve": "CVE-2026-44487",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44487"
},
{
"cve": "CVE-2026-44488",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44488"
},
{
"cve": "CVE-2026-44492",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44492"
},
{
"cve": "CVE-2026-44494",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44494"
},
{
"cve": "CVE-2026-44496",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44496"
},
{
"cve": "CVE-2026-44728",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-44728"
},
{
"cve": "CVE-2026-4539",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-4539"
},
{
"cve": "CVE-2026-45409",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-45409"
},
{
"cve": "CVE-2026-45736",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-45736"
},
{
"cve": "CVE-2026-46625",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-46625"
},
{
"cve": "CVE-2026-4800",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-4800"
},
{
"cve": "CVE-2026-4923",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-4923"
},
{
"cve": "CVE-2026-4926",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-4926"
},
{
"cve": "CVE-2026-7246",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-7246"
},
{
"cve": "CVE-2026-8723",
"product_status": {
"known_affected": [
"T058718"
]
},
"release_date": "2026-08-26T22:00:00.000+00:00",
"title": "CVE-2026-8723"
}
]
}
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.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.