{ "document": { "category": "csaf_base", "csaf_version": "2.0", "distribution": { "tlp": { "label": "WHITE" } }, "lang": "en", "notes": [ { "category": "legal_disclaimer", "text": "The Netherlands Cyber Security Center (henceforth: NCSC-NL) maintains this portal to enhance access to its information and vulnerabilities. The use of this information is subject to the following terms and conditions:\n\nThe vulnerabilities disclosed in this portal are gathered by NCSC-NL from a variety of open sources, which the user can retrieve from other platforms. NCSC-NL makes every reasonable effort to ensure that the content of this portal is kept up to date, and that it is accurate and complete. Nevertheless, NCSC-NL cannot entirely rule out the possibility of errors, and therefore cannot give any warranty in respect of its completeness, accuracy or real-time keeping up-to-date. NCSC-NL does not control nor guarantee the accuracy, relevance, timeliness or completeness of information obtained from these external sources. The vulnerabilities disclosed in this portal are intended solely for the convenience of professional parties to take appropriate measures to manage the risks posed to the cybersecurity. No rights can be derived from the information provided therein.\n\nNCSC-NL and the Kingdom of the Netherlands assume no legal liability or responsibility for any damage resulting from either the use or inability of use of the vulnerabilities disclosed in this portal. This includes damage resulting from the inaccuracy of incompleteness of the information contained in it.\nThe information on this page is subject to Dutch law. All disputes related to or arising from the use of this portal regarding the disclosure of vulnerabilities will be submitted to the competent court in The Hague. This choice of means also applies to the court in summary proceedings." } ], "publisher": { "category": "coordinator", "contact_details": "cert@ncsc.nl", "name": "National Cyber Security Centre", "namespace": "https://www.ncsc.nl/" }, "title": "CVE-2026-27195", "tracking": { "current_release_date": "2026-03-26T18:51:39.104997Z", "generator": { "date": "2026-02-17T15:00:00Z", "engine": { "name": "V.E.L.M.A", "version": "1.7" } }, "id": "CVE-2026-27195", "initial_release_date": "2026-02-24T21:38:35.378906Z", "revision_history": [ { "date": "2026-02-24T21:38:35.378906Z", "number": "1", "summary": "CVE created.| Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (2).| References created (6).| CWES updated (1)." }, { "date": "2026-02-24T21:38:41.106745Z", "number": "2", "summary": "NCSC Score created." }, { "date": "2026-02-24T21:39:50.052790Z", "number": "3", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (7).| CWES updated (1)." }, { "date": "2026-02-24T21:39:54.982400Z", "number": "4", "summary": "NCSC Score updated." }, { "date": "2026-02-24T22:32:29.914268Z", "number": "5", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| References created (6).| CWES updated (1)." }, { "date": "2026-02-24T22:32:38.626670Z", "number": "6", "summary": "NCSC Score updated." }, { "date": "2026-02-24T22:38:51.025218Z", "number": "7", "summary": "Unknown change." }, { "date": "2026-02-25T00:43:45.987633Z", "number": "8", "summary": "Source created.| CVE status created. (valid)" }, { "date": "2026-02-25T06:43:27.297607Z", "number": "9", "summary": "Description created for source." }, { "date": "2026-02-25T11:02:22.746899Z", "number": "10", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (4).| References created (8).| CWES updated (1)." }, { "date": "2026-02-25T12:27:57.551165Z", "number": "11", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products connected (2).| Product Identifiers created (1).| Product Remediations created (2).| References created (8).| CWES updated (1).| Vendor_assessment created." }, { "date": "2026-02-25T12:28:00.995262Z", "number": "12", "summary": "NCSC Score updated." }, { "date": "2026-02-25T15:14:03.539093Z", "number": "13", "summary": "Source created.| CVE status created. (valid)| EPSS created." }, { "date": "2026-02-25T15:28:59.465812Z", "number": "14", "summary": "CVSS created.| Products connected (2).| Product Identifiers created (2)." }, { "date": "2026-02-25T15:29:03.688329Z", "number": "15", "summary": "NCSC Score updated." }, { "date": "2026-02-27T20:39:34.498216Z", "number": "16", "summary": "References created (2)." }, { "date": "2026-02-27T20:39:42.068412Z", "number": "17", "summary": "NCSC Score updated." }, { "date": "2026-03-02T15:43:11.004975Z", "number": "18", "summary": "Products connected (28).| Products created (1)." }, { "date": "2026-03-02T15:43:23.908085Z", "number": "19", "summary": "NCSC Score updated." }, { "date": "2026-03-03T14:25:19.281340Z", "number": "20", "summary": "Products removed (29)." }, { "date": "2026-03-03T14:25:24.905635Z", "number": "21", "summary": "NCSC Score updated." }, { "date": "2026-03-20T09:42:04.270409Z", "number": "22", "summary": "Source connected.| CVE status created. (valid)| EPSS created." }, { "date": "2026-03-20T09:42:08.338176Z", "number": "23", "summary": "NCSC Score updated." }, { "date": "2026-03-26T18:47:42.134983Z", "number": "24", "summary": "Source created.| CVE status created. (valid)| Description created for source.| CVSS created.| Products created (4).| References created (10).| CWES updated (1)." }, { "date": "2026-03-26T18:47:48.959557Z", "number": "25", "summary": "NCSC Score updated." } ], "status": "interim", "version": "25" } }, "product_tree": { "branches": [ { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:rpm/1", "product": { "name": "vers:rpm/1", "product_id": "CSAFPID-2914823", "product_identification_helper": { "cpe": "cpe:/a:redhat:connectivity_link:1" } } } ], "category": "product_name", "name": "Red Hat Connectivity Link 1" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:rpm/unknown", "product": { "name": "vers:rpm/unknown", "product_id": "CSAFPID-5194593" } } ], "category": "product_name", "name": "wasm-shim-rhel9" } ], "category": "product_family", "name": "Red Hat Connectivity Link 1" } ], "category": "vendor", "name": "Red Hat" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/40.0.4", "product": { "name": "vers:unknown/40.0.4", "product_id": "CSAFPID-5918964" } }, { "category": "product_version_range", "name": "vers:unknown/41.0.4", "product": { "name": "vers:unknown/41.0.4", "product_id": "CSAFPID-5918965" } }, { "category": "product_version_range", "name": "vers:unknown/>=39.0.0|<40.0.4", "product": { "name": "vers:unknown/>=39.0.0|<40.0.4", "product_id": "CSAFPID-5918966" } }, { "category": "product_version_range", "name": "vers:unknown/>=41.0.0|<41.0.4", "product": { "name": "vers:unknown/>=41.0.0|<41.0.4", "product_id": "CSAFPID-5918967" } } ], "category": "product_name", "name": "cargo/wasmtime" } ], "category": "vendor", "name": "bytecodealliance" }, { "branches": [ { "branches": [ { "category": "product_version_range", "name": "vers:unknown/>=39.0.0|<40.0.4", "product": { "name": "vers:unknown/>=39.0.0|<40.0.4", "product_id": "CSAFPID-5699781", "product_identification_helper": { "cpe": "cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/>=41.0.0|<41.0.4", "product": { "name": "vers:unknown/>=41.0.0|<41.0.4", "product_id": "CSAFPID-5699782", "product_identification_helper": { "cpe": "cpe:2.3:a:bytecodealliance:wasmtime:*:*:*:*:*:rust:*:*" } } }, { "category": "product_version_range", "name": "vers:unknown/v41.0.0", "product": { "name": "vers:unknown/v41.0.0", "product_id": "CSAFPID-5480178" } }, { "category": "product_version_range", "name": "vers:unknown/v41.0.1", "product": { "name": "vers:unknown/v41.0.1", "product_id": "CSAFPID-5702047" } }, { "category": "product_version_range", "name": "vers:unknown/v41.0.2", "product": { "name": "vers:unknown/v41.0.2", "product_id": "CSAFPID-5702048" } }, { "category": "product_version_range", "name": "vers:unknown/v41.0.3", "product": { "name": "vers:unknown/v41.0.3", "product_id": "CSAFPID-5702049" } } ], "category": "product_name", "name": "wasmtime" } ], "category": "vendor", "name": "Bytecode Alliance" } ] }, "vulnerabilities": [ { "cve": "CVE-2026-27195", "cwe": { "id": "CWE-248", "name": "Uncaught Exception" }, "notes": [ { "category": "description", "text": "Wasmtime is a runtime for WebAssembly. Starting with Wasmtime 39.0.0, the `component-model-async` feature became the default, which brought with it a new implementation of `[Typed]Func::call_async` which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances: First, the host embedding calls `[Typed]Func::call_async` on a function exported by a component, polling the returned `Future` once. Second, the component function yields control to the async runtime (e.g. Tokio), e.g. due to a call to host function registered using `LinkerInstance::func_wrap_async` which yields, or due an epoch interruption. Third, the host embedding drops the `Future` after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete. Fourth, the host embedding calls `[Typed]Func::call_async` again, polling the returned `Future`. Since the component instance cannot be entered at this point, the call traps, but not before allocating a task and thread for the call. Fifth, the host embedding ignores the trap and drops the `Future`. This panics due to the runtime attempting to dispose of the task created above, which panics since the thread has not yet exited. When a host embedder using the affected versions of Wasmtime calls `wasmtime::component::[Typed]Func::call_async` on a guest export and then drops the returned future without waiting for it to resolve, and then does so again with the same component instance, Wasmtime will panic. Embeddings that have the `component-model-async` compile-time feature disabled are unaffected. Wasmtime 40.0.4 and 41.0.4 have been patched to fix this issue. Versions 42.0.0 and later are not affected. If an embedding is not actually using any component-model-async features then disabling the `component-model-async` Cargo feature can work around this issue. This issue can also be worked around by either ensuring every `call_async` future is awaited until it completes or refraining from using the `Store` again after dropping a not-yet-resolved `call_async` future.", "title": "cveprojectv5 - https://www.cve.org/CVERecord?id=CVE-2026-27195" }, { "category": "description", "text": "The affected versions of Wasmtime can panic if the host embedder drops the future returned by `wasmtime::component::[Typed]Func::call_async` before it resolves.\n\n### Details\n\nStarting with Wasmtime 39.0.0, the `component-model-async` feature became the default, which brought with it a new implementation of `[Typed]Func::call_async` which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances:\n\n1. The host embedding calls `[Typed]Func::call_async` on a function exported by a component, polling the returned `Future` once.\n2. The component function yields control to the async runtime (e.g. Tokio), e.g. due to a call to host function registered using `LinkerInstance::func_wrap_async` which yields, or due an epoch interruption.\n3. The host embedding drops the `Future` after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete.\n4. The host embedding calls `[Typed]Func::call_async` again, polling the returned `Future`. Since the component instance cannot be entered at this point, the call traps, but not before allocating a task and thread for the call.\n5. The host embedding ignores the trap and drops the `Future`. This panics due to the runtime attempting to dispose of the task created above, which panics since the thread has not yet exited.\n\n### Impact\nWhen a host embedder using the affected versions of Wasmtime calls `wasmtime::component::[Typed]Func::call_async` on a guest export and then drops the returned future without waiting for it to resolve, and then does so again with the same component instance, Wasmtime will panic. Embeddings that have the `component-model-async` compile-time feature disabled are unaffected.\n\n### Patches\nWasmtime 40.0.4 and 41.0.4 have been patched to fix this issue. Versions 42.0.0 and later are not affected.\n\n### Workarounds\nIf an embedding is not actually using any component-model-async features then disabling the `component-model-async` Cargo feature can work around this issue. This issue can also be worked around by either ensuring every `call_async` future is awaited until it completes or refraining from using the `Store` again after dropping a not-yet-resolved `call_async` future.\n\n### Resources\nThis was first reported in https://bytecodealliance.zulipchat.com/#narrow/channel/206238-general/topic/Panic.20in.20Wasmtime.2041.2E0.2E3.20.28runtime.2Fconcurrent.2Fcomponent.29", "title": "github - https://github.com/advisories/GHSA-xjhv-v822-pf94" }, { "category": "description", "text": "Wasmtime is a runtime for WebAssembly. Starting with Wasmtime 39.0.0, the `component-model-async` feature became the default, which brought with it a new implementation of `[Typed]Func::call_async` which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances: First, the host embedding calls `[Typed]Func::call_async` on a function exported by a component, polling the returned `Future` once. Second, the component function yields control to the async runtime (e.g. Tokio), e.g. due to a call to host function registered using `LinkerInstance::func_wrap_async` which yields, or due an epoch interruption. Third, the host embedding drops the `Future` after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete. Fourth, the host embedding calls `[Typed]Func::call_async` again, polling the returned `Future`. Since the component instance cannot be entered at this point, the call traps, but not before allocating a task and thread for the call. Fifth, the host embedding ignores the trap and drops the `Future`. This panics due to the runtime attempting to dispose of the task created above, which panics since the thread has not yet exited. When a host embedder using the affected versions of Wasmtime calls `wasmtime::component::[Typed]Func::call_async` on a guest export and then drops the returned future without waiting for it to resolve, and then does so again with the same component instance, Wasmtime will panic. Embeddings that have the `component-model-async` compile-time feature disabled are unaffected. Wasmtime 40.0.4 and 41.0.4 have been patched to fix this issue. Versions 42.0.0 and later are not affected. If an embedding is not actually using any component-model-async features then disabling the `component-model-async` Cargo feature can work around this issue. This issue can also be worked around by either ensuring every `call_async` future is awaited until it completes or refraining from using the `Store` again after dropping a not-yet-resolved `call_async` future.", "title": "nvd - https://nvd.nist.gov/vuln/detail/CVE-2026-27195" }, { "category": "description", "text": "Wasmtime is a runtime for WebAssembly. Starting with Wasmtime 39.0.0, the `component-model-async` feature became the default, which brought with it a new implementation of `[Typed]Func::call_async` which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances: First, the host embedding calls `[Typed]Func::call_async` on a function exported by a component, polling the returned `Future` once. Second, the component function yields control to the async runtime (e.g. Tokio), e.g. due to a call to host function registered using `LinkerInstance::func_wrap_async` which yields, or due an epoch interruption. Third, the host embedding drops the `Future` after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete. Fourth, the host embedding calls `[Typed]Func::call_async` again, polling the returned `Future`. Since the component instance cannot be entered at this point, the call traps, but not before allocating a task and thread for the call. Fifth, the host embedding ignores the trap and drops the `Future`. This panics due to the runtime attempting to dispose of the task created above, which panics since the thread has not yet exited. When a host embedder using the affected versions of Wasmtime calls `wasmtime::component::[Typed]Func::call_async` on a guest export and then drops the returned future without waiting for it to resolve, and then does so again with the same component instance, Wasmtime will panic. Embeddings that have the `component-model-async` compile-time feature disabled are unaffected. Wasmtime 40.0.4 and 41.0.4 have been patched to fix this issue. Versions 42.0.0 and later are not affected. If an embedding is not actually using any component-model-async features then disabling the `component-model-async` Cargo feature can work around this issue. This issue can also be worked around by either ensuring every `call_async` future is awaited until it completes or refraining from using the `Store` again after dropping a not-yet-resolved `call_async` future.", "title": "debian - https://security-tracker.debian.org/tracker/CVE-2026-27195" }, { "category": "description", "text": "Wasmtime is a runtime for WebAssembly. Starting with Wasmtime 39.0.0, the `component-model-async` feature became the default, which brought with it a new implementation of `[Typed]Func::call_async` which made it capable of calling async-typed guest export functions. However, that implementation had a bug leading to a panic under certain circumstances: First, the host embedding calls `[Typed]Func::call_async` on a function exported by a component, polling the returned `Future` once. Second, the component function yields control to the async runtime (e.g. Tokio), e.g. due to a call to host function registered using `LinkerInstance::func_wrap_async` which yields, or due an epoch interruption. Third, the host embedding drops the `Future` after polling it once. This leaves the component instance in a non-reenterable state since the call never had a chance to complete. Fourth, the host embedding calls `[Typed]Func::call_async` again, polling the returned `Future`. Since the component instance cannot be entered at this point, the call traps, but not before allocating a task and thread for the call. Fifth, the host embedding ignores the trap and drops the `Future`. This panics due to the runtime attempting to dispose of the task created above, which panics since the thread has not yet exited. When a host embedder using the affected versions of Wasmtime calls `wasmtime::component::[Typed]Func::call_async` on a guest export and then drops the returned future without waiting for it to resolve, and then does so again with the same component instance, Wasmtime will panic. Embeddings that have the `component-model-async` compile-time feature disabled are unaffected. Wasmtime 40.0.4 and 41.0.4 have been patched to fix this issue. Versions 42.0.0 and later are not affected. If an embedding is not actually using any component-model-async features then disabling the `component-model-async` Cargo feature can work around this issue. This issue can also be worked around by either ensuring every `call_async` future is awaited until it completes or refraining from using the `Store` again after dropping a not-yet-resolved `call_async` future.", "title": "osv - https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/GIT%2FCVE-2026-27195.json?alt=media" }, { "category": "description", "text": "No description is available for this CVE.", "title": "redhat - https://access.redhat.com/security/cve/CVE-2026-27195" }, { "category": "description", "text": "The affected versions of Wasmtime can panic if the host embedder drops the future returned by `wasmtime::component::[Typed]Func::call_async` before it resolves.", "title": "gitlab - https://gitlab.com/api/v4/projects/25847700/repository/files/cargo%2Fwasmtime%2FCVE-2026-27195.yml/raw" }, { "category": "other", "text": "0.00061", "title": "EPSS" }, { "category": "other", "text": "CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H", "title": "CVSSV4" }, { "category": "other", "text": "6.9", "title": "CVSSV4 base score" }, { "category": "other", "text": "4.3", "title": "NCSC Score" }, { "category": "other", "text": "Is related to (a version of) an uncommon product, Is related to an uncommon product vendor, Is related to CWE-248 (Uncaught Exception), There is product_remediation data available from source Redhat", "title": "NCSC Score top decreasing factors" }, { "category": "details", "text": "Severity: 2\n", "title": "Vendor assessment" } ], "product_status": { "fixed": [ "CSAFPID-5918964", "CSAFPID-5918965" ], "known_affected": [ "CSAFPID-5699781", "CSAFPID-5699782", "CSAFPID-5480178", "CSAFPID-5702047", "CSAFPID-5702048", "CSAFPID-5702049", "CSAFPID-2914823", "CSAFPID-5194593", "CSAFPID-5918966", "CSAFPID-5918967" ] }, "references": [ { "category": "external", "summary": "Source - cveprojectv5", "url": "https://www.cve.org/CVERecord?id=CVE-2026-27195" }, { "category": "external", "summary": "Source raw - cveprojectv5", "url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/27xxx/CVE-2026-27195.json" }, { "category": "external", "summary": "Source - github", "url": "https://github.com/advisories/GHSA-xjhv-v822-pf94" }, { "category": "external", "summary": "Source raw - github", "url": "https://api.github.com/advisories/GHSA-xjhv-v822-pf94" }, { "category": "external", "summary": "Source - nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27195" }, { "category": "external", "summary": "Source raw - nvd", "url": "https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-27195" }, { "category": "external", "summary": "Source - debian", "url": "https://security-tracker.debian.org/tracker/CVE-2026-27195" }, { "category": "external", "summary": "Source - osv", "url": "https://www.googleapis.com/download/storage/v1/b/osv-vulnerabilities/o/GIT%2FCVE-2026-27195.json?alt=media" }, { "category": "external", "summary": "Source - redhat", "url": "https://access.redhat.com/security/cve/CVE-2026-27195" }, { "category": "external", "summary": "Source raw - redhat", "url": "https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-27195.json" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?cve=CVE-2026-27195" }, { "category": "external", "summary": "Source raw - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - first", "url": "https://api.first.org/data/v1/epss?limit=10000&offset=0" }, { "category": "external", "summary": "Source - gitlab", "url": "https://gitlab.com/api/v4/projects/25847700/repository/files/cargo%2Fwasmtime%2FCVE-2026-27195.yml/raw" }, { "category": "external", "summary": "Reference - cveprojectv5; github; gitlab; nvd; osv; redhat", "url": "https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-xjhv-v822-pf94" }, { "category": "external", "summary": "Reference - cveprojectv5; github; gitlab; nvd; osv; redhat", "url": "https://github.com/bytecodealliance/wasmtime/commit/9e51c0d9a240a9613d279c061f82286bd11383fd" }, { "category": "external", "summary": "Reference - cveprojectv5; github; gitlab; nvd; osv; redhat", "url": "https://github.com/bytecodealliance/wasmtime/commit/d86b00736b9ece60b3c81e52f7a7e4cdd9f7d895" }, { "category": "external", "summary": "Reference - cveprojectv5; github; gitlab; nvd; osv; redhat", "url": "https://bytecodealliance.zulipchat.com/#narrow/channel/206238-general/topic/.E2.9C.94.20Panic.20in.20Wasmtime.2041.2E0.2E3.20.28runtime.2Fconcurrent.2Fcomponent.29/with/574438798" }, { "category": "external", "summary": "Reference - cveprojectv5; github; gitlab; nvd; osv; redhat", "url": "https://github.com/bytecodealliance/wasmtime/releases/tag/v40.0.4" }, { "category": "external", "summary": "Reference - cveprojectv5; github; gitlab; nvd; osv; redhat", "url": "https://github.com/bytecodealliance/wasmtime/releases/tag/v41.0.4" }, { "category": "external", "summary": "Reference - github; gitlab", "url": "https://github.com/advisories/GHSA-xjhv-v822-pf94" }, { "category": "external", "summary": "Reference - osv", "url": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/27xxx/CVE-2026-27195.json" }, { "category": "external", "summary": "Reference - github; gitlab; osv; redhat", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-27195" }, { "category": "external", "summary": "Reference - redhat", "url": "https://www.cve.org/CVERecord?id=CVE-2026-27195" }, { "category": "external", "summary": "Reference - github; gitlab", "url": "https://rustsec.org/advisories/RUSTSEC-2026-0022.html" }, { "category": "external", "summary": "Reference - gitlab", "url": "https://github.com/bytecodealliance/wasmtime" } ], "remediations": [ { "category": "mitigation", "details": "Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.", "product_ids": [ "CSAFPID-2914823", "CSAFPID-5194593" ] } ], "scores": [ { "cvss_v3": { "version": "3.1", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H", "baseScore": 7.5, "baseSeverity": "HIGH" }, "products": [ "CSAFPID-2914823", "CSAFPID-5194593", "CSAFPID-5480178", "CSAFPID-5699781", "CSAFPID-5699782", "CSAFPID-5702047", "CSAFPID-5702048", "CSAFPID-5702049", "CSAFPID-5918966", "CSAFPID-5918967" ] } ], "title": "CVE-2026-27195" } ] }